pnpm README: Change yarn occurrences with pnpm.

Author: thet

README.md

@@ -31,9 +31,9 @@ There are several options to integrate Mockup.
 
     This starts up the webpack build process in watch mode.
     Any JavaScript changes are immediately compiled.
-    For some changes - like for adding new packages via `yarn add` and then using it you might need to restart.
+    For some changes - like for adding new packages via `pnpm add` and then using it you might need to restart.
     The command also spins up a development server for our `11ty` based documentation and demo pages.
-    If you don't need the docs running, you can run `yarn start:webpack` or `npm run start:webpack` instead, so that only the webpack devserver is running.
+    If you don't need the docs running, you can run `pnpm start:webpack` or `npm run start:webpack` instead, so that only the webpack devserver is running.
 
 - Go to `http://localhost:8000`:
   On this port our demo and documentation pages are served.
@@ -124,7 +124,7 @@ If you want to develop in Plone, you have two options:
 1. Run `make watch-plone`. You need buildout to have plone.staticresources checked out next to Mockup.
    Mockup will compile it's bundle directly into the `++plone++static` directory of plone.staticresources and update it when you change something in Mockup.
 
-2. Run `npx yarn start:webpack`, go to the resource registry ( http://localhost:8080/Plone/@@resourceregistry-controlpanel ) and add the URL `http://localhost:8000/bundle.min.js` to the JavaScript input field of the plone bundle instead of the other URL `++plone++static/bundle-plone/bundle.min.js`.
+2. Run `npx pnpm start:webpack`, go to the resource registry ( http://localhost:8080/Plone/@@resourceregistry-controlpanel ) and add the URL `http://localhost:8000/bundle.min.js` to the JavaScript input field of the plone bundle instead of the other URL `++plone++static/bundle-plone/bundle.min.js`.
 
 For more commands inspect Makefile and the script part of the package.json.
 
@@ -166,17 +166,17 @@ You can put some `debugger;` statements to the code to break the execution and i
 
 ### Developing external Packages
 
-If you want to work on ony external package like Patternslib or any external Mockup pattern you can do so by linking those packages into the node_modules folder via `yarn link`.
+If you want to work on ony external package like Patternslib or any external Mockup pattern you can do so by linking those packages into the node_modules folder via `pnpm link`.
 
 1. Check out the external package you want to develop on.
 
-2. Make sure you have installed the dependencies in the development package (e.g. by running `yarn install`). (TODO: verify that!)
+2. Make sure you have installed the dependencies in the development package (e.g. by running `pnpm install`). (TODO: verify that!)
 
-3. Run `yarn link` in the external development package to register it with yarn.
+3. Run `pnpm link` in the external development package to register it with pnpm.
 
-4. Run `yarn link "PACKAGE-NAME"` in mockup to create the node_modules symlink.
+4. Run `pnpm link "PACKAGE-NAME"` in mockup to create the node_modules symlink.
 
-After developing you might want to run `yarn unlink "PACKAGE-NAME"` to unlink the development package.
+After developing you might want to run `pnpm unlink "PACKAGE-NAME"` to unlink the development package.
 
 For more information see:
 
@@ -195,7 +195,7 @@ https://formidable.com/blog/2018/finding-webpack-duplicates-with-inspectpack-plu
 Build the stats.json file:
 
 ```
-npx yarn build:stats
+npx pnpm build:stats
 ```
 
 Check dependency tree and why which package was included:
@@ -219,7 +219,7 @@ To update the translation file, the following needs to be done:
 1. Extract the messages from this package:
 
 ```
-npx yarn run i18n
+npx pnpm run i18n
 ```
 
 Or just `npm run i18n`...
@@ -290,7 +290,7 @@ Without grouping: `TYPE: MESSAGE`
 
 If the commit message doesn't follow this convention, then it won't be included in the changelog.
 To bypass the pre-commit hook, use the git `-n` switch.
-Example: `git commit yarn.lock -m "yarn install." -n`.
+Example: `git commit pnpm-lock.yaml -m "pnpm install." -n`.
 
 If you are working on a component like the structure pattern (pat-structure), use `pat structure` as a group.
 
@@ -318,11 +318,11 @@ git commit -am "maint: Remove unnecessary file from root directory."
 
 **Note**
 
-Please keep commits on the `yarn.lock` file or any other auto-generated code seperate.
+Please keep commits on the `pnpm-lock.yaml` file or any other auto-generated code seperate.
 
-Just commit them seperately with `git commit yarn.lock -m "yarn install" -n`.
+Just commit them seperately with `git commit pnpm-lock.yaml -m "pnpm install" -n`.
 
 Keeping them seperate reduces the effort when merging or rebasing branches where a merge conflict can easily happen.
-In such cases you can just withdraw your changes on the `yarn.lock` file, or remove those commits and reinstall with `yarn install` at the end of a successful merge or rebase.
+In such cases you can just withdraw your changes on the `pnpm-lock.yaml` file, or remove those commits and reinstall with `pnpm install` at the end of a successful merge or rebase.
 
 ---