node-ffi-napi
handlebars-helpers
Our great sponsors
node-ffi-napi | handlebars-helpers | |
---|---|---|
3 | 6 | |
949 | 2,190 | |
1.9% | 0.6% | |
0.0 | 0.0 | |
26 days ago | 3 months ago | |
JavaScript | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
node-ffi-napi
-
The unexpected return of JavaScript for Automation
I actually came from AutoHotKey as well, specifically for the cross platform support!
I've found the dev experience with nut.js to be worlds ahead of AutoHotKey as well. You get to use a real programming language with proper modules, data structures, first-class functions, asynchrony, and have access to a vast ecosystem of third party libraries and tooling.
Some Windows specific APIs are easier to work with on AHK due to the collection of built-in functions specifically tailored for automation, but everything AHK is still possible with nut.js since you're just writing a node.js script and have access to libraries like https://github.com/node-ffi-napi/node-ffi-napi that can call native system libraries, with a bit more work involved.
-
NPM package ‘ua-parser-JS’ with more than 7M weekly download is compromised
> check out the Web X-Ray repo <https://github.com/mozilla/goggles.mozilla.org/>.
Thanks for example. Peeking a bit under the hood, it appears to be due to transitive dependencies referencing github urls (and transient ones at that) instead of semver, which admittedly is neither standard nor good practice...
FWIW, simply removing `"grunt-contrib-jshint": "~0.4.3",` from package.json and related jshint-related code from Gruntfile was sufficient to get `npm install` to complete successfully. The debugging just took me a few minutes grepping package-lock.json for the 404 URL in question (https://github.com/ariya/esprima/tarball/master) and tracing that back to a top-level dependency via recursively grepping for dependent packages. I imagine that upgrading relevant dependencies might also do the trick, seeing as jshint no longer depends on esprima[0].
I'm not sure how representative this particular case is to the sort of issues you run into, but I'll tell that reproducibility issues can get a lot worse in ways that committing deps doesn't help (for example, issues like this one[1] are nasty to narrow down).
But assuming that installation in your link just happens to have a simple fix and that others are not as forgiving, how is committing node_modules supposed to help here if you're saying you can't even get it to a working state in the first place? DO you own the repo in order to be able to make the change? Or are you mostly just saying that hindsight is 20-20?
[0] https://github.com/jshint/jshint/blob/master/package.json#L4...
[1] https://github.com/node-ffi-napi/node-ffi-napi/issues/143
-
how can c++ code be made available in JavaScript?
NodeJS also has an FFI, where you can build a shared library (not limited to c++) and import it. Node-ffi-addon
handlebars-helpers
-
@lrvick bought the expired domain name for the 'foreach' NPM package maintainer. He now controls the package which 2.2m packages depend on.
https://www.npmjs.com/package/handlebars-helpers, if anyone is curious.
- Node.js packages don't deserve your trust
- NPM package ‘ua-parser-JS’ with more than 7M weekly download is compromised
- BREAKING!! NPM package ‘ua-parser-js’ with more than 7M weekly download is compromised
-
wait what!?
The biggest project that still depends on it is handlebars-helpers, which accounts for about half of the daily downloads. The other half are probably from installs of old versions of other libraries.
-
SBCL: New in Version 2.1.0
I am actually using handlebars along with helpers https://github.com/helpers/handlebars-helpers to automatically generate sql, golang, json and jsx. cl-who is only for markup.
What are some alternatives?
libnut - An Node-API addon for desktop automation
deno-puppeteer - A port of puppeteer running on Deno
JSHint - JSHint is a tool that helps to detect errors and potential problems in your JavaScript code
koa-hbs - Handlebars templates for Koa.js
npm-package-repro
regex - An implementation of regular expressions for Rust. This implementation uses finite automata and guarantees linear time matching on all inputs.
node-jxa - Use your favorite node.js modules (and JS editor) for your Javascript OSX automation scripts
deno - A modern runtime for JavaScript and TypeScript.
NUnit - NUnit Framework
pnpm - Fast, disk space efficient package manager
lodash - A modern JavaScript utility library delivering modularity, performance, & extras.