no-context / moo

Optimised tokenizer/lexer generator! 🐄 Uses /y for performance. Moo.
BSD 3-Clause "New" or "Revised" License
817 stars 65 forks source link

Latest version not pushed to npm #110

Closed TheMrZZ closed 5 years ago

TheMrZZ commented 5 years ago

It seems that the last version is not pushed on npm. In the latest npm version, the moo exports are the following:

return {
    compile: compile,
    states: compileStates,
    error: Object.freeze({error: true}),
  }

while in the github repo, they are the following:

  return {
    compile: compile,
    states: compileStates,
    error: Object.freeze({error: true}),
    fallback: Object.freeze({fallback: true}),
    keywords: keywordTransform,
}

The npm repo mentions the existence of built-in moo.keywords, but they are not available via npm i moo - therefore, I think the latest version has not been pushed on npm.

I tried to uninstall / install, update, rebuild etc... Nothing seemed to work. Am I doing something wrong?

tjvr commented 5 years ago

That's correct, we haven't done an NPM release for a while! I was waiting for the API changes to settle down a bit. I should probably do one this week :blush:

TheMrZZ commented 5 years ago

Fine :) thank you for your quick answer!

tjvr commented 5 years ago

This is now published to NPM. Thanks for the reminder! :blush: