Revert "Replace npm with pnpm (#136)" (#144)

## Summary

Reverting back to `npm` due to Snyk UI not supporting `pnpm.overrides`
in `package.json` (best source appears to be this
[comment](snyk/nodejs-lockfile-parser#111 (comment))).
Sounds like the CLI might support it at this time, which means the Snyk
[github action](https://github.com/snyk/actions/tree/master/node) might
work, but not worth exploring further at this time. Also not sure if
Vanta requires Snyk UI for compliance.

## Checklist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update


<!-- av pr metadata
This information is embedded by the av CLI when creating PRs to track
the status of stacks when using Aviator. Please do not delete or edit
this section of the PR.
```
{"parent":"main","parentHead":"","trunk":"main"}
```
-->

Co-authored-by: Sean Lynch <[email protected]>

Author: sean-zlai

build.sbt

@@ -240,14 +240,14 @@ lazy val frontend = (project in file("frontend"))
     buildFrontend := {
       println("Installing frontend dependencies...")
       import scala.sys.process._
-      val pnpmCiResult = Process("pnpm install --frozen-lockfile", file("frontend")).!
+      val npmCiResult = Process("npm ci", file("frontend")).!
 
-      if (pnpmCiResult != 0) {
-        sys.error("pnpm install failed!")
+      if (npmCiResult != 0) {
+        sys.error("npm ci failed!")
       }
 
       println("Building frontend...")
-      val buildResult = Process("pnpm run build", file("frontend")).!
+      val buildResult = Process("npm run build", file("frontend")).!
 
       if (buildResult == 0) {
         println("Copying frontend assets to /hub/public...")

docker-init/README.md

@@ -33,7 +33,7 @@ $ docker compose -f docker-init/compose.yaml up
 
 The **backend** is served at: http://localhost:9000
 
-The **frontend** is served at: http://localhost:3000. This serves statically built code - no live dev server. `cd frontend; pnpm run dev` for a live dev server.
+The **frontend** is served at: http://localhost:3000. This serves statically built code - no live dev server. `cd frontend; npm run dev` for a live dev server.
 
 You can also access the parquet anomaly data table. To do so, from another terminal run:
 

frontend/README.md

@@ -7,7 +7,7 @@ The frontend for Chronon.
 ### Prerequisites
 
 - [Node.js](https://nodejs.org/en/) (LTS version recommended)
-- [pnpm](https://pnpm.io/installation) - fast and disk space efficient package manager
+- npm (comes with Node.js)
 
 ### Installation
 
@@ -26,7 +26,7 @@ The frontend for Chronon.
 
 3. Install dependencies:
    ```bash
-   pnpm install
+   npm install
    ```
 
 ### Development
@@ -53,7 +53,7 @@ Done uploading summaries! 🥳
 3. Then, start the development server:
 
 ```bash
-pnpm dev
+npm run dev
 ```
 
 This will start a local server. The app will automatically reload if you make changes to the code.
@@ -63,7 +63,7 @@ This will start a local server. The app will automatically reload if you make ch
 To create an optimized production build:
 
 ```bash
-pnpm build
+npm run build
 ```
 
 This will create an optimized version of your project in the `build` directory.
@@ -73,7 +73,7 @@ This will create an optimized version of your project in the `build` directory.
 To preview the production build locally:
 
 ```bash
-pnpm preview
+npm run preview
 ```
 
 ### Running Tests
@@ -85,72 +85,72 @@ pnpm preview
 To run both unit and integration tests together:
 
 ```bash
-pnpm test
+npm run test
 ```
 
 #### Unit Tests
 
 To run unit tests using Vitest:
 
 ```bash
-pnpm test:unit
+npm run test:unit
 ```
 
 To run unit tests once:
 
 ```bash
-pnpm test:unit:once
+npm run test:unit:once
 ```
 
 #### Integration Tests
 
 To run integration tests using Playwright:
 
 ```bash
-pnpm test:integration
+npm run test:integration
 ```
 
 To run integration tests once:
 
 ```bash
-pnpm test:integration:once
+npm run test:integration:once
 ```
 
 For the Playwright UI to explore test results:
 
 ```bash
-pnpm test:integration:ui
+npm run test:integration:ui
 ```
 
 ### Linting and Formatting
 
 To check code formatting and linting issues:
 
 ```bash
-pnpm lint
+npm run lint
 ```
 
 To format the codebase:
 
 ```bash
-pnpm format
+npm run format
 ```
 
 ### Type Checking
 
 To check the TypeScript types:
 
 ```bash
-pnpm check
+npm run check
 ```
 
 To continuously check types while developing:
 
 ```bash
-pnpm check:watch
+npm run check:watch
 ```
 
 ## Best Practices
 
-1. **Code Style**: This project uses Prettier and ESLint for code formatting and linting. Please run `pnpm lint` and `pnpm format` before committing changes.
+1. **Code Style**: This project uses Prettier and ESLint for code formatting and linting. Please run `npm run lint` and `npm run format` before committing changes.
 2. **Testing**: Ensure all changes are covered with unit and integration tests. Use Vitest for unit tests and Playwright for integration tests.