Published most recent version to npm

[wenkokke]

This package hasn't been published to npm in a while, and the most recently published version no longer compiles with the recent versions of tree-sitter.

Would be possible to publish a more recent version? What is currently blocking a new version release?

[tek]

@patrickt @maxbrunsfeld

how do we do this?

[414owen]

Looks like @maxbrunsfeld is a collaborator on the npm package.
@wenkokke Do you want to wait for #69, or is your ERROR node non-fatal?

[wenkokke]

We cannot release a new version until tree-sitter does, as we'll need to list the very latest version in our package.json.

[wenkokke]

The new version of tree-sitter is out!
https://github.com/tree-sitter/tree-sitter/releases/tag/v0.20.4

We can publish a release which uses that version now :)

[Thaodan]

The last tagged version doesn't even build anymore (requires 5280130 to build again).

Please tag a new release.

[tek]

@Thaodan I bumped a tag.

With my upcoming rewrite of the project, I will set the version to 1.0 and do regular uploads to npm, as soon as tree-sitter/tree-sitter#3080 is handled.

[tek]

https://www.npmjs.com/package/tree-sitter-haskell

New release is up! Please confirm that it's working 🙂

[Thaodan]

Thank. Help me packaging the grammar with rpm.

[Thaodan]

You tagged 0.15.0 as 0.15.0 and v15.0.0 please remove the first redundant tag.

[tek]

oh hmm maybe the release workflow tagged this as well