-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A bit of clarification about possible performance loss #1
Comments
@welitonderesende - it's a fine question and we're not far enough along to have any sense of that yet... i'll try to remember to report back here once our code base behind this puts on some real weight |
Hi @Beej126 any updates on that, I'm going to start a project from scratch and I don't want to eject from CRA, would be great to see your findings on this. |
I guess my question is: are you comfortable with CRA for single-spa? |
The basic mechanics are solid. Rescripts is solving everything we've run into needing to customize webpack and jest and it feels very clean & concise... it feels great to rather blindly leverage webpack's optimizations and then just override the little bits as we come to each need... we've rolled from react-scripts 1.8 last year through 2.x to 3.2 already without a hitch. After getting this much under my belt, I can finally comprehend CanopyTax's coaching about "import maps" as the answer for letting wepback do it's usual code splitting bundles in the microspas... but haven't quite gathered the need or mojo to go finish that off in our environment. Like anything, make sure you really need the benefit vs the overhead. For example, maybe wait till you have the need to diverge into multiple front end frameworks (e.g. React + Blazor or Angular)... it's a bit silly for us since we're currently doing them all in React anyway... no surprise, you wind up wanting to share logic & components across all those individual spas... we went with an internal npm package which is then it's own overhead to debug locally (Tip: I've held the line on Typescript and am happy for it, so another tip is just leave your npm package in typescript as well and just publish the src folder as root... in the build script, copy copy package.json to src\ and
|
Hi @Beej126, I was looking for some solution that could help me out go through the setup using create-react-app and single-spa.
I found this repo, I'd like to know if this setup caused any visible loss of performance while running the applications?
Since this discussion implies that bundling all the code together could lead to performance loss
The text was updated successfully, but these errors were encountered: