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
Using importCost on a project set up with packages installed by pnpm doesn't work.
Installing the same packages using npm then swapping back to pnpm works (because of the cache).
Tried debugging the issue to see where symlinks aren't respected (this is the main difference from pnpm to npm node_modules) to cause that, might be a problem with webpack itself?
The text was updated successfully, but these errors were encountered:
Just installed the extension and was wondering why it's not working for most modules 😅
Can confirm, that the resolution of symlinked modules seems to be the issue.
Seems at first glace that symlinks are handled here though…
Looks like #259 deals with the same issue
Using importCost on a project set up with packages installed by pnpm doesn't work.
Installing the same packages using npm then swapping back to pnpm works (because of the cache).
Tried debugging the issue to see where symlinks aren't respected (this is the main difference from pnpm to npm node_modules) to cause that, might be a problem with webpack itself?
The text was updated successfully, but these errors were encountered: