Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Publishing to NPM
See original GitHub issueCould you please start publishing tree-sitter-elixir to NPM, like e.g. tree-sitter-ruby or tree-sitter-python do ?
Reasons are pretty obvious (for me):
- versioning / change control for free. There was a change around 2 weeks ago that broke Node bindings. With NPM, it wouldn’t be a problem. Without, I had to spend a couple of hours to debug things.
- convenience
In principle, I can help with this, if needed.
Issue Analytics
- State:
- Created a year ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Creating and publishing scoped public packages - npm Docs
Publishing scoped public packages ; On the command line, navigate to the root directory of your package. cd /path/to/package ; To publish your...
Read more >How to publish packages to npm (the way the industry does ...
The way the industry publishes (and updates) packages. · Run tests (if there are any) · Update version in package.json according to Semver...
Read more >How to Publish Your First npm Package | by Bret Cameron
How to Publish Your First npm Package · Install npm · Choose a package name · Initialise your project · Initialise Git ·...
Read more >How to Publish a Package on npm - MakeUseOf
How to Publish a Package on npm · Step 1: Installing NodeJS · Step 2: Creating an npm Account · Step 3: Initializing...
Read more >How To Create And Publish Your First NPM Package - YouTube
It may seem daunting to create your first NPM package, but it is surprisingly easy to do so. In this video I will...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The question is what versioning we should follow. Currently pretty much all packages I looked at align the version with the tree-sitter version, but I think this has issues. For someone using the AST, we should bump the major version whenever the AST changes, and not try to mirror the tree-sitter versioning. There is more discussion in https://github.com/tree-sitter/tree-sitter/discussions/1768, however there’s no standardization yet, as far as I can see.
Sidenote: when pointing the dependency to GitHub, it’s a good idea to specify the SHA.
Related to #35.
Hey @jonatanklosko likewise with the late reply 🙈
I wasn’t as familiar with NPM at the time, I now realise I can just use a git dependency, which seems to be what cursorless is doing anyway. Feel free to disregard.