[V2] Fails to auto-install packages when using yarn workspaces.

[SantoJambit]

🐛 bug report

When you have a monorepo with yarn set up, parcel tries to auto-install dependencies into the root package.json.
This even happens when I run parcel from the package folder.

🎛 Configuration (.babelrc, package.json, cli command)

Aside from the workspaces configuration:

{
...
  "workspaces": {
    "packages": [
      "packages/*"
    ],
    "nohoist": [
      "**/parcel",
      "**/parcel/**",
      "**/@parcel/**"
    ]
  },
...
}

There is only one .parcelrc file

{
  "extends": "@parcel/config-default",
    "transformers": {
      "*.{jpg,png,svg}": [
        "@parcel/transformer-raw"
      ]
    }
}

🤔 Expected Behavior

It should work with monorepos.

😯 Current Behavior

Installing @parcel/transformer-posthtml...
@parcel/package-manager: yarn: Running this command will add the dependency to the workspace root rather than the workspace itself, which might not be what you want - if you

🔦 Context

I have a simple monorepo with one backend and one frontend package. The frontend package has parcel as dependency.
I was on 2.0.0-nightly.506 before, where nothing needed to be installed by parcel, so I never had the issue then.

I tried manually installing the items, but it still detects them as missing and tries to auto-install them again.

💻 Code Sample

🌍 Your Environment

Software	Version(s)
Parcel	2.0.0-nightly.596
Node	15.8.0
npm/Yarn	yarn 1.22.4
Operating System	Ubuntu 18.04

[mischnic]

This should probably not be the project root (= workspace root)

parcel/packages/core/core/src/loadParcelPlugin.js

Lines 75 to 76 in 36035d8

	// Resolve from project root if not in the config's dependencies.
	resolveFrom = path.join(options.projectRoot, 'index');

This would also explain why the resolution fails after installing manually

If there's a .parcelrc in the project, it should be relative to that. If there isn't, 🤷‍♂️

[SantoJambit]

Wow, that was a quick response!

[jeffpeck10x]

This seems to still be happening on 2.0.0-nightly.607+d77a5647

I downgraded to the last version that I know that this was not an issue - 2.0.0-nightly.573 (i.e. it might be working on later version, but this was the last version that was working for me prior to updating to the latest)

[mischnic]

So the workaround here is installing Parcel in the monorepo root.

The problem is that isn't a simple solution for determining what to use instead of the project root here: #5854 (comment)

[SantoJambit]

Wouldn't it be possible to check the package.json dependencies if it has parcel installed and if so, install the dependencies there?

[jeffpeck10x]

The latest @nightly, even with parcel in the monorepo root, does not work. The only current solution for me is staying parcel@2.0.0-nightly.573

[mischnic]

I meant:

1. Install parcel in the root
2. run Parcel with --no-autoinstall
3. Install all of the requested packages in the root

All other solutions might break due to hoisting or because Yarn 2 enforces declared dependencies

[toastal]

Like @jeffpeck10x, I've been stuck on an old version for quite some time using Yarn v1 workspaces. The version that works for me is slightly newer @ 2.0.0-nightly.579. I haven't tried moving parcel up to the root, but this isn't a fix I want to do as I want the various packages's dependencies siloed. I tried upgrading to the latest nightly today, but it's still not working. I do have a .parcelrc(.json) file in the root of the problematic workspace (other workspaces are using Webpack).