Update PNPM lock file and remove Yarn lock

.github/workflows/CD.yml

@@ -20,7 +20,7 @@ jobs:
       - name: Install Node.js
         uses: actions/setup-node@v3
         with:
-          node-version: 14
+          node-version: 20
       - uses: pnpm/[email protected]
         name: Install pnpm
         id: pnpm-install

README.md

@@ -6,40 +6,40 @@ This Ember front-end is the UI where Interflux team members log in to make chang
 
 You will need the following things properly installed on your computer.
 
-* [Git](https://git-scm.com/)
-* [Node.js](https://nodejs.org/)
-* [Yarn](https://yarnpkg.com/)
-* [Ember CLI](https://cli.emberjs.com/release/)
-* [Google Chrome](https://google.com/chrome/)
+- [Git](https://git-scm.com/)
+- [Node.js](https://nodejs.org/)
+- [PNPM](https://pnpm.io/)
+- [Ember CLI](https://cli.emberjs.com/release/)
+- [Google Chrome](https://google.com/chrome/)
 
 ## Installation
 
 - `git clone <repository-url>` this repository
 - `cd admin.interflux.com`
 - `nvm install`
-- `yarn install`
+- `pnpm install`
 
 ## Serving
 
-- `yarn lint`
-- `yarn lint:fix`
+- `pnpm lint`
+- `pnpm lint:fix`
 
 ## Building
 
-- `yarn build`
+- `pnpm build`
 
-## Deploying
+## Development
 
-- `yarn deploy`
+- `pnpm start`
 
 ## Further Reading / Useful Links
 
-* [ember.js](https://emberjs.com/)
-* [ember-cli](https://cli.emberjs.com/release/)
-* Development Browser Extensions
-  * [ember inspector for chrome](https://chrome.google.com/webstore/detail/ember-inspector/bmdblncegkenkacieihfhpjfppoconhi)
-  * [ember inspector for firefox](https://addons.mozilla.org/en-US/firefox/addon/ember-inspector/)
+- [ember.js](https://emberjs.com/)
+- [ember-cli](https://cli.emberjs.com/release/)
+- Development Browser Extensions
+  - [ember inspector for chrome](https://chrome.google.com/webstore/detail/ember-inspector/bmdblncegkenkacieihfhpjfppoconhi)
+  - [ember inspector for firefox](https://addons.mozilla.org/en-US/firefox/addon/ember-inspector/)
 
 ## Branches
 
-  We have two branches: `master` and `production`. Developers branch of and merge back into `master` and never need access to `production`. The `production` branch is a representation of what is currently live on our servers and only needs to be checked out for recreating bugs found in production, but not in master.
+We have two branches: `master` and `production`. Developers branch of and merge back into `master` and never need access to `production`. The `production` branch is a representation of what is currently live on our servers and only needs to be checked out for recreating bugs found in production, but not in master.