Is there a limit to packages built in the CI?

[caseybaggz]

Hello! I have a mono-repo using Yarn Berry Workspaces with Pnp and we have successfully been using the ci.json config for the past year. However, our repo now has 4 workspaces we need to build but our config only continues to build the original three.

Question

Is there a limit to how many packages the ci.json file will build (like three)?

I can't seem to find any information on that but the ci docs are kind of minimal in general.

[lbogdan]

Can you please share the repository?

[lbogdan]

No worries, glad that it works! 🙂

[caseybaggz]

Ah...I think I found the possible issue (don't know if it's a bug or intended but should probably mention it in the CI docs).

The React custom sandbox had no other workspace npm packages in the deps list. All the other custom sandboxes did. So it's as if the ci.json job just completely ignored replacing the workspace deps in general if one existed.

Working Example:

1. Run ci.json (CI)
2. CI starts building all workspaces
3. CI uses sandbox defined
4. CI adds all workspace packages in the custom sandbox as npm deps
5. It works

Bug Example (pre-defined workspaces):

1. Run ci.json (CI)
2. CI starts building all workspaces
3. CI uses sandbox defined
4. CI adds all workspace packages in the custom sandbox as npm deps
5. CI notices npm packages already exist in custom sandbox and ingores step & exit

☝️ I feel as though step 5 of the Bug example should instead do this...
5. CI notices npm packages already exist in custom sandbox and replaces version with commit
6. CI adds any remaining missing workspace packages as npm packages to deps list
7. it works

[lbogdan]

This is indeed expected behavior. If some of the built packages already exist in dependencies, we only replace those, and also all their dependencies on other built packages. As an example:

• repository builds packages foo and bar, foo depends on bar
• sandbox only has foo in dependencies
• we only replace foo with foo-build in the sandbox, and also bar with bar-build in foo-build's dependencies

If you want to also have bar in the resulting sandbox's dependencies, you should add it to the source sandbox's dependencies.

[caseybaggz]

Ahhhh, yeah, that should definitely be on the docs ci page somewhere. If the website is an open-source repository, I don't mind updating that. Just let me know. 👍

[lbogdan]

We recently moved them to a separate, (for now) private repository, but if you want to make a PR for the initial version, which, for CI, we just copied over, we can probably apply it.

[aj-foster]

Psst... Hi Casey 👋🏼

[caseybaggz]

@aj-foster Hello! 👋