single-spa

@ernishant83 The profit sharing would only be if there was substantial contribution and actual revenue.

@ernishant83 What is your experience level with ecmascript, single-spa, react, angular, vue, svelte, webpack, and import maps? Perhaps to start, you could review the following: github.com/single-spa/com…

I need a code reviewer and author for a final attempt to turn the single-spa project into a financially sustainable ecosystem If you join now, we can discuss revenue/profit sharing Please contact info@single-spa-workshop.com or via this twitter account

Women are often stalkers too but not as horrible bc used to the sexualization. The single-spa community has been lots of interactions with stalkers for many years, not usually with sexual aims. Men, nonbinary, and others will also be considered. Women in STEM still marginalized

I prefer working with women, including the trans-inclusive definition of that term, which many do not think should be allowed. This work is fully remote and never meet in person or voice call. Just written communication and technical review/code.

single-spa@7.0.0-beta.13 is released! github.com/single-spa/sin…

heeler@4.0.3 is released! github.com/single-spa/hee…

single-spa@7.0.0-beta.12 is released! github.com/single-spa/sin…

single-spa@7.0.0-beta.11 is released! github.com/single-spa/sin…

Here is an example of how what a trans woman says is aggressed by the open source world 7 days later: x.com/internettrans/…

heeler@4.0.1 is released github.com/single-spa/hee…

single-spa@7.0.0-beta.10 is released github.com/single-spa/sin…

node-loader/import-maps@2.0.0 is released to match the updated api github.com/node-loader/no…

single-spa-react@7.0.0-beta.0 is released. It is a rewrite to typescript, with some updates to the api github.com/single-spa/sin…

Microfrontends are better for projects that survive many years Most software organizations do not The reason why is that the encapsulation allows for re-approaching old Microfrontends without worrying about the tech debt of anything except that one microfrontend One at a time

The only thing I’ve heard about microfrontends for many years is how horrible they are. Open source stalkers sexualize telling maintainers, creators, and authors that their labor was not only low quality, but pointless. They gain satisfaction from feeling powerful

dom-element-getter-helpers@2.1.0 is released! github.com/single-spa/dom…

heeler@3.2.0 is released github.com/single-spa/hee…

vite's use of esbuild in local dev but rollup in production concerns me, since i prefer the same tooling so that there are portable build artifacts and no chance of "works on my machine but not production" vite uses esbuild and rollup webpack / rollup preferred bc JS

Webpack vs rollup vs vite vs esbuild vs swc vs ..??? For microfrontends, build speeds are usually a lot faster than monolithic build - it's part of the advantage of the microservice architecture - so the argument for esbuild or swc isn't as strong. 1/2