Integrate pkg.pr.new

[ritz078]

Has anyone considered adding https://github.com/stackblitz-labs/pkg.pr.new to this repo. It will be an immense improvement in PR reviews as anyone will be able to test the PR build in their project and ensure everything is working fine. Much easier than the whole process of linking package which becomes tricky if you don't use the same package manager.

We use this internally in our internal projects and it has been incredibly useful.

[snowystinger]

Thanks for the resource. I've not heard of this before. Definitely interested to look into it more.

[snowystinger]

If we did pkg.pr.new, we'd likely want to set up our own hosting/instance for it, they only keep artifacts around for 6months, and we've had it useful before to be able to go back farther.

We could also consider a hybrid approach, still do nightlies on main, but do pkg.pr.new for PRs possibly.

[snowystinger]

consolidating comments #8410 (comment)

[snowystinger]

where does pkg.pr.new publish to? as in, where do my zipped packages get stored for the pkg.pr.new urls to know about them? does it cost anything? and what does temporary mean? can the amount of time the links work for be adjusted?

• we have a registry for it (cloudflare R2) that we store everything there. we do not publish anything to npm.
• no it does not cost anything for the users.
• the goal of pkg.pr.new is to enable preview packages, which means release cycles but for testing purposes! so temporary in this context means that since everything is for preview & testing, it’d be removed after a 6 month timeline window.

[snowystinger]

We will need to verify that there are no tokens needed for the setup of pkg.pr.new