Closed tinesoft closed 11 months ago
@tinesoft I'd love a PR for this 🎉 - I think 0.0.0-e2e.0 should make sense. Let me know if you need any assistance on the PR.
PR in progress. I'm thinking of adding a migration too , to update existing code, do you think it make sense @AgentEnder ?
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.
Current Behavior
Currently, the tools script
tools/scripts/start-local-registry.ts
generated by the@nx/js
library, tries to publish the packages used for e2e testing, with the version1.0.0
https://github.com/nrwl/nx/blob/38fa586b78564f1b9b69eea8b11adbdbe45f3fab/packages/js/src/utils/add-local-registry-scripts.ts#L25
which may cause the publishing to fail because this specific version can already exist on NPM registry (that is proxied by
Verdaccio
, see here https://github.com/nrwl/nx/blob/38fa586b78564f1b9b69eea8b11adbdbe45f3fab/packages/js/src/generators/setup-verdaccio/files/config.yml#L19)Expected Behavior
Instead of trying to publish a
1.0.0
version by default, which is either very likely to already exist on NPM (or will at some point), One solution would be to publish under a different version. For example:0.0.0-e2e
1.0.0-e2e
0.0.0-dev
0.0.0-development
Personally, I would prefer the
0.0.0-e2e
variant, the0.0.0
part reminds of the "in development, or for testing" aspect, and thee2e
would be aligned with the NPM tag name used to publish the package under.GitHub Repo
No response
Steps to Reproduce
Nx Report
Failure Logs
Operating System
Additional Information
I can provide a PR if above "expected behavior" is accepted