npm module

[mitica]

Will you publish a npm module?

[armandabric]

👍

[jpravetz]

+1

[rreusser]

Here's an abandoned npm module (no valid gh repo): https://www.npmjs.com/package/node-expression-eval
And a somewhat heavily modified fork: https://www.npmjs.com/package/js-expression

It looks like there's still room for a nice clean mainstream module of this. @silentmatt if it works for you, I'd love to make the following changes and publish to npm:

• fix 10/-1 parity issue (done? see Fix 10/-1 parity error and add tests #42)
• add a linter (looks like one was used, but not explicitly enforced. no strong preference here—main goal is to catch messy things like unused/duplicate variables. I like semistandard since it's zero-config and good enough, but I'm flexible)
• add package.json
• add travis.yml

Bottom line: math.js is like > 400K. jsep isn't without issues and doesn't do super-simple evaluation. Esprima is overkill. So unless there's another candidate for sanitizing and evaluating expressions, seems like there's value in tightening things up and publishing it as a simple, robust expression evaluator.

[silentmatt]

@rreusser That sounds good to me. I pretty much have the same thoughts about semistandard, but I'm not sure about changing from tabs to spaces, only because it eliminates any git blame history. Although that might not be a huge deal, because for an old project there's not a huge amount of activity anyway :)

[rreusser]

Ah, git blame -w? Does that blame while ignoring whitespace? If so, that's pretty cool! http://stackoverflow.com/questions/3945382/git-commit-that-doesnt-override-original-authors-in-git-blame

[silentmatt]

That works for me then. I'll take a look at your pull request and probably merge it tonight after work.

[rreusser]

Cool. Really appreciated! Used it to make a pretty straightforward function plotter: http://rickyreusser.com/plotly-expression-transform/ (source WIP. Unfortunately you need to double-click to get the change to have any effect. Still straightening that out.)

[silentmatt]

Nice 👍 That was actually my original use case for this.

[jonkemp]

Was this ever published to npm?

[silentmatt]

@jonkemp Not yet. I've been working on cleaning up the parser to make it clearer and easier to modify without breaking. I'm about done with that and I'm hoping to get that pushed out this weekend, and then publish it to npm.

[silentmatt]

It's actually been available in npm for a while now, but I'm closing this now that version 1.0.0 is out.