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
When doing this, remember to update the location of config-yargs.js, it has changed. Maybe some other sources has changed too, so check where you import directly from the library.
The text was updated successfully, but these errors were encountered:
Hello @evenstensberg
I did a PR to update the paths of both config-yargs & convert-argv
I upgraded webpack-cli to the master branch and I run npm test cli.test on my machine and it passes the test however in AppVeyor testing it doesn't pass the test
on my machine, if I returned the paths to their origin it won't pass the test
I tried to upgrade webpack to it's latest version but it's still not passing the test
I got an idea to check if the new module with the new path exists or not and if it doesn't exist fall back to the original path so it can work with all versions v3.3.x and v3.2.x but I got that error 85:1 error Calls to require() should use string literals import/no-dynamic-require
so what did I miss here?
Just a heads up
When doing this, remember to update the location of
config-yargs.js
, it has changed. Maybe some other sources has changed too, so check where you import directly from the library.The text was updated successfully, but these errors were encountered: