Use binary of dependency

[matzeeable]

Imagine the following workspace structure:

- packages/
  - webpack-config/
    - package.json
      name: @my-monorepo/webpack-config
      devDependencies: webpack-cli
  - my-frontend/
    - package.json
      name: @my-monorepo/my-frontend
      devDependencies: @my-monorepo/webpack-config
      scripts:
        - yarn webpack

Unfortunately, my frontend package cannot access the webpack cli:

Usage Error: Couldn't find a script named "dotenv".

Is it somehow possible to access the Webpack CLI anyway without adding webpack-cli as a dependency to my frontend?

Related: #2825, #2784

EDIT: I want to avoid something like g:webpack as described here: https://yarnpkg.com/getting-started/qa#how-to-share-scripts-between-workspaces

[arcanis]

EDIT: I want to avoid something like g:webpack as described here: https://yarnpkg.com/getting-started/qa#how-to-share-scripts-between-workspaces

Well, that's the prescribed answer 😄 apart from that, you could make a plugin that defines yarn webpack as a proper command forwarded to your binary, using the Yarn APIs. In fact it could probably generalized, like a plugin-global-commands; that would be interesting to see 🤔

[matzeeable]

Yes, that is indeed the right answer because that is how it works.

Why do I want to avoid this? The chain of a lot of yarn commands becomes very "slow" as yarn uses a custom script interpreter (perhaps this is also relevant: #1731 (comment)):

yarn build -> yarn g:webpack -> yarn webpack looks like it opens three shell sessions and the overhead until webpack is reached is about ~1.5s (using yarn set version from sources). For me, this time would not be a problem at the moment, but it will be clearly noticeable in our CI.

In fact it could probably generalized, like a plugin-global-commands; that would be interesting to see 🤔

Yeah, something like this would be great. How could a plugin like this work exactly? How can commands be defined? Do you have something like a "Getting started" for plugins? I cannot find it right now in the docs. 😊

[merceyz]

You can use the -T flag from yarn run to run binaries from the root, that gives you the chain yarn build -> yarn run -T webpack

berry/packages/plugin-essentials/sources/commands/run.ts

Lines 47 to 49 in bef2039

	// This flag is mostly used to give users a way to configure node-gyp. They
	// just have to add it as a top-level workspace.
	topLevel = Option.Boolean(`-T,--top-level`, false, {hidden: true});

Yeah, something like this would be great. How could a plugin like this work exactly? How can commands be defined? Do you have something like a "Getting started" for plugins? I cannot find it right now in the docs. 😊

Here are the relevant docs:

• https://yarnpkg.com/features/plugins
• https://yarnpkg.com/advanced/plugin-tutorial
• https://yarnpkg.com/advanced/plugin-tutorial#adding-commands

[merceyz]

See my answer to your question at #2784 (comment)