Switch from yarn to npm

.github/workflows/build.yaml

@@ -18,15 +18,15 @@ jobs:
         uses: actions/setup-node@v4
         with:
           node-version: ${{ env.node-version }}
-          cache: "yarn"
+          cache: "npm"
       - name: Install dependencies
-        run: yarn install --immutable
+        run: npm ci
       - name: Lint
-        run: yarn lint
+        run: npm run lint
       - name: Test
-        run: yarn test
+        run: npm run test
       - name: Build for production
-        run: yarn build:prod
+        run: npm run build:prod
       - name: Pack
         run: cd dist && npm pack
       - uses: actions/upload-artifact@v4

.gitignore

@@ -12,11 +12,4 @@ dist
 *.log
 **/.DS_Store
 
-.yarn/*
-!.yarn/releases
-!.yarn/plugins
-!.yarn/sdks
-!.yarn/versions
-.pnp.*
-
 /.angular/cache

README.md

@@ -23,12 +23,6 @@ Using `npm`:
 npm install ngx-translate-messageformat-compiler @messageformat/core --save
 ```
 
-... or if you use `yarn`:
-
-```sh
-yarn add ngx-translate-messageformat-compiler @messageformat/core
-```
-
 Something to be aware of if you deploy to strict production environments: [Fundamentally, messageformat is a compiler that turns ICU MessageFormat input into JavaScript](https://messageformat.github.io/messageformat/use/), and we do this at runtime. This means calling `new Function` under the hood, which requires allowing `unsafe-eval` for the [`script-src`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src) Content Security Policy (CSP).
 
 ## Setup