Видео

While this is true to some extend, the alternative options (Module Federation in Vite or esbuild) are really weak at the moment. For instance, for Vite you have a couple of plugins - one which is really new and totally buggy, one which is actually made for Native Federation and returns an incompatible result, and one which only returns esm + Module Federation v1. The latter you cannot use as remote from Webpack or rspack - you can only use as a host (or make Vite - Vite doable). Let's not talk about the esbuild one (this one is even more alpha / buggy - not at all usable for production). So overall I don't think the statement is wrong. If you do Module Federation you most likely do rspack or Webpack (which are both quite the same - just a different engine).

​@@FlorianRappl That makes sense. I don't have much experience outside of that ecosystem (as you correctly guessed 😅)

Vite(rolldown) will offically support Module Federation 2.0 next year.

I fully agree. The Angular router is actually a bit of a disgrace (not only in this area, but this is one of the areas where you feel it the most). I don't know of any bug ticket; I think there was some discussion in the past but it was never followed up.

Usually you want the bundler to resolve your assets (e.g., by using constructs such as "import myImage from './image.png' and then referring to myImage as the source). If, for whatever reason, you need to work with paths instead, then use the static copy functionality of the bundler you've chosen (e.g., for Webpack 5 you want to use the CopyWebpackPlugin: webpack.js.org/plugins/copy-webpack-plugin/). What you need to know, however, is that the URL of the asset is dynamic - it depends where your pilet is deployed. Either use the "basePath" property of the `api.meta` (where api is the pilet API in the pilet) or the functionality of your bundler (e.g., in Webpack the __webpack_public_path__ variable points to this). If you want to know more then please join our community discord to sort things out! discord.gg/kKJ2FZmK8t

You can do it pretty much the same. Ideally, you already start with a template such as the Angular one. It also has some documentation; see github.com/smapiot/piral-templates/tree/develop/templates/pilet-template-angular

@@smapiot is it possible that piral remains in React ja and I can create pilet in different tech stack like Angular or react as per my requirement

@@bijay7 It's a bit difficult to follow. - Piral itself is a framework for micro frontends. Your question however is pointed towards pilet (micro frontends). - A pilet itself is independent of any tech stack. It's just a JS library. - The components registered / created in a pilet can be written using any framework. I've given you a link for a template (with instructions) that creates a pilet with components written in Angular. Just use this. So yes - of course, pilets can be written with whatever tech stack as long as its rendering in the frontend.

@@smapiot hmm… I can understand the confusion. Let me explain. For me the requirement is that there is an existing pilet in Angular and I have to create another pilet which will be used as an extension in the existing pilet. Now as per my understanding the micro frontends or the pilets can be be developed in any technology. So I want to develop my new pilet in react and use it inside the existing Angular pilet. And I am doing a POC for the same that’s why I asked how to create an Angular pilet. I hope it is a bit clear now 🥲🙃

@@bijay7 Yes as mentioned you can - but technically you'll never "use a micro frontend in another micro frontend", but rather "use a component from another micro frontend in a component from the current micro frontend". Piral is all about loose coupling, so one micro frontend will never know another micro frontend - they always go over contracts (e.g., extension components).

There is no notion for that as a pilet is a micro frontend. Micro frontends are generally not "used", but rather their components. As components in Piral are always loosely coupled (to prevent tight coupling, which leads to hidden monoliths) you can only access them indirectly via the extension component mechanism. docs.piral.io/guidelines/tutorials/12-sharing-between-pilets#components As such you can always use any components / events / whatever from any pilet in any pilet. But you will always do that indirectly. If you need direct imports consider shared libraries using the distributed sharing mechanism.

Cool! Also more reading material on the subject: dev.to/florianrappl/micro-frontend-discovery-the-driver-for-scalability-oai

Could you please address this question to Zackery directly? He choose the title and the content of the title - not we.

❤

❤😊😊😊

❤😊😊😊❤😊😊😊❤😊😊😊❤❤❤❤😊❤❤1a

❤p🎉ql❤🎉ql🎉qr

Ll ll

Lrq Q ❤L🎉

CT

Hi Dr

​@@IbrahimQasim-zr9djաք😂😂ոաաաԱԱաԹ😂😂😂

BaduiZzama

BaduiZzama

😢😢😢😢😢😢

wow

​@@fgryikvti😊😊😊😊😊

​😊😊😊😊

Ill😮i

0:01

0:01

​@@blancaras573229:14

29:42

> However I have a hard time getting my pilet working in the shell app. What exactly are you struggling with? If you follow the README it would just work. Make sure to follow the steps closely and respect the requirements. > How would I deploy a pilet to a local file system without the feed? What is a local file system deployment? You can always just pack your pilet (make a tgz via pilet pack), but then where would it be hosted? If you don't want to have a feed service create a manifest build (pilet build --type manifest), so that you can retrieve your pilet via the created JSON. But using a Piral instance w/o a feed service is not recommended. It takes away some of the advantages that MFEs give you. > I would like to run my pilet in a docker container on my own server, have a json file describe where to find the pilet, and let the shell application load the pilet with that json file. A bit confused. You mean you want to run the app shell in a Docker container? A pilet is just a set of static files - it does not run anywhere (besides a user's browser). > Do you have any links to useful documentation I might've missed? Most things become clear when you go throw the tutorials and look at the samples. See docs.piral.io and github.com/piral-samples

The reason that we have great dev experience here is your outstanding work and foundation. Thanks a lot for your contributions! (Also: There is more planned for v5 - you'll be able to publish pilets directly by right-clicking and "publish" in Visual Studio.)

You can either - use npm link on your app shell to be able to link against it or - you start a local npm registry such as verdaccio (github.com/verdaccio/verdaccio) to host / distribute it

Thanks for the info! We'll try to adjust it a bit better in future videos!

There are multiple ways: 1. Load other pilets at debug runtime using Piral Inspector (browser extension) 2. Start the pilet debug command with the --feed option to load other pilets from a known feed 3. Start the pilet debug with multiple directories (arguments) to debug multiple pilets at the same time (running in the same shell)