Only run npm pack if there are public packages in workspace

[fcollonval]

Fix issue seen in jupyterlab-contrib/jupyterlab-favorites#15

[jtpio]

Fix issue seen in jupyterlab-contrib/jupyterlab-favorites#15

Shouldn't the top-level package.json in https://github.com/jupyterlab-contrib/jupyterlab-favorites be picked up since it does not have a private field?

Usually the extension should also be published to npm by default, so maybe this indicates there is an issue somewhere else?

[fcollonval]

The releaser picked up the top repo correctly. But as a workspace listing the ui-test was present it also tries to list all public packages part of the workspace requiring packaging. However in that specific case there is no public package in the workspace; hence the bug (it runs npm pack with no argument in a folder that is not a npm package) that this PR fixes.

[jtpio]

OK thanks for providing the extra context.

Maybe this case should be put under tests? Or we add a print / info statement if workspaces is defined but no packages will be published? In case there is a misconfiguration issue.

Otherwise the change looks good 👍

[fcollonval]

we add a print / info statement if workspaces is defined but no packages will be published?

Thanks for the suggestion @jtpio; I added a log message in ee81639

[jtpio]

Thanks!