prepack
react-18
prepack | react-18 | |
---|---|---|
8 | 140 | |
14,385 | 5,203 | |
- | 0.2% | |
0.0 | 0.0 | |
over 2 years ago | over 3 years ago | |
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.
prepack
-
Ask HN: Interest in a Rust-Inspired Language Compiling to JavaScript?
Hello HN,
I'm considering the development of a new programming language, drawing inspiration from Rust's strengths, with a focus on compiling to JavaScript. Here what I'm considering are some key features:
Strict Type System
Algebraic Data Types
*Unsafe Mode for JS/TS Interaction*: Facilitate direct interaction with existing JavaScript and TypeScript code.
No Null Usage: Option/Result patterns to avoid null.
Trait Implementation
Backend Development Priority: Initially targeting server-side applications.
Efficient Compiler Design: Including features like dead-code elimination and partial evaluation, similar to the approach of Prepack[0] (by Facebook).
I believe this approach could bring significant benefits, especially with recent advancements like Uint8Array and worker threads.
Would this be of interest to the community? Looking forward to your insights and discussion.
[0] https://github.com/facebookarchive/prepack
-
Do any engines or optimizers product TS-specific performance gains?
You can still do optimisations based purely on Javascript semantics. This is similar to the first example you give with dead function elimination, and many minifiers do some amount of this already, but you can take it to some extremes. One example of this is the (no longer maintained) Prepack project from Facebook. The core idea is to evaluate as much Javascript as possible at compile time, with the expectation that the result will probably be smaller (albeit less human readable) than the initial code.
-
[AskJS] Are there JS minifiers that can compress the code by storing and reusing repeating property/method names and strings?
It's no longer maintained, but I think prepack is roughly what you're looking for.
- Can something like typescript or elm be AOT-compiled efficiently?
-
React I Love You, But You're Bringing Me Down
i've had code where it intentionally relied on the wrong behavior (missing hook dependencies) and when I fixed it it caused an unintentional bug (hook fired too often or sometimes infinite rerendering). Yes it is more of a bug in the code rather than React hooks issue but it is also really hard to fix/rewrite. while i'd love to jump on the hype train projects like https://github.com/facebookarchive/prepack and how concurrent mode is still experimental after five+ years doesn't give me a lot of confidence.
-
Memoirs of a lone JavaScript developer PART 2 : Svelte. An awful implementation of an old idea.
Some real examples in JavaScript can be seen on Prepack[2]. Consequently it is natural to wonder whether we can AOT compile components of client side frameworks, to achieve a reduction in the final bundle size, but also to increase application execution speed.
-
React 18 is now in beta
Less or more it’s likely to happen, and could have been expected 2-3 years ago.
Especially with https://github.com/facebook/prepack. They want to eventually ship pre-compiled components rather than React.createElement() to end user
-
Vercel Welcomes Rich Harris, Creator of Svelte
https://github.com/facebook/react/issues/7324
I also think this is why facebook had been investing in `prepack` - https://github.com/facebook/prepack
react-18
- useSyncExternalStoreExports in Zustand source code explained.
-
Simulate global state tradeoffs in React concurrent mode
If you aren't sure why state tearing was a hot topic a few years ago, when React's concurrent mode was first discussed, this github discussion should help: https://github.com/reactwg/react-18/discussions/69.
Tanner Linsley had a great post on twitter that suggested that concurrent rendering was fundamentally at odds with fine-grained reactivity, so to better understand what he was talking about I decided to write this demo.
- A modest request: How do you fetch data in React 18+ WITHOUT a third party dependency?
-
The Sisyphean Quest for Web Performance
Image Source: https://github.com/reactwg/react-18/discussions/37
-
useAsyncState in react, no more unnecessary useEffects.
But it does since React 18.
-
Function props
See this post for more details and an example of an actual memory leak.
-
ELI5, why is ReactDOM.createRoot an improvement over ReactDOM.render?
From the React WG:
- I know my component is re-rendering because a console.log I put in the component is logging in the console. However when I use the inspector to see why it re-rendered, its saying that it didnt re-render. How is this possible?
- Timeout in event handler
-
The current state of CSS-in-JS + React
The React working group is officially advising against using runtime CSS-in-JS.
What are some alternatives?
next-runtime - The Next.js Runtime allows Next.js to run on Netlify with zero configuration
Preact - ⚛️ Fast 3kB React alternative with the same modern API. Components & Virtual DOM.
SvelteKit - web development, streamlined
htmx - </> htmx - high power tools for HTML
denoflare - Develop, test, and deploy Cloudflare Workers with Deno.
petite-vue - 6kb subset of Vue optimized for progressive enhancement
jsx - The JSX specification is a XML-like syntax extension to ECMAScript.
react-query - 🤖 Powerful asynchronous state management, server-state utilities and data fetching for TS/JS, React, Solid, Svelte and Vue. [Moved to: https://github.com/TanStack/query]
realworld - SvelteKit implementation of the RealWorld app
React - The library for web and native user interfaces.
rfcs - RFCs for changes to Ember
zustand - 🐻 Bear necessities for state management in React