We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
Perhaps the following is the correct syntax in Webpack 4?
import jssCamelCase from 'jss-camel-case'; import jssDefaultUnit from 'jss-default-unit'; import jssGlobal from 'jss-global'; import jssNested from 'jss-nested'; import jssPropsSort from 'jss-props-sort'; import jssVendorPrefixer from 'jss-vendor-prefixer'; ... use: [ { loader: 'jss-loader', // compiles JSS to CSS options: { plugins: [ jssCamelCase, jssDefaultUnit, //jssGlobal, jssNested, jssPropsSort, jssVendorPrefixer ] } } ] ...
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
object { mode?, amd?, bail?, cache?, context?, dependencies?, devServer?, devtool?, entry?, externals?, loader?, module?, name?, node?, output?, optimization?, parallelism?, performance?, plugins?, profile?, recordsInputPath?, recordsOutputPath?, recordsPath?, resolve?, resolveLoader?, serve?, stats?, target?, watch?, watchOptions? }
Perhaps the following is the correct syntax in Webpack 4?
The text was updated successfully, but these errors were encountered: