dcard/yarn-plugins

Yarn plugins for Yarn 2.

yarn-plugins

Yarn plugins for Yarn 2.

Plugins

• yarn-plugin-changed - List and run a command on changed workspaces and their dependents.
• yarn-plugin-docker-build - Build a Docker image for a workspace.
• yarn-plugin-tsconfig-references - Update references in tsconfig.json when adding/removing workspaces.

License

MIT

yarn-plugins's Issues

[docker-build] how does it integrate with build-push-action?

How would I use this plugin in CI/CD together with https://github.com/docker/build-push-action?

copy doesn't work (for folders)

E.g. this fails yarn docker build --copy client/corp.js @corp/api with YN0001: │ Error: Invalid filename: "client/corp.js"

I want to copy a folder into the dockerfile. Any escape hatch around??

yarn-plugin-changed git-range command with only one commit hash

Hello,
I'm using your plugin and I wanna see changes for one commit hash instead of a git range, I've tried this:

yarn changed list --git-range 6032ef1a9ac712c6ce64714cd6589a06eb48df00..6032ef1a9ac712c6ce64714cd6589a06eb48df00 --json

using the same hash but give me no changes, it is possible?

Use without workspace

How can I use this without using workspaces (i.e. without monorepo)?

[docker-build] Unnecessary package.json included

package.json of workspaces that are not dependencies are included in docker image. Wondering if this is avoidable?

Add --cached options for staged changes in local branch

Hi, love this plugin for git-ops based monorepo, and I'd love to have greater flexibility in using this on a pre-commit git hook. There should be a --cached option that gets sent to git-diff to look at staged changes instead of unstaged changes.

Can I use the cache file to automatically determine what needs to be modified?

Similar to lerna publish or ultra-runner, write the built information into the cache file, and then run the command again according to the cache file to calculate which module changes need to be rebuilt

Plugin crashes with TypeError in Yarn v3

Stack:

$ yarn changed list
➤ YN0001: TypeError: Cannot read property 'length' of undefined
    at C:\Repositories\node-zwave-js\.yarn\plugins\@yarnpkg\plugin-changed.cjs:5:1737
    at Array.filter (<anonymous>)
    at listWorkspaces (C:\Repositories\node-zwave-js\.yarn\plugins\@yarnpkg\plugin-changed.cjs:5:1656)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async C:\Repositories\node-zwave-js\.yarn\plugins\@yarnpkg\plugin-changed.cjs:5:2770
    at async Function.start (C:\Repositories\node-zwave-js\.yarn\releases\yarn-3.0.0-rc.6.cjs:273:2287)
    at async l.execute (C:\Repositories\node-zwave-js\.yarn\plugins\@yarnpkg\plugin-changed.cjs:5:2665)
    at async l.validateAndExecute (C:\Repositories\node-zwave-js\.yarn\releases\yarn-3.0.0-rc.6.cjs:197:620)
    at async _n.run (C:\Repositories\node-zwave-js\.yarn\releases\yarn-3.0.0-rc.6.cjs:209:1846)
    at async _n.runExit (C:\Repositories\node-zwave-js\.yarn\releases\yarn-3.0.0-rc.6.cjs:209:2013)

docker buildx support

Would be really cool if this plugin supported buildx so that I could build my images for different architectures the easy way!

[docker-build] on Github Actions; cannot find layer

When using this as described in the README on Github Actions:

 Step 13/22 : COPY --chown=nextjs:nodejs packs ./
failed to export image: failed to create image: failed to get layer sha256:3eacc4e8c190bdfa7d007d4196b1a57b82c5c04ee113491787a9e1d94a76db20: layer does not exist
➤ YN0001: Child docker reported an error
➤ YN0001:   Exit Code: 1
➤ YN0000: Failed with errors in 1m 5s

However, this works great locally.

Any idea why this might be?

[docker-build] How to use with docker-compose?

Since this is invoked via yarn, how do you make docker-compose use it?

Differences between prepack in plugin-docker-build compared to yarn workspace pack

Hi, thank you for the plugins!

We are using plugin-docker-build in rafiki

When I check out the main branch of that repo and run yarn install and yarn docker build backend -t rafiki-backend, I get the following error:

➤ YN0000: ┌ Pack workspace backend
➤ YN0036: │ Calling the "prepack" lifecycle script
➤ YN0001: │ UsageError: Couldn't find knex@npm:0.21.19 [aa597] in the currently installed PnP map - running an install might help
    at fl.findPackageLocation (/Users/raphael/workspace/rafiki/.yarn/releases/yarn-3.0.2.cjs:543:4529)
    at /Users/raphael/workspace/rafiki/.yarn/releases/yarn-3.0.2.cjs:289:1296
    at Function.from (<anonymous>)
    at XI (/Users/raphael/workspace/rafiki/.yarn/releases/yarn-3.0.2.cjs:289:1040)
    at UW (/Users/raphael/workspace/rafiki/.yarn/releases/yarn-3.0.2.cjs:289:1621)
    at jQe (/Users/raphael/workspace/rafiki/.yarn/releases/yarn-3.0.2.cjs:288:2882)
    at async /Users/raphael/workspace/rafiki/.yarn/releases/yarn-3.0.2.cjs:288:2135
    at async Ft.mktempPromise (/Users/raphael/workspace/rafiki/.yarn/releases/yarn-3.0.2.cjs:177:62506)
    at async VI (/Users/raphael/workspace/rafiki/.yarn/releases/yarn-3.0.2.cjs:288:2075)
    at async HW (/Users/raphael/workspace/rafiki/.yarn/releases/yarn-3.0.2.cjs:288:4104)

However, when I try to manually run the pack using yarn workspace backend pack, the pack succeeds without an error. This suggests that there is some difference between the yarn context in use by the plugin, and the yarn context that is used normally. Do you know what it could be?

[docker-build] using devDependencies

Hey, nice work with docker-build!

I'd really like to use it for our Nestjs project, but I have a few devDependencies that are required for the build stage. Is there any way to include these in one of my build steps, perhaps by loading two lockfiles, on with devDependencies and one without?

Best regards,
Malcolm

[docker-build] Fails to build TypeScript projects...

...due to not copying devDependencies; normally one use multi-stage builds, so to include devDependencies by default doesn't mean one has to let the runner have those too; instead yarn install --prod can be used in the runner, without copying node_modules/ from the builder.

#21 — also relevant.

Feature Request (changed): Ignore changes to certain workspaces when computing dependency tree

Thanks for the awesome plugins!

This is a feature request for the changed plugin for ignoring certain workspaces so that changes to any of those workspaces doesn't trigger any dependent workspaces to be included in the changed output.

We have a monorepo with a structure like this:

packages
- build-utils
- frontend-1 (has devDependency on build-utils)
- frontend-2 (has devDependency on build-utils)

We are using yarn changed to determine which workspaces should have their tests run. When someone modifies build-utils, the frontend-* workspaces have their tests run because they have a development dependency on it. In this scenario, the fact that the build of frontend-* workspaces passed is good enough for us; we don't need to run tests.

It would be useful to be able to exclude certain workspaces from the dependency tree computation, in any of these ways:

• Allow a --ignore <workspace> option which means "ignore changes made to these workspaces when computing dependents"
• Allow a --production flag which means "ignore development dependencies when computing dependents"

[yarn-plugin-tsconfig-references] allow customizing tsconfig file name

I work on projects with multiple tsconfig files in each package, and would references to go into non-default tsconfig

Access to unpacked folders with docker-build

Hopefully there's an easy answer to this!

I'm trying to use the docker-build plugin on Yarn 3 -- it works really well, with the exception of one big issue. The workspace in question is a package, which means that it has files defined under package.json. Because of that, yarn pack returns only those files, meaning that I'm unable to do anything outside of manifests and the files in the package itself.

What I'm hoping for is a way to copy in the original code from my workflow; I can make a minimal docker image of dependencies with the excellent existing manifests folder, but I can't do anything that requires the source code, including building and testing. Any advice is appreciated.

--copy seemed like a possible answer here (though I don't think it's how it's intended to work), but that returns an "Invalid filename" error when passed a folder.

[docker-build] Recreates files, causing docker cache busting

Files are recreated when doing a docker build command, meaning that the yarn install step always happens, despite no changes to the source files.