Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Webpack error when using v5.0.0
See original GitHub issue`WebpackOptionsValidationError: Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
- configuration.module.rules[1].resolve has an unknown property ‘fullySpecified’. These properties are valid: object { alias?, aliasFields?, cachePredicate?, cacheWithContext?, concord?, descriptionFiles?, enforceExtension?, enforceModuleExtension?, extensions?, fileSystem?, ignoreRootsErrors?, mainFields?, mainFiles?, moduleExtensions?, modules?, plugins?, preferAbsolute?, resolver?, roots?, symlinks?, unsafeCache?, useSyncFileSystemCalls? }`
serverless offline won’t start because of this error
My quick fix was to comment out the following inside src/webpack.config.js What would be a final fix? Thanks
// { // test: /\.mjs$/, // include: /node_modules/, // type: "javascript/auto", // resolve: { // fullySpecified: false, // }, // },
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:20 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I totally gave up on updating this library. It does not work properly since 5.0.
Went back to v4.4.0 due to this issue. Even if I can make it work locally using the hack mentioned above, the CI/CD doesn’t like it.