vite-plugin-federation
ts-monorepo
vite-plugin-federation | ts-monorepo | |
---|---|---|
6 | 14 | |
2,030 | 1,430 | |
3.6% | - | |
7.0 | 8.5 | |
about 1 month ago | 2 days ago | |
TypeScript | TypeScript | |
GNU General Public License v3.0 or later | 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.
vite-plugin-federation
-
Module Federation using ViteJS - Step into the Micro-frontend architecture
Today, we'll delve into Module Federation using the Vite Plugin, an excellent tool created by Originjs to develop micro-frontend applications with Vite.
-
🚀 Dominate React Project Startups: Insider Tips for Dev Success! 🤓
In my most recent project, I needed to build an application with micro-frontends. Starting my research in this area, I found that the Vite plugin for supporting Module Federation is not stable. In particular, I faced an issue that is still open, raising doubts about its usage. Meanwhile, create-react-app works with Module Federation without any issues. I had to make this difficult decision back then, endure the slow webpack build in favor of stability. 😓
-
.NET Core front end development
Vite is largely modular in that a basic installation will not have the features you want but there seems to be a plugin for everything. As far as module federation goes there is this plugin to support it I haven’t used it personally but I’ve also not had any issues with any of the plugins I’ve used. Seems to be fairly solid. You can continue to use webpack if you prefer. Vue 3 will work either way. I just started using vite because the initial setup and configuration was cleaner and easier to use in my opinion.
- Module Federation for distributed front ends — the best of both worlds?
-
When I initialize a Tauri project, it using vite by default. How can i use Tauri together with webpack?
It looks like there is a plugin for that. https://github.com/originjs/vite-plugin-federation
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?
What are some alternatives?
module-federation-plugin
tsconfig-paths - Load node modules according to tsconfig paths, in run-time or via API.
zustand - 🐻 Bear necessities for state management in React
babel-plugin-tsconfig-paths-module-resolver - Use tsconfig-paths in any bundler that supports a custom babel config.
unplugin - Unified plugin system for Vite, Rollup, Webpack, esbuild, rolldown, and more
typescript-rollup - A Single-Page Application(SPA) built using TypeScript, Rollup.js, and Web Dev Server
electron-vite-vue - 🥳 Really simple Electron + Vite + Vue boilerplate.
alias-hq - The end-to-end solution for configuring, refactoring, maintaining and using path aliases
jotai - 👻 Primitive and flexible state management for React
lerna-lite - Subset of Lerna in a smaller & more modular project. Helps manage and publish multiple packages in a monorepo/workspace structure
vitext - The Next.js like React framework for better User & Developer experience!
nestjs-monorepo-microservices-proxy - Example of how to implement a Nestjs monorepo with no shared folder