Could not resolve module preprocess-loader

[stereokai]

pnpm version: 0.73.2

Expected behavior:

Existing project is able to complete the build (it works when node modules are installed using npm/yarn)

Actual behavior:

Node errors:

• node -v prints:

ERROR in C:/Users/Tom/.pnpm-store/2/registry.npmjs.org/json3/3.3.2/~/json3/li
b/json3.js
Module not found: Error: Cannot resolve module 'preprocess-loader' in C:\User
s\Tom\.pnpm-store\2\registry.npmjs.org\json3\3.3.2\node_modules\json3\lib
 @ C:/Users/Tom/.pnpm-store/2/registry.npmjs.org/json3/3.3.2/~/json3/lib/json
3.js 1:0-135

ERROR in C:/Users/Tom/.pnpm-store/2/registry.npmjs.org/wtf-8/1.0.0/~/wtf-8/wt
f-8.js
Module not found: Error: Cannot resolve module 'preprocess-loader' in C:\User
s\Tom\.pnpm-store\2\registry.npmjs.org\wtf-8\1.0.0\node_modules\wtf-8
 @ C:/Users/Tom/.pnpm-store/2/registry.npmjs.org/wtf-8/1.0.0/~/wtf-8/wtf-8.js
 1:0-132

• Windows, OS X, or Linux?:
  Windows

[zkochan]

@vjpr is this similar to the one you had?

[vjpr]

@zkochan Looks similar.

@stereokai Can you post your webpack config?

[vjpr]

Maybe try to use require.resolve for your loader as mentioned here: https://webpack.js.org/guides/migrating/#loaders-in-configuration-resolve-relative-to-context

@stereokai There is a flag coming to pnpm soon that should fix this. Are you using webpack 1 or 2?

@zkochan That config we discussed would resolve this. @stereokai

[zkochan]

ok, if this causes so many issues then I'll make the flag turned off by default. And v1 of pnpm will not symlink leaf dependencies from the global store by default

[stereokai]

@zkochan But isn't that the whole point of pnpm?

[zkochan]

not really, that optimization was introduced only in version 0.70.
The point of pnpm is global store + sane node_modules structure + speed

[vjpr]

@stereokai pnpm symlinks from node_modules/foo to node_modules/.registry.npmjs.org/foo/x.x.x to give each module a unique ancestry of modules so that transitive deps are perfectly met depending on semver, and then hard links to a central store.

This was just a minor optimisation.

[stereokai]

@vjpr "unique hierarchy of its transitive deps" sounds like Greek to me :(

[vjpr]

@stereokai Haha, its really hard to describe in few words. I'll see if I can find the docs explaining it.

@zkochan Do we have some docs on how pnpm works - it seems the docs dir is a bit out of date. The peer deps is nice and detailed but, we need something similar for normal resolution.

[zkochan]

Check my blog. Why should we use pnpm? That one has a good explanation. There's a link to it in the readme

On Thu, Jun 22, 2017, 18:01 Vaughan Rouesnel ***@***.***> wrote: @stereokai <https://github.com/stereokai> Haha, its really hard to describe in few words. I'll see if I can find the docs explaining it. @zkochan <https://github.com/zkochan> Do we have some docs on how pnpm works - it seems the docs dir is a bit out of date. The peer deps is nice and detailed but, we need something similar for normal resolution. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#821 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB1pmzJsRnc5ltnDlj6_6xAUjwsKchj9ks5sGoGsgaJpZM4OCOfA> .

-- Zoltan

[vjpr]

@stereokai https://www.kochan.io/nodejs/why-should-we-use-pnpm.html

pnpm is usually faster than yarn, and the more deps you have, it becomes much much faster than yarn.

[zkochan]

not published yet

[zkochan]

Published in v0.74.3

[zkochan]

@stereokai I also added a documentation page about the node_modules layout that pnpm creates: https://github.com/pnpm/pnpm/blob/master/docs/symlinked-node-modules-structure.md

[stereokai]

@zkochan That's aweomse of you! Appreciate that.

I'm going now to upgrade to v1 and update here if it solved the issue. Thanks :)