Switched from npm to pnpm and now absolute paths are broken? #5055
Unanswered
NikAtNight
asked this question in
Q&A
Replies: 1 comment
-
Did you find a fix for this? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
So
npm
was getting really slow for CircleCi and my builds were timing out and running into memory issues. So I wanted to switch topnpm
. Upon switching topnpm
I noticed that any.js
file in my react project that are using an absolute path no longer work and wants me to turn them all into relative paths. Not sure if this is a bug with the version or I'm doing something wrong but it all i did was delete mypackage-lock.json
and deleted mynode_modules
and installedpnpm@5
then ranpnpm i
Also using Webpack 4.
webpack file
jsconfig.json
I'm also getting this warning which I wasn't getting when using
npm
ExperimentalWarning: Package name self resolution is an experimental feature. This feature could change at any time
With
yarn
I also get the same error as above, but then this special failurecheeriojs/cheerio#2545
This did not work
Beta Was this translation helpful? Give feedback.
All reactions