proposal-shadowrealm
node
proposal-shadowrealm | node | |
---|---|---|
19 | 930 | |
1,376 | 103,799 | |
1.2% | 0.7% | |
6.0 | 9.9 | |
13 days ago | 6 days ago | |
HTML | JavaScript | |
- | 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.
node
-
How to Add Firebase Authentication To Your NodeJS App
Basic knowledge of Node.js and its environment setup. If you don't have Node.js installed on your system, make sure you download and install it from the official Node.js website.
-
Part 2: Setting Up Your Node.js Environment
Node.js can be easily installed from its official website. Depending on your operating system, you can choose the Windows, macOS, or Linux version. Node.js packages come with npm (Node Package Manager), which is essential for managing dependencies in your projects.
-
Announcing Node.js 22.0.0: What’s New and Why It Matters
To get started with Node.js 22.0.0, you can download the latest version from the official Node.js website. For those upgrading from an older version, it is recommended to test your existing applications for compatibility with the new release, particularly if you are using native modules or rely heavily on third-party npm packages.
-
How to Make a VS Code Extension Using TypeScript: A Step-by-Step Guide
Node.js (version 10 or higher)
-
Getting Started with Next.js: Part 1 - Setting Up Your Project
Before we start, ensure that you have Node.js installed on your computer. This is necessary because we will use Node's package manager (npm) to create our Next.js project. If you need to install Node.js, you can download it from the official Node.js website.
-
How to create a react project from scratch
Before starting a new project in react, you need to make sure that you have NodeJS install on your system. You can download the latest version of node at https://nodejs.org. Follow the instructions on the node website to do the installation.
-
The Ultimate Node.js Cheat Sheet for Developers
Installing Node.js: Download and install Node.js from nodejs.org. Choose the version recommended for most users, unless you have specific needs that require the latest features or earlier compatibility.
- Node 22.0.0 Just Released
-
Google Authentication in Nodejs using Passport and Google Oauth
You should have Nodejs installed on your laptop and if not, check the Node.js official website, and download/ install the latest and stable release.
-
Getting an error when using @ValidateNested decorator in NestJs
[Nest] 60017 - 04/22/2024, 1:07:48 PM ERROR Error [ERR_INTERNAL_ASSERTION]: Error: BSONError: Cannot create Buffer from undefined at Object.toLocalBufferType at Object.toHex at ObjectId.toHexString at ObjectId.inspect at ObjectId.[nodejs.util.inspect.custom] at formatValue (node:internal/util/inspect:782:19) at formatProperty (node:internal/util/inspect:1819:11) at formatArray (node:internal/util/inspect:1645:17) at formatRaw (node:internal/util/inspect:1027:14) at formatValue (node:internal/util/inspect:817:10) This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
What are some alternatives?
wtfjs - 🤪 A list of funny and tricky JavaScript examples
Svelte - Cybernetically enhanced web apps
Pentive - Collaborative Spaced Repetition
widevine-l3-decryptor - A Chrome extension that demonstrates bypassing Widevine L3 DRM
vm2-process - Execute unsafe javascript code in a sandbox
source-map-resolve - [DEPRECATED] Resolve the source map and/or sources for a generated file.
vrite - Open-source developer content platform
sharp-libvips - Packaging scripts to prebuild libvips and its dependencies - you're probably looking for https://github.com/lovell/sharp
caja - Caja is a tool for safely embedding third party HTML, CSS and JavaScript in your website.
nodejs.dev - A redesign of Nodejs.org built using Gatsby.js with React.js, TypeScript, and Remark.
LavaMoat - tools for sandboxing your dependency graph
hashlips_art_engine - HashLips Art Engine is a tool used to create multiple different instances of artworks based on provided layers.