pnpm: Project build error using gulp when dependencies were install using pnpm

In my case I am using gulp-less plugin to build less files to css. I have no problem if the dependencies were installed using npm install, but when using pnpm install I got the following error:

Error: 'tried to require: less'. None found. Make sure one has been installed!

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 21 (11 by maintainers)

Commits related to this issue

refactor: engine requiring No need to resolve the custom path again. Resolves https://github.com/pnpm/pnpm/issues/118 — committed to zkochan/accord by zkochan 7 years ago
fix: engine requiring No need to resolve the custom path again. To be sure that no tooling will be broken, the fix is used only when the original method fails. Resolves https://github.com/pnpm/pnpm/... — committed to zkochan/accord by zkochan 7 years ago
fix: don't preserve symlinks when requiring engine close #275 ref https://github.com/pnpm/pnpm/issues/118 — committed to zkochan/accord by zkochan 6 years ago
fix: don't preserve symlinks when requiring engine (#337) close #275 ref https://github.com/pnpm/pnpm/issues/118 — committed to jescalan/accord by zkochan 6 years ago
fix(deps): update accord to version 0.28 accord@0.28 fixes its engine resolution algorithm. It does not preserve symlinks anymore. It is the wanted behavior because it is the way Node resolves module... — committed to zkochan/gulp-less by zkochan 6 years ago
fix(deps): update accord to version 0.28 (#281) accord@0.28 fixes its engine resolution algorithm. It does not preserve symlinks anymore. It is the wanted behavior because it is the way Node resolv... — committed to gulp-community/gulp-less by zkochan 6 years ago

Most upvoted comments

I looked into accorn and resolve and both seem to work fine.

I see two possible issues here:

you might run the task with a gulp that was installed not via pnpm. You have to install the global gulp with pnpm in order to make this work because gulp has to be executed with the --preserve-symlinks option
if you run it directly. Like node index.js, then you’ll have to run it with the --preserve-symlinks parameter. An important note: the parameter should be at the beginning. So you have to run node --preserve-symlinks index.js

zkochan on Oct 28, 2016