[wip] include npm tarballs in dist

[bollwyvl]

Hooray continuing to publish on npm and not build another walled garden!

This builds and includes the npm tarballs in the dist artifact... these can be directly uploaded with (npm|lerna) publish (or whatever, i always forget), and has the advantage of what is published being exactly what was tested, instead of whatever happens to be on a developer's box at the time. I've learned this the hard way a few times 😊 .

• follow-on to add multi-platform install smoke test #68 (comment)

[bollwyvl]

Hooray 🟢 .

Actually had a look at the dists (ha): of note, the npm tarballs don't include LICENSE in package.json/files, but seems out of scope for this... and indeed, neither does lab core. We need to deal with that, as developers forget and then downstream package managers 😉 have to pick up the shiny pieces (looking at you, rust/go/coursier).

[jtpio]

Nice, thanks again @bollwyvl for this, this is great!

[bollwyvl]

Thanks for the speedy review... Have already adopted this approach over on lsp!

[jtpio]

Thanks, I will most likely adopt it in other repos too!

[bollwyvl]

So the bigger question... Is it worth it to start a jupyter/test-extensions action? Probably needs a discussion over on compass is something...

[jtpio]

An issue on the team compass sounds good 👍

It would be nice to have this as some kind of reusable component yes. Something that could complement other aspects of testing such as jupyterlab/frontends-team-compass#77