yarn.build
yarn.build copied to clipboard
ojkelly
Build 🛠 and Bundle 📦 your local workspaces. Like Bazel, Buck, Pants and Please but for Yarn Berry. Build any language, mix javascript, typescript, golang and more in one polyglot repo. Ship your bund...
**Is your feature request related to a problem? Please describe.** It would be nice to run this in "watch mode" where it runs a build automatically when files change. **Describe...
**Describe the bug** yarn build --since with commit hash or number of commits are not working Also, it shouldn't build the dependencies. Instead it should do other way round (Let's...
**Describe the bug** --ignore-dependencies are not part of latest build **To Reproduce** Steps to reproduce the behavior: yarn run test --ignore-dependencies **Expected behavior** ignore dependencies **Screenshots** yarn test --ignore-dependencies Unknown...
**Describe the bug** The `--exclude-current` switch causes yarn.build to also exclude the dependencies of the current workspace. This does not appear to be the intended functionality based on the description...
**Describe the bug** I have a yarn workspace, I am trying to use this plugin to bundle and create docker images. When I try to bundle a package to be...
**Is your feature request related to a problem? Please describe.** I have a use case where two commands are used to upload, `upload` and `upload:docker`. They depend on the output...
### Discussed in https://github.com/ojkelly/yarn.build/discussions/102 Originally posted by **icereval** January 4, 2021 **Is your feature request related to a problem? Please describe.** Unable to load the `handler` function from `entrypoint.js` in...
**Describe the bug** I have a workspace with this structure: - packages - core - api api depends on core. when I run yarn bundle inside api, everything works fine,...
**Describe the bug** When there are files that have permissions incompatible with whatever yarn bundle does with them (or yarn/fslib does with them), adding such files to .bundleignore does not...
Hi there, I see today a big difference between running `yarn jest` (38s) in my module and the `yarn test` (2m49s) My guess is that yarn.build start jest in sequential...
