Micro-Frontends Course - Beginner to Expert
video description
Date: 2022-03-14
Related videos
Comments and reviews: 10
Philipjc
Great video, very well explained concepts and implementations. I am currently gearing up to implement microfrontends in my projects at work, but as with other videos in the scene currently yu have not dug into how they are hosted and shared via real environments once deployed. I have hazarded some guesses. In the Webpack configs we point to where the remote projects are hosted (locally (localhost) on in your tutorial) is it safe to safe we just need to point at where we store them once deployed, for me this would be in the nginx folder, nginx/build/project files (index.js).
Cheers
reply
Great video, very well explained concepts and implementations. I am currently gearing up to implement microfrontends in my projects at work, but as with other videos in the scene currently yu have not dug into how they are hosted and shared via real environments once deployed. I have hazarded some guesses. In the Webpack configs we point to where the remote projects are hosted (locally (localhost) on in your tutorial) is it safe to safe we just need to point at where we store them once deployed, for me this would be in the nginx folder, nginx/build/project files (index.js).
Cheers
reply
itech
I didn't face any issue following the tutorial,
However, when I am trying to serve it using serve, it causes problem with inter application routing,
reproduce-able steaps:
1. yarn build
2. yarn build:start
3. navigate to localhost:3000
4. click on any product (it will show pdp for that product) E.g: localhost:3000/product/1
5. reload
4. localhost:3000/product/1 will give 404 response
I assume the reason behind this is the remote is being fetched only in the index.jsx of the home repository,
what is the work around?
reply
I didn't face any issue following the tutorial,
However, when I am trying to serve it using serve, it causes problem with inter application routing,
reproduce-able steaps:
1. yarn build
2. yarn build:start
3. navigate to localhost:3000
4. click on any product (it will show pdp for that product) E.g: localhost:3000/product/1
5. reload
4. localhost:3000/product/1 will give 404 response
I assume the reason behind this is the remote is being fetched only in the index.jsx of the home repository,
what is the work around?
reply
Kayote
Apologies for the poor choice of words but I want people to strongly consider alternatives to this approach before deciding upon this. At my last place, the CTO, even though he didnt understand what micro-frontends are, was still insistent that this is the way to go for their startup (they were working on the MVP!). Unnecessary complexity just for the sake a few very specific case benefits makes no sense to me.
reply
Apologies for the poor choice of words but I want people to strongly consider alternatives to this approach before deciding upon this. At my last place, the CTO, even though he didnt understand what micro-frontends are, was still insistent that this is the way to go for their startup (they were working on the MVP!). Unnecessary complexity just for the sake a few very specific case benefits makes no sense to me.
reply
Research
Why do they come up with a fancy name -micro frontend- when really its just a library...i mean sure its handed to us by the server but its not much different than acting just like library, its a UI library...just in the client instead of the server. I swear to God programmers these days just like to sit around and come up with words
reply
Why do they come up with a fancy name -micro frontend- when really its just a library...i mean sure its handed to us by the server but its not much different than acting just like library, its a UI library...just in the client instead of the server. I swear to God programmers these days just like to sit around and come up with words
reply
Esther
Hello -Jack Herrington and everyone else. I am having trouble installing npm and starting the server on the server app. I keep getting this error - Invalid package name ---: name can only contain URL-friendly characters-. I believe this error is being caused by this dependency ---: -nestjs/passport-, how do i get around this.
reply
Hello -Jack Herrington and everyone else. I am having trouble installing npm and starting the server on the server app. I keep getting this error - Invalid package name ---: name can only contain URL-friendly characters-. I believe this error is being caused by this dependency ---: -nestjs/passport-, how do i get around this.
reply
zengin07
After watching demo part at the beginning here is my opinion:
This may be very beneficial for large projects that are developed by multiple teams but I think nx workspaces provides similar benefits more conveniently for projects that are developed by single team.
Thanks for the high quality free content.
reply
After watching demo part at the beginning here is my opinion:
This may be very beneficial for large projects that are developed by multiple teams but I think nx workspaces provides similar benefits more conveniently for projects that are developed by single team.
Thanks for the high quality free content.
reply
Ayta-
01:09:23 Is there any method for share dependencies (NPM modules) between this three micro frontend app? Because you installed 'remix icon package' for every micro frontends app(cart , pdp, home). Is there any solution for this?
By the way, thank you so much for this video Jack. You rock!
reply
01:09:23 Is there any method for share dependencies (NPM modules) between this three micro frontend app? Because you installed 'remix icon package' for every micro frontends app(cart , pdp, home). Is there any solution for this?
By the way, thank you so much for this video Jack. You rock!
reply
freecodecamp
You-ve highlighted a major problem with micro frontends in this video in that you need to have versioning. Wrapping components in an error boundary is not a solution, nor is having a fallback to a library. You may as well just have the library in the first place.
reply
You-ve highlighted a major problem with micro frontends in this video in that you need to have versioning. Wrapping components in an error boundary is not a solution, nor is having a fallback to a library. You may as well just have the library in the first place.
reply
jongood01
You-ve highlighted a major problem with micro frontends in this video in that you need to have versioning. Wrapping components in an error boundary is not a solution, nor is having a fallback to a library. You may as well just have the library in the first place.
reply
You-ve highlighted a major problem with micro frontends in this video in that you need to have versioning. Wrapping components in an error boundary is not a solution, nor is having a fallback to a library. You may as well just have the library in the first place.
reply
sam
I Didnt understand how login is retained from homepage to cart page.Can any body help me what I am missing .Is this is becoz of rxjs or he stored the jwt in some local storage to be extracted when cart page is loaded?
reply
I Didnt understand how login is retained from homepage to cart page.Can any body help me what I am missing .Is this is becoz of rxjs or he stored the jwt in some local storage to be extracted when cart page is loaded?
reply
Add a review, comment
Other channel videos
