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

Publish npm package #10183

Open
Zaczero opened this issue Mar 30, 2024 · 6 comments
Open

Publish npm package #10183

Zaczero opened this issue Mar 30, 2024 · 6 comments

Comments

@Zaczero
Copy link
Contributor

Zaczero commented Mar 30, 2024

Description

It would be nice if iD published its own npm package.

Screenshots

No response

@matkoniecz
Copy link
Contributor

Why? What would be the benefit?

@Zaczero
Copy link
Contributor Author

Zaczero commented Apr 5, 2024

Easier integration, Rapid already does that and I like it more. The versions are nice and you can easily lock specific ones. It's really not that hard to publish a package and it can be automated. Ease of life.

@matkoniecz
Copy link
Contributor

It definitely cannot be fully automated and you have one more part to upkeep (may be worth it overall, but denying that costs exists is not helpful)

@Zaczero
Copy link
Contributor Author

Zaczero commented Apr 5, 2024

I don't think you do. It's literally setup-and-forget.

https://github.com/marketplace/actions/automated-releases-for-npm-packages
https://github.com/marketplace/actions/publish-to-npm

Could you please be more specific? What part would there be to upkeep?

From the maintainer perspective, clear package version numbers are night-and-day easier to work with. Git commit hashes are pretty meaningless. While they are acceptable for projects of smaller size, of closed projects, I don't think it's appropriate for a project of this size to keep using git hashes.

I have additionally prepared an AI-generated response which deep dives into pros and cons of both solutions: https://g.co/gemini/share/f5179a748329 (since this kind of knowledge is well-known to the internet). The "When to Choose Which" section is most applicable here.

@matkoniecz
Copy link
Contributor

matkoniecz commented Apr 5, 2024

It's literally setup-and-forget.

nothing requires no maintenance (npm recently was sending me some email demanding attention about my test package, I would need to process them if it would be a real project). And I think that you are not going to claim that setup has zero costs.

I bet that GPTchat can explain this if you are considering it as useful source (though linking AI-generated response is quite pointless).

@Zaczero
Copy link
Contributor Author

Zaczero commented Apr 5, 2024

npm recently was sending me some email demanding attention about my test package, I would need to process them if it would be a real project

I really wish I could address this specific example but there is nothing specific about it. Just "some email" that was sent to you. Perhaps we misunderstood each other, here's what I mean by asking for a specific example: https://www.thefreedictionary.com/specific. For example, how did this email affect your ability to push package updates? Can you attach a copy of that email?

And I think that you are not going to claim that setup has zero costs.

I never claimed so. You are now suggesting something completely abstract. I claimed "It's literally setup-and-forget". The setup has cost, the maintenance does not (in practical terms, not theoretical).

though linking AI-generated response is quite pointless

It's a great internet-knowledge summarization tool. It's like Google but on steroids. It's super useful if you are exploring some new topics to you. If you could clarify what's pointless about it, I could perhaps give you a more-suited answer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants