-
Notifications
You must be signed in to change notification settings - Fork 273
New issue
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
getWebpackVersion does not work properly #309
Comments
Проще по русски написать :) |
Could you please create repo with minimal setup to demonstrate a problem (package.json, webpack config, SVG image and piece of your code). If you don't want to create a repository - you can create a gist with multiple files. |
fixed.. |
Fixed in |
@williansabiao which NodeJS version is used? |
The Cypress uses his own Node build. It's v8.2.1 😞 . I just saw they are working on to update it. So, probably it is the reason I'm getting the error in the new versions of I guess I can update to a newer version when Cypress update as well. That's ok. Thanks. |
Just wanted to highlight that this change (PR #314 ) breaks builds where webpack is started from a global Node.js application such as a global Gulp installation. In that case the main entry point for Node.js will be the global Gulp and its paths (global paths) will be present in I have found the following workarounds:
Not sure if this is a problem that this of concern for this module, but since others might encounter the same issue I post my findings here. |
I'm also running into this problem when running ESLint (with eslint-import-resolver-webpack). This line: Causes this error:
|
I use lerna and there is two directories: with builder and with sites. When I bootstrap builder to each site, this error is causing:
|
Is there any way to make it work with eslint-import-resolver-webpack? |
@williansabiao @linqcan @Nettsentrisk @ivan-podgornov @ViieeS Using autodetecting webpack version was very bad idea. I've published alpha version without detecting webpack version, could some of you guys help me with trying it out?
|
@kisenka works fine! Thank you! Make PR, please. |
Published in |
Do you want to request a feature, report a bug or ask a question?
Bug
What is the current behavior?
svg-sprite-loader
havewebpack 4
in dependencies.getWebpackVersion
return version for webpack in{project}/node_modules/svg-sprite-loader/node_modules/webpack/package.json
What is the expected behavior?
getWebpackVersion
should return version for webpack in{project}/node_modules/webpack/package.json
If the current behavior is a bug, please provide the steps to reproduce, at least part of webpack config with loader configuration and piece of your code.
I just run my nuxt.js project and get this error:
Please tell us about your environment:
The text was updated successfully, but these errors were encountered: