Replace yarn (#3554)

* introduce basic api style controller

* locks

* locks

* update readme

* replace yarn with pnpm in readme

* locks

* ignore files

* ignore files

---------

Co-authored-by: ScriptedAlchemy <[email protected]>

Author: ScriptedAlchemy

.gitignore

@@ -132,7 +132,7 @@ buildServer
 **/cypress/report/**
 /federated-express-routes/host/build/
 /federated-express-routes/remote/build/
-/comprehensive-demo-react*/*/public/*.js
-/comprehensive-demo-react*/*/public/*.css
+/comprehensive-demo-react*/**/public/*.js
+/comprehensive-demo-react*/**/public/*.css
 *.map
 

angular-universal-ssr/README.md

@@ -5,7 +5,7 @@
 
 # Running Demo
 
-Run `yarn start`. This will build and serve both `client-app`, `host-app`, on
+Run `pnpm run start`. This will build and serve both `client-app`, `host-app`, on
 ports `4000`, `5000`, respectively.
 
 - [localhost:4000](http://localhost:4000/) (CLIENT_APP)

angular-universal-ssr/e2e.ci.js

@@ -1,6 +1,6 @@
 const concurrently = require('concurrently');
 const commands = {
-    startHost: 'yarn start',
+    startHost: 'pnpm run start',
     startE2e: 'wait-on http://localhost:4000 && yarn e2e:test'
 };
 

angular11-microfrontends-ngrx/README.md

@@ -20,8 +20,8 @@ cd angular11-microfrontends-ngrx
 
 - Install packages: `yarn install`
 - Build the shared library `yarn build:shared`
-- Start the mdmf-shell: `yarn start:shell`
-- Start the Microfrontend: `yarn start:profile`
+- Start the mdmf-shell: `pnpm run start:shell`
+- Start the Microfrontend: `pnpm run start:profile`
 - Open the shell http://localhost:4200
 - Click the profile navigation link to load the remote Microfrontend
 

angular11-microfrontends-ngxs/README.md

@@ -18,8 +18,8 @@ This project shows an example of using Webpack 5 Module Federation with Angular
 
 - Install packages: `yarn install`
 - Build the shared library `yarn build:shared`
-- Start the mdmf-shell: `yarn start:shell`
-- Start the Microfrontend: `yarn start:profile`
+- Start the mdmf-shell: `pnpm run start:shell`
+- Start the Microfrontend: `pnpm run start:profile`
 - Open the shell http://localhost:4200
 - Click the profile navigation link to load the remote Microfrontend
 

angular14-react/README.md

@@ -8,13 +8,13 @@ Note the use of **yarn**, this is required to override the webpack version for t
 
 For `react-user-list`:
 - Install packages: `yarn install`
-- Start: `yarn start`(the app uses port 3002)
+- Start: `pnpm run start`(the app uses port 3002)
 
 
 For `angular-profile`:
 
 - Install packages: `yarn install`
-- Start: `yarn start`
+- Start: `pnpm run start`
 - Open the shell http://localhost:4201
 
 Ports could be changed in `webpack.config.js` files located in `react-user-list` and `angular-profile` folders.

angular15-microfrontends-lazy-components/README.md

@@ -18,8 +18,8 @@ This project shows an example of using Webpack 5 Module Federation with Angular
 
 - Install packages: `yarn install`
 - Build the shared library `yarn build:shared`
-- Start the mdmf-shell: `yarn start:shell`
-- Start the Microfrontend: `yarn start:profile`
+- Start the mdmf-shell: `pnpm run start:shell`
+- Start the Microfrontend: `pnpm run start:profile`
 - Open the shell http://localhost:4200
 - Click the profile navigation link to load the remote Microfrontend
 

angular15-vue3/README.md

@@ -5,8 +5,8 @@ This project shows an example of using Webpack 5 Module Federation with Angular
 ## Running the demo
 
 - Install packages: `yarn install`
-- Start the shell: `yarn start:shell`
-- Start the shell: `yarn start:remote`
+- Start the shell: `pnpm run start:shell`
+- Start the shell: `pnpm run start:remote`
 - Open the shell http://localhost:4200
 
 # Running Cypress E2E Tests

angular15-vue3/e2e.ci.js

@@ -1,7 +1,7 @@
 const concurrently = require('concurrently');
 const commands = {
-    startHost: 'yarn start:shell',
-    startRemote: 'yarn start:remote',
+    startHost: 'pnpm run start:shell',
+    startRemote: 'pnpm run start:remote',
     startE2e: 'yarn e2e:test'
 };
 

apollo-client/README.md

@@ -11,7 +11,7 @@ The `app2` is used to expose a component called `Content` and a route called `us
 
 Run `yarn` to install the dependencies.
 
-Run `yarn start` this will build and start all applications.
+Run `pnpm run start` this will build and start all applications.
 
 Bellow you can see the port mapping:
 

basic-host-remote/README.md

@@ -7,7 +7,7 @@ This example demos a basic host application loading remote component.
 
 # Running Demo
 
-Run `yarn start`. This will build and serve both `app1` and `app2` on ports 3001 and 3002 respectively.
+Run `pnpm run start`. This will build and serve both `app1` and `app2` on ports 3001 and 3002 respectively.
 
 - [localhost:3001](http://localhost:3001/) (HOST)
 - [localhost:3002](http://localhost:3002/) (STANDALONE REMOTE)

bi-directional/README.md

@@ -7,7 +7,7 @@ This example demos bi-directional hosts each with their own remote `Button` comp
 
 # Running Demo
 
-Run `yarn start`. This will build and serve both `app1` and `app2` on ports 3001 and 3002 respectively.
+Run `pnpm run start`. This will build and serve both `app1` and `app2` on ports 3001 and 3002 respectively.
 
 - [localhost:3001](http://localhost:3001/)
 - [localhost:3002](http://localhost:3002/)

comprehensive-demo-react16/README.md

@@ -2,7 +2,7 @@
 
 ```sh
 yarn install
-yarn start
+pnpm run start
 ```
 
 Open [http://localhost:3001](http://localhost:3001).

comprehensive-demo-react18/README.md

@@ -2,7 +2,7 @@
 
 ```sh
 yarn install
-yarn start
+pnpm run start
 ```
 
 Open [http://localhost:3001](http://localhost:3001).

comprehensive-demo-react18/app-01/package.json

@@ -22,8 +22,8 @@
   },
   "scripts": {
     "build": "cross-env NODE_ENV=production rspack build --mode production",
-    "legacy:build": "cross-env NODE_ENV=production webpack",
-    "start": "rspack cross-env NODE_ENV=production --watch",
+    "legacy:build": "cross-env NODE_ENV=production webpack --mode production",
+    "start": "rspack --watch",
     "legacy:start": "webpack --watch",
     "dev": "rspack serve",
     "legacy:dev": "webpack-dev-server --content-base public",

comprehensive-demo-react18/app-02/package.json

@@ -21,7 +21,7 @@
   },
   "scripts": {
     "build": "cross-env NODE_ENV=production rspack build --mode production",
-    "legacy:build": "cross-env NODE_ENV=production webpack",
+    "legacy:build": "cross-env NODE_ENV=production webpack --mode production",
     "start": "rspack cross-env NODE_ENV=production --watch",
     "legacy:start": "webpack --watch",
     "dev": "rspack serve",

comprehensive-demo-react18/app-03/package.json

@@ -21,7 +21,7 @@
   },
   "scripts": {
     "build": "cross-env NODE_ENV=production rspack build --mode production",
-    "legacy:build": "cross-env NODE_ENV=production webpack",
+    "legacy:build": "cross-env NODE_ENV=production webpack --mode production",
     "start": "rspack serve",
     "legacy:start": "webpack --watch",
     "dev": "rspack serve",

comprehensive-demo-react18/app-04/package.json

@@ -21,7 +21,7 @@
   },
   "scripts": {
     "build": "cross-env NODE_ENV=production rspack build --mode production",
-    "legacy:build": "cross-env NODE_ENV=production webpack",
+    "legacy:build": "cross-env NODE_ENV=production webpack --mode production",
     "start": "rspack serve",
     "legacy:start": "webpack --watch",
     "dev": "rspack serve",

comprehensive-demo-react18/app-05/package.json

@@ -5,7 +5,7 @@
   "ignored": true,
   "scripts": {
     "build": "cross-env NODE_ENV=production rspack build --mode production",
-    "legacy:build": "cross-env NODE_ENV=production webpack",
+    "legacy:build": "cross-env NODE_ENV=production webpack --mode production",
     "start": "rspack serve",
     "legacy:start": "webpack --watch",
     "dev": "rspack serve",

cra-react-app-rewired/README.md

@@ -8,7 +8,7 @@ This example demos a basic host application loading remote component.
 
 # Running Demo
 Run `yarn install`.
-Run `yarn start`. This will build and serve both `host` and `remote` on ports 3000 and 3001 respectively.
+Run `pnpm run start`. This will build and serve both `host` and `remote` on ports 3000 and 3001 respectively.
 
 - [localhost:3000](http://localhost:3000/) (HOST)
 - [localhost:3001](http://localhost:3001) (STANDALONE REMOTE)

cra-react-app-rewired/host/public/index.html

@@ -33,7 +33,7 @@
       You can add webfonts, meta tags, or analytics to this file.
       The build step will place the bundled scripts into the <body> tag.
 
-      To begin the development, run `npm start` or `yarn start`.
+      To begin the development, run `npm start` or `pnpm run start`.
       To create a production bundle, use `npm run build` or `yarn build`.
     -->
   </body>

cra-react-app-rewired/remote/public/index.html

@@ -33,7 +33,7 @@
       You can add webfonts, meta tags, or analytics to this file.
       The build step will place the bundled scripts into the <body> tag.
 
-      To begin the development, run `npm start` or `yarn start`.
+      To begin the development, run `npm start` or `pnpm run start`.
       To create a production bundle, use `npm run build` or `yarn build`.
     -->
   </body>

cra/README.md

@@ -7,7 +7,7 @@ This example demos a basic host application loading remote component.
 
 # Running Demo
 
-Run `yarn start`. This will build and serve both `host` and `remote` on ports 3001 and 3002 respectively.
+Run `pnpm run start`. This will build and serve both `host` and `remote` on ports 3001 and 3002 respectively.
 
 - [localhost:3001](http://localhost:3000/) (HOST)
 - [localhost:3002](http://localhost:3002/) (STANDALONE REMOTE)

css-isolation/README.md

@@ -33,7 +33,7 @@ By default the Webpack style-loader will inject CSS in `<style>` tags into the `
 
 # Running Demo
 
-Run `yarn start`. This will build and serve both `app1` and `app2` on ports 3001 and 3002 respectively.
+Run `pnpm run start`. This will build and serve both `app1` and `app2` on ports 3001 and 3002 respectively.
 
 - [localhost:3001](http://localhost:3001/) (HOST)
 - [localhost:3002](http://localhost:3002/) (STANDALONE REMOTE)

different-react-versions-16-17-typescript/README.md

@@ -11,7 +11,7 @@ The adapter consumes both versions of react to "translate" the props into a fres
 
 # Running Demo
 
-Run `yarn start`. This will build and serve both `app1` and `app2` on ports 3001 and 3002 respectively.
+Run `pnpm run start`. This will build and serve both `app1` and `app2` on ports 3001 and 3002 respectively.
 
 - [localhost:3001](http://localhost:3001/) (HOST)
 - [localhost:3002](http://localhost:3002/) (STANDALONE REMOTE)

different-react-versions-16-17/README.md

@@ -11,7 +11,7 @@ The adapter consumes both versions of react to "translate" the props into a fres
 
 # Running Demo
 
-Run `yarn start`. This will build and serve both `app1` and `app2` on ports 3001 and 3002 respectively.
+Run `pnpm run start`. This will build and serve both `app1` and `app2` on ports 3001 and 3002 respectively.
 
 - [localhost:3001](http://localhost:3001/) (HOST)
 - [localhost:3002](http://localhost:3002/) (STANDALONE REMOTE)

different-react-versions-16-18/README.md

@@ -11,7 +11,7 @@ The adapter consumes both versions of react to "translate" the props into a fres
 
 # Running Demo
 
-Run `yarn start`. This will build and serve both `app1` and `app2` on ports 3001 and 3002 respectively.
+Run `pnpm run start`. This will build and serve both `app1` and `app2` on ports 3001 and 3002 respectively.
 
 - [localhost:3001](http://localhost:3001/) (HOST)
 - [localhost:3002](http://localhost:3002/) (STANDALONE REMOTE)

different-react-versions-isolated/README.md

@@ -7,7 +7,7 @@ This example demos host and remote applications running in isolation with two di
 
 # Running Demo
 
-Run `yarn start`. This will build and serve both `app1` and `app2` on ports 3001 and 3002 respectively.
+Run `pnpm run start`. This will build and serve both `app1` and `app2` on ports 3001 and 3002 respectively.
 
 - [localhost:3001](http://localhost:3001/) (HOST)
 - [localhost:3002](http://localhost:3002/) (STANDALONE REMOTE)

different-react-versions-typescript/README.md

@@ -11,7 +11,7 @@ Module Federation allows us to create an adapter which attaches a hooks-friendly
 
 ## Running Demo
 
-Run `yarn start`. This will build and serve both `app1` and `app2` on ports 3001 and 3002 respectively.
+Run `pnpm run start`. This will build and serve both `app1` and `app2` on ports 3001 and 3002 respectively.
 
 - [localhost:3001](http://localhost:3001/) (HOST)
 - [localhost:3002](http://localhost:3002/) (STANDALONE REMOTE)

different-react-versions/README.md

@@ -11,7 +11,7 @@ Module Federation allows us to create an adapter which attaches a hooks-friendly
 
 ## Running Demo
 
-Run `yarn start`. This will build and serve both `app1` and `app2` on ports 3001 and 3002 respectively.
+Run `pnpm run start`. This will build and serve both `app1` and `app2` on ports 3001 and 3002 respectively.
 
 - [localhost:3001](http://localhost:3001/) (HOST)
 - [localhost:3002](http://localhost:3002/) (STANDALONE REMOTE)

dynamic-remotes-node/README.md

@@ -4,7 +4,7 @@ Similar to browser side dynamic remotes.
 
 This allows you to dynamically load remote containers on the server.
 
-`yarn start` will initiate a build and http server, then node will execute a simple test.
+`pnpm run start` will initiate a build and http server, then node will execute a simple test.
 
 ## runtime-container
-This example shows the same thing but how to do it outside of the webpack runtime (outside a webpack bundle). See the script `import-remote.js`, which is not compiled by webpack. Run the command `yarn import-remote` or simply, `node import-remote.js`
+This example shows the same thing but how to do it outside of the webpack runtime (outside a webpack bundle). See the script `import-remote.js`, which is not compiled by webpack. Run the command `yarn import-remote` or simply, `node import-remote.js`

dynamic-system-host/README.md

@@ -9,7 +9,7 @@ This example demos a basic host application loading remote component.
 
 # Running Demo
 
-Run `yarn start`. This will build and serve both `app1`, `app2`, and `app3` on
+Run `pnpm run start`. This will build and serve both `app1`, `app2`, and `app3` on
 ports `3001`, `3002`, and `3003` respectively.
 
 - [localhost:3001](http://localhost:3001/) (HOST)

federated-css/README.md

@@ -41,7 +41,7 @@ Commands will run host react App on `http://localhost:3001-3008/`
 
 Since there are 9! variants of remotes combinations you are able to create and run your own `start:react:any-combination --scopes=@federated-css/{REQUIRED_COMBINATION_OF_REMOTES}`
 
-ex. `yarn start:react:any-combination @federated-css/{expose-css,expose-scss,expose-less,expose-tailwind-css-global}`
+ex. `pnpm run start:react:any-combination @federated-css/{expose-css,expose-scss,expose-less,expose-tailwind-css-global}`
 it will run all required expose remotes and creates host app with provided depth.
 Note. you don't need to start required remotes separately for this command.
 
@@ -64,7 +64,7 @@ Commands will run host NextJs App on `http://localhost:8081-8084/`.
 
 Since there are 9! variants of remotes combinations you are able to create and run your own `start:nextjs:any-combination --scopes=@federated-css/{REQUIRED_COMBINATION_OF_REMOTES}`
 
-ex. `yarn start:nextjs:any-combination @federated-css/{expose-css,expose-scss,expose-less,expose-tailwind-css-global}`
+ex. `pnpm run start:nextjs:any-combination @federated-css/{expose-css,expose-scss,expose-less,expose-tailwind-css-global}`
 it will run all required expose remotes and creates host app with provided depth.
 Note. you don't need to start required remotes separately for this command.
 

federated-npm/README.md

@@ -7,7 +7,7 @@ This example demos a basic host application loading remote component.
 
 # Running Demo
 
-Run `yarn start`. This will build and serve both `app1` and `app2` on ports 3001 and 3002 respectively.
+Run `pnpm run start`. This will build and serve both `app1` and `app2` on ports 3001 and 3002 respectively.
 
 - [localhost:3001](http://localhost:3001/) (HOST)
 - [localhost:3002](http://localhost:3002/) (STANDALONE REMOTE)

genesis/README.md

@@ -7,7 +7,7 @@
 
 # Running Demo
 
-Run `yarn && yarn dev` or `yarn && yarn build && yarn start`
+Run `yarn && yarn dev` or `yarn && yarn build && pnpm run start`
 
 - [localhost:3001](http://localhost:3001) (ssr-mf-home)
 - [localhost:3002](http://localhost:3002/about) (ssr-mf-about)

loadable-react-16/README.md

@@ -13,7 +13,7 @@ The `app2` is used to expose a component called `Content` and a route called `us
 
 Run `yarn` to install the dependencies.
 
-Run `yarn start` this will build and start all applications.
+Run `pnpm run start` this will build and start all applications.
 
 Bellow you can see the port mapping:
 

loadable-react-18/README.md

@@ -13,7 +13,7 @@ The `app2` is used to expose a component called `Content` and a route called `us
 
 Run `yarn` to install the dependencies.
 
-Run `yarn start` this will build and start all applications.
+Run `pnpm run start` this will build and start all applications.
 
 Bellow you can see the port mapping:
 

medusa-delegate-example/README.md

@@ -6,7 +6,7 @@
 2. Login to medusa https://medusa.codes/
 3. Generate Read/Write Tokens and save https://app.medusa.codes/settings
 4. Copy Read/Write Tokens and add them to `.env` in the root of this directory.
-5. Run a build with yarn start, then go check medusa.
+5. Run a build with pnpm run start, then go check medusa.
 6. If you want to test out version management, change something in `dsl` and run `yarn build && yarn serve` again - you will now be able to control what remote/app uses what version at runtime
 
 # Running Demo

medusa-example/README.md

@@ -6,7 +6,7 @@
 2. Login to medusa https://medusa.codes/
 3. Generate Read/Write Tokens and save https://app.medusa.codes/settings
 4. Copy Read/Write Tokens and add them to `.env` in the root of this directory.
-5. Run a build with yarn start, then go check medusa.
+5. Run a build with pnpm run start, then go check medusa.
 6. If you want to test out version management, change something in `dsl` and run `yarn build && yarn serve` again - you will now be able to control what remote/app uses what version at runtime
 
 # Running Demo

modernjs-medusa/README.md

@@ -6,7 +6,7 @@
 2. Login to medusa https://medusa.codes/
 3. Generate Read/Write Tokens and save https://app.medusa.codes/settings
 4. Copy Read/Write Tokens and add them to `.env` in the root of this directory.
-5. Run a build with yarn start, then go check medusa.
+5. Run a build with pnpm run start, then go check medusa.
 
 # Running Demo
 
@@ -15,4 +15,4 @@ Run `yarn build && yarn serve`
 - [Host is on localhost:3001](http://localhost:3001/)
 - [Provider is on localhost:3002](http://localhost:3002/)
 
-<img src="https://sf16-sg.tiktokcdn.com/obj/eden-sg/shloeh7nuhonuhog/medusa.jpeg" width="800"/>
+<img src="https://sf16-sg.tiktokcdn.com/obj/eden-sg/shloeh7nuhonuhog/medusa.jpeg" width="800"/>