Cannot publish package dependent on new version of another package in same changeset

Affected Packages

https://github.com/BitskiCo/bitski-js

• packages/browser
• packages/provider

Problem

When going to publish a changeset, my browser package fails on npm install because it depends on the latest version of my provider package which is part of the same changeset. Can I somehow specify an order in which the package gets published, or are there any other native ways to get this playing nicely?

Proposed solution

???

[chronicIntrovert]

@imthinhvu what is your recipe for publishing packages in topological order with Turborepo? I’d love to borrow that.

There’s nothing magical we’re doing - turborepo should support topological build: https://turborepo.org/docs/core-concepts/pipelines#topological-dependency

What we’ve added is a release npm script that does turbo run build && changeset publish

[Andarist]

We could accept a PR that would publish packages in a topological order. If you don’t intend to prepare a PR for this then I would recommend you to remove your prepare scripts from packages and just run a single monorepo-wide build before you call changeset publish.