proposal-shadowrealm
tldr
proposal-shadowrealm | tldr | |
---|---|---|
19 | 262 | |
1,376 | 48,406 | |
1.2% | 0.8% | |
6.0 | 10.0 | |
12 days ago | 6 days ago | |
HTML | Markdown | |
- | GNU General Public License v3.0 or later |
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.
tldr
-
Ask HN: Is there a GUI for bash shell?
Maybe this already helps: https://github.com/tldr-pages/tldr
-
Try / Ripgrep in Y Minutes
A bit of an aside, but I really like "guides to things we otherwise take for granted". So few man pages are built around example use cases, but those are often what make the case for a tool!
A similar spirit to projects like https://github.com/tldr-pages/tldr/ , but this has a lot more useful detail.
The ripgrep author has a blog post on performance and benchmarking that is an interesting read in itself: https://blog.burntsushi.net/ripgrep/
- Serving my blog posts as Linux manual pages
- Tldr: Simplified and community-driven man pages
- Tell HN: My Favorite Tools
-
Should you add screenshots to documentation?
Looks like bro pages is archived and they recommend https://github.com/tldr-pages/tldr or https://github.com/cheat/cheat
-
Have i made my own linux distro? ^_^
a very excellent tool to grab is TLDR https://tldr.sh/
- fixedIt
-
Day 2 - Basic navigation
And that's why tldr is such a powerful tool! You can easily install it with sudo apt install tldr or follow this demo.
- Tldr Pages
What are some alternatives?
wtfjs - 🤪 A list of funny and tricky JavaScript examples
cheat - cheat allows you to create and view interactive cheatsheets on the command-line. It was designed to help remind *nix system administrators of options for commands that they use frequently, but not frequently enough to remember.
Pentive - Collaborative Spaced Repetition
tealdeer - A very fast implementation of tldr in Rust.
vm2-process - Execute unsafe javascript code in a sandbox
cheat.sh - the only cheat sheet you need
vrite - Open-source developer content platform
zsh-autosuggestions - Fish-like autosuggestions for zsh
caja - Caja is a tool for safely embedding third party HTML, CSS and JavaScript in your website.
navi - An interactive cheatsheet tool for the command-line
LavaMoat - tools for sandboxing your dependency graph
fish-shell - The user-friendly command line shell.