Using pkg.pr.new in the Babel repo

[nicolo-ribaudo]

Hello!

I was looking at pkg.pr.new, and wondering if it would be possible for me to use it in https://github.com/babel/babel/.

We have a few of uncommon setups, so I'm not 100% sure that we would be actually able to do it:

• We have 150 packages, but usually our consumers have at most a couple in their package.json. A pull request can affect package babel-A, the user depends on package babel-B, package babel-B depends on package babel-A. Ideally there would be a way for the user to test the changes even if they are not in the package that they are directly depending on.
• We currently publish both Babel 7 and Babel 8-alpha/beta releases from the same branch. Any pull request can affect either one, the other, or both (usually it's both, but it's probably possible to run some static analysis to tell if it's only going to affect one). Ideally, for each PR we would just publish previews for both versions.
• We don't simply run npm/yarn/pnpm/lerna publish to publish packages. We have a custom plugin for Yarn that basically builds the tarball files (https://github.com/nicolo-ribaudo/yarn-plugin-babel-release-tool), and then Yarn will only upload the tarballs to the registry without actually creating them.
  • This is needed, among other things, because we have custom syntax in package.json that needs to be resolved/replaced at publish time (examples: https://github.com/babel/babel/blob/e02b0ffd871ab07a47947956f39698346b200b1f/packages/babel-core/package.json#L53, https://github.com/babel/babel/blob/e02b0ffd871ab07a47947956f39698346b200b1f/packages/babel-core/package.json#L81)
• On each PR, as part of our CI, we actually already publish all the packages to a local Verdaccio registry. This might simplify things?

Do you see any blocker, or can you point me in the right direction? :)

[Aslemammad]

ok, this message made me happy! i can say finally now :)

for now, pkg.pr.new relies on pnpm pack / npm pack but if you want to upload your own generated tarball (which makes me think, only trusted entities can do in pkg.pr.new, via the whitelist), maybe we can introduce a --tarball option to pkg.pr.new?

i'd love to hear your thoughts.