ajv: Building with Webpack causes spurious warnings
It is being caused by this line:
https://github.com/epoberezkin/ajv/blob/3.5.0/lib/compile/index.js#L10
Is there a cleaner way to manage this dependency? Is peerDependencies
built for this?
Error stack below:
./~/ajv/lib/compile/index.js
Module not found: Error: Cannot resolve module 'js-beautify' in /app/myapp/node_modules/ajv/lib/compile
resolve module js-beautify in /app/myapp/node_modules/ajv/lib/compile
looking for modules in /app/myapp/node_modules
/app/myapp/node_modules/js-beautify doesn't exist (module as directory)
resolve 'file' js-beautify in /app/myapp/node_modules
resolve file
/app/myapp/node_modules/js-beautify doesn't exist
/app/myapp/node_modules/js-beautify.webpack.js doesn't exist
/app/myapp/node_modules/js-beautify.web.js doesn't exist
/app/myapp/node_modules/js-beautify.js doesn't exist
/app/myapp/node_modules/js-beautify.json doesn't exist
looking for modules in /app/myapp/public/js
/app/myapp/public/js/js-beautify doesn't exist (module as directory)
resolve 'file' js-beautify in /app/myapp/public/js
resolve file
/app/myapp/public/js/js-beautify doesn't exist
/app/myapp/public/js/js-beautify.webpack.js doesn't exist
/app/myapp/public/js/js-beautify.web.js doesn't exist
/app/myapp/public/js/js-beautify.js doesn't exist
/app/myapp/public/js/js-beautify.json doesn't exist
looking for modules in /app/myapp/public/css
/app/myapp/public/css/js-beautify doesn't exist (module as directory)
resolve 'file' js-beautify in /app/myapp/public/css
resolve file
/app/myapp/public/css/js-beautify doesn't exist
/app/myapp/public/css/js-beautify.webpack.js doesn't exist
/app/myapp/public/css/js-beautify.web.js doesn't exist
/app/myapp/public/css/js-beautify.js doesn't exist
/app/myapp/public/css/js-beautify.json doesn't exist
[/app/myapp/node_modules/js-beautify]
[/app/myapp/node_modules/js-beautify]
[/app/myapp/node_modules/js-beautify.webpack.js]
[/app/myapp/node_modules/js-beautify.web.js]
[/app/myapp/node_modules/js-beautify.js]
[/app/myapp/node_modules/js-beautify.json]
[/app/myapp/public/js/js-beautify]
[/app/myapp/public/js/js-beautify]
[/app/myapp/public/js/js-beautify.webpack.js]
[/app/myapp/public/js/js-beautify.web.js]
[/app/myapp/public/js/js-beautify.js]
[/app/myapp/public/js/js-beautify.json]
[/app/myapp/public/css/js-beautify]
[/app/myapp/public/css/js-beautify]
[/app/myapp/public/css/js-beautify.webpack.js]
[/app/myapp/public/css/js-beautify.web.js]
[/app/myapp/public/css/js-beautify.js]
[/app/myapp/public/css/js-beautify.json]
@ ./~/ajv/lib/compile/index.js 8:42-69
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Reactions: 2
- Comments: 28 (13 by maintainers)
Commits related to this issue
- refactor: make variable for package names local, closes #325, #117 — committed to ajv-validator/ajv by epoberezkin 8 years ago
- chore: Update ajv to stop errors in twitter library https://github.com/epoberezkin/ajv/issues/117#issuecomment-269841238 — committed to guilhermelimak/winter by guilhermelimak 7 years ago
@epoberezkin I am not talking about your library. But for example my library which is using your ajv library. I need to inform all my users about this problem because it looks like a bug in my library. I do not want to complain but you know it is ugly
I managed to suppress errors with the following plugin added to Webpack configuration:
@strax, new IgnorePlugin(/regenerator|nodent|js-beautify/, /ajv/) worked for me. Thanks
5.0.1-beta.3 should resolve it, finally
I believe the issue here is that the JavaScript community does not have a standard for loading modules dynamically.
Webpack 2 will support
System.import
. I don’t know what the spec is named, but I’ll definitely be testing it when it releases.