proposal-shadowrealm
handlebars-helpers
proposal-shadowrealm | handlebars-helpers | |
---|---|---|
19 | 6 | |
1,376 | 2,190 | |
1.2% | 0.2% | |
6.0 | 0.0 | |
12 days ago | 3 months ago | |
HTML | JavaScript | |
- | 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.
proposal-shadowrealm
-
Updates from the 98th TC39 meeting
ShadowRealm: ECMAScript Proposal, specs, and reference implementation for Realms [Stage 3 -> 2].
-
Should you use jest as a testing library?
You can't out of the box. There is an open issue on the Node.js repositoryto let the node:vm module to use the vm's context, but it is still open. It seems that the Node.js core team is interested in fixing this problem by implementing the new ShadowRealm spec, and I think we will make some progress during 2023.
-
Building an Extension System on the Web
ShadowRealms — a successor of the Realms proposals, this API is intended for use cases exactly like plugins or extension systems, providing an option for creating distinct global environments to run the code in. While not entirely secure on its own, this API could provide a strong foundation to build actual extension systems on the Web. That said, 4 years later, the TC39 proposal is currently only at stage 3, not implemented by any browser;
-
Vitest vs Jest benchmarks on a 5 year old real work SPA
With --no-isolate it was 2.8x faster than vitest and 1.7x faster than Jest, but 19 tests failed (see table above). Some people report issues with watch mode when using --no-isolate. So I decided to not pursue it any further. Once the vm module that Vitest relies on supports ESM, or when the amazingly named Shadow Realms are added to JavaScript, we will likely get this performance boost for free without the downsides.
-
Improving Vitest Performance
If ShadowRealms are ever added to EcmaScript (and implemented into V8/Node) they'll allow for a different approach to isolating code that would be faster without the downsides of sharing global.
- Virtualization is not an important enough use case for the web platform to tradeoff ergonomics and possible confusion for web devs, who by and large […] do not understand the separation between the specs. More to the point, they really shouldn't need to.
-
Is there an npm package for perchance?
Eventually I will get around to creating a "proper" package by just grabbing all the JS that is loaded by the code in the iframe, and bundling it up. We really need the ShadowRealm proposal to go through because the perchance engine messes with a lot of JS internals, so it would mess up the rest of your app. Could do it in a WebWorker, but then everything would have to be async.
-
Show HN: Run unsafe user generated JavaScript in the browser
The upcoming JavaScript Shadow Realms proposal looks like it solves a similar problem: https://github.com/tc39/proposal-shadowrealm/blob/main/expla...
- Named Element IDs Can Be Referenced as JavaScript Globals
-
Running user code in the browser (for a leetcode clone)
Browser-based JavaScript doesn't yet have a way to isolate code fully in this manner though there is a new JavaScript feature on the way that would provide this capability. Its called ShadowRealm and would basically give you a new global context to execute code that's completely separate from your main document code.
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?
wtfjs - 🤪 A list of funny and tricky JavaScript examples
deno-puppeteer - A port of puppeteer running on Deno
Pentive - Collaborative Spaced Repetition
koa-hbs - Handlebars templates for Koa.js
vm2-process - Execute unsafe javascript code in a sandbox
regex - An implementation of regular expressions for Rust. This implementation uses finite automata and guarantees linear time matching on all inputs.
vrite - Open-source developer content platform
deno - A modern runtime for JavaScript and TypeScript.
caja - Caja is a tool for safely embedding third party HTML, CSS and JavaScript in your website.
NUnit - NUnit Framework
LavaMoat - tools for sandboxing your dependency graph
lodash - A modern JavaScript utility library delivering modularity, performance, & extras.