Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ignore npm registry when using local packages #21

Closed
d-roak opened this issue Jun 19, 2024 · 0 comments · Fixed by #41
Closed

Ignore npm registry when using local packages #21

d-roak opened this issue Jun 19, 2024 · 0 comments · Fixed by #41
Labels
bug Something isn't working external contributors Open for external contributors

Comments

@d-roak
Copy link
Member

d-roak commented Jun 19, 2024

There is a bug when installing packages defined as being local, npm tries to fetch that version from npm registry. Therefore, our ci fails when we do new releases.

E.g. https://github.com/topology-foundation/ts-topology/actions/runs/9576039797/job/26401878399

"dependencies": {
"@topology-foundation/crdt": "file:../../packages/crdt",
"@topology-foundation/network": "file:../../packages/network",
"@topology-foundation/node": "file:../../packages/node",
"@topology-foundation/object": "file:../../packages/object",

@d-roak d-roak added bug Something isn't working good first issue external contributors Open for external contributors labels Jun 19, 2024
@d-roak d-roak moved this from Triage to 🗃️ Backlog in Project Management Jul 5, 2024
@github-project-automation github-project-automation bot moved this from 🗃️ Backlog to 🏆 Done in Project Management Jul 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working external contributors Open for external contributors
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant