You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 4, 2020. It is now read-only.
I initially encountered the following error with Grommet CLI 5.0.0 and a webpack config titled webpack.config.babel.js
Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
- configuration should be an object.
After digging through the cli bin folder I noticed this line so I changed my webpack config file name to webpack.config.js and my project builds as expected. It would seem that the .default is the culprit, I switched through a few recent versions of Node to see if maybe there was a discrepancy there but Node 6.9.4 and up all seem to return undefined when reaching for the default export of the webpack config file.
This would most likely indicate a bug in how babel is interpreting the default export of the webpack config.
The text was updated successfully, but these errors were encountered:
I initially encountered the following error with Grommet CLI
5.0.0
and a webpack config titledwebpack.config.babel.js
After digging through the cli bin folder I noticed this line so I changed my webpack config file name to
webpack.config.js
and my project builds as expected. It would seem that the.default
is the culprit, I switched through a few recent versions of Node to see if maybe there was a discrepancy there but Node6.9.4
and up all seem to returnundefined
when reaching for the default export of the webpack config file.This would most likely indicate a bug in how babel is interpreting the default export of the webpack config.
The text was updated successfully, but these errors were encountered: