Parcel: It can't find modules in the root node_modules (monorepo - Yarn workspaces) - (probably hoisting problem?)

[MatejBransky]

🙋 feature request

It looks like that ParcelJS can't find packages from the root node_modules folder in monorepo with Yarn workspaces.

├── node_modules (modules in this directory are not found)
└── app (with ParcelJS)
    └── node_modules (parcel-bundler is in this folder)

Link to monorepo.

🤔 Expected Behavior

It should solve modules from the root node_modules folder.

😯 Current Behavior

It tries to find directory in the app level but that directory is in the root folder of monorepo.

💁 Possible Solution

Support hoisting shared dependencies.

🔦 Context

I want to build a monorepo with ParcelJS.

My environment:

• Windows 10
• Node.js 10.3.0
• Yarn 1.7.0
  

💻 Examples

Here is the monorepo with this problem.

[MatejBransky]

Ok, it was something weird. After reinstall it suddenly works.

[dbuezas]

Had the exact same problem. After yarn again, it found the modules in the root

[dandv]

This seems still broken. I've run yarn install twice in a monorepo. My web app is in foo. yarn install creates foo/node_modules/.bin/parcel as a symlink to ../../../node_modules/parcel-bundler/bin/cli.js.

I'm running yarn run start in the foo workspace, which runs parcel index.html from foo/package.json. I get the following error:

Error: ENOENT: no such file or directory, open '/home/dandv/myapp/foo/node_modules/parcel-bundler/src/builtins/css-loader.js'

It's clear that Parcel looks for the src files in the foo directory, not in the monorepo's node_modules.

Running the CLI from the monorepo's node_modules fails as well:

~/myapp/foo$ ../node_modules/parcel-bundler/bin/cli.js index html
Server running at http://localhost:1234 
🚨  No entries found.
    at Bundler.bundle (/home/dandv/myapp/node_modules/parcel-bundler/src/Bundler.js:261:17)

../node_modules/.bin/parcel index.html fails with the same css-loader ENOENT error.

What else can I try?

[mauron85]

Same problem here

[mauron85]

But succeeded with using NODE_PATH set to root of mono repo. eg:

NODE_PATH=../../../../../../ parcel build ...

[kontrollanten]

Same issue here.

File structure:

/node_modules/package-a@
/node_modules/parcel
/packages/package-a
/packages/demo

/packages/demo/package.js:

{
  "name": "demo",
  "version": "1.0.0",
  "main": "index.js",
  "license": "MIT",
  "scripts": {
    "lint": "eslint src",
    "start": "parcel src/index.html",
    "build": "parcel build src/index.html"
  },
  "devDependencies": {
    "@babel/core": "^7.3.4",
    "parcel": "^1.11.0"
  },
  "dependencies": {
    "preact": "^8.4.2",
    "preact-leaflet": "1.0.0"
  }
}

Full repo at https://github.com/kontrollanten/preact-leaflet/tree/workspaces

[ianliu]

I was experiencing this problem because I was running parcel index.html from a global parcel installation. After I put that into the start script, and executed with yarn start, it worked.

[holt-mansfield-finaeo]

NODE_PATH=../../ solved the problem for me in my Lerna monorepo

[good-idea]

I came across this issue as well ~ I had parcel installed in one of my project directories, fixed this by removing it from the project and installing it in the root package.json. not ideal but it works!

[resistdesign]

I came across this issue as well ~ I had parcel installed in one of my project directories, fixed this by removing it from the project and installing it in the root package.json. not ideal but it works!

@good-idea Did you run Parcel from the root as well?

[kristiandupont]

@good-idea's solution appears to work for me as well. I still run Parcel from the client folder.