ts-monorepo
inferno
ts-monorepo | inferno | |
---|---|---|
14 | 10 | |
1,434 | 16,014 | |
- | 0.1% | |
8.5 | 8.4 | |
5 days ago | about 1 month ago | |
TypeScript | 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.
ts-monorepo
-
[AskJS] Is there a silver bullet for consuming Typescript libraries in a Monorepo?
1. Linking libs with tsconfig paths. This approach involves setting a tsconfig.json paths object which maps the package name, to the local filesystem location. Eg. "paths": {"@org/lib":"../libs/lib"} - Nx uses this approach for their Integrated Monorepo configuration https://nx.dev/tutorials/integrated-repo-tutorial https://github.com/NiGhTTraX/ts-monorepo.
-
Recommendations for lerna/yarn mono repos?
FYI I tried renaming packages/bar/index.ts to index.js and adding allowJs: true in its tsconfig.json and tsconfig.build.json and everything works as expected.
-
Structuring packages and working with workspaces
Give https://github.com/NiGhTTraX/ts-monorepo a try :) It uses path aliases to map your imports to the source code inside the monorepo.
-
How to use npm workspace with create-react-app and typescript?
Make sure you've copied the jest craco config and that you've set up path aliases accordingly.
-
Handling TypeScript in a monorepo
You can check https://github.com/NiGhTTraX/ts-monorepo.
-
You might not need TypeScript project references
FWIW https://github.com/NiGhTTraX/ts-monorepo works in a similar way by using path aliases instead. The result is the same (imports resolve to monorepo source code), but this approach doesn't prevent you from publishing any of the packages (check the repo and the linked docs for more details).
-
using references in tsconfig.json to point to library code
You didn't give an example of how your imports look, but I'm assuming you're trying to use absolute imports for the lib files like from 'lib/src/...'. Project references don't rewrite the imports in any way, they just optimize the builds by caching referenced projects. You'll want to use path aliases instead. Feel free to check out https://github.com/NiGhTTraX/ts-monorepo for full examples.
-
[Question] Setting up monorepo: How be able to debug and build in the same project without changing package.json?
You can use two tsconfig.json files and in one of them configure path aliases to map your package names to the source code, effectively "overriding" package.json#main. You can find examples here https://github.com/NiGhTTraX/ts-monorepo.
-
Monorepo with Yarn Workspaces + TS + Docker Templates
Here is one I liked that is very basic, although I removed lerna from it personally. Shows examples of package sharing and a bunch of popular libraries. Next not nuxt but you get the idea. https://github.com/NiGhTTraX/ts-monorepo
- How do you manage TypeScript monorepos?
inferno
-
Inferno 8.2.3 Released!
FormEvent event.target has been explicitly defined for this event type c337fdd
-
Inferno Versions 2 through, like, 8 released.
Added a warning when rendering links with javascript: URLs 7bc3763
-
[AskJS] Is there a silver bullet for consuming Typescript libraries in a Monorepo?
I mean I don't know what your monorepo looks like, but for example infernojs (actually written with typescript) uses lerna, and lerna seems simpler than typescript references
-
New Svelte Core/Vercel Team Member
Svelte just got a lot more interesting! Dominic who is the creator of LexicalJs and InfernoJs (which is known to be insanely fast) has joined the svelte core team and is now working at Vercel full time! Here is the announcement on Twitter!
-
Virtual DOM is pure overhead
Inferno.js uses VDOM https://github.com/infernojs/inferno and is faster than Svelte according to these benchmarks https://krausest.github.io/js-framework-benchmark/2023/table.... Sooo, VDOM can improve performance?
-
Current stats show that React is still by far the most popular and beloved front-end framework
Inferno (~6 years old) uses a VDOM, just like React, but it completely smokes React in benchmarks
-
Solid vs React - the Fastest VS the Most Popular UI Library
Some might argue that React’s relatively poor performance (it’s still plenty-fast for many apps) is due to Virtual DOM and prioritization of development experience, i.e., clarity over complexity. To counter the first argument - there’s React-like Inferno. For the second one - there’s Solid.
-
The Real Cost of UI Components Revisited
1. Inferno:
-
A Look at Compilation in JavaScript Frameworks
A VDOM library like Inferno uses this information to compile its JSX directly into pre-optimized node structures. Marko, and Vue hoist their static VDOM nodes outside of their components so that they don't incur the overhead of recreating them on every render.
-
React JS FAQ: The Most Common Questions
InfernoJS
What are some alternatives?
tsconfig-paths - Load node modules according to tsconfig paths, in run-time or via API.
solid - A declarative, efficient, and flexible JavaScript library for building user interfaces.
babel-plugin-tsconfig-paths-module-resolver - Use tsconfig-paths in any bundler that supports a custom babel config.
Preact - ⚛️ Fast 3kB React alternative with the same modern API. Components & Virtual DOM.
typescript-rollup - A Single-Page Application(SPA) built using TypeScript, Rollup.js, and Web Dev Server
Mithril.js - A JavaScript Framework for Building Brilliant Applications
alias-hq - The end-to-end solution for configuring, refactoring, maintaining and using path aliases
Svelte - Cybernetically enhanced web apps
lerna-lite - Subset of Lerna in a smaller & more modular project. Helps manage and publish multiple packages in a monorepo/workspace structure
React - The library for web and native user interfaces.
nestjs-monorepo-microservices-proxy - Example of how to implement a Nestjs monorepo with no shared folder
Vue.js - This is the repo for Vue 2. For Vue 3, go to https://github.com/vuejs/core