fix: coordinator build working after rename (#46)

* fix: coordinator build working after rename

* chore: use npm ci for ci build

README.md

@@ -259,7 +259,7 @@ module.exports = {
 - add our module file(s) (e.g. `src/clients.ts`) and test file(s) (e.g. `src/clients.test.ts`)
   - NOTE: when these files were copied over, they came from caravan when not all files were converted to typescript. A `transform` field needed to be added to the jest config as well as `babel-jest` package to handle js transformations for those older files.
 - You should now be able to run `turbo run test --scope=@caravan/clients` and `turbo run build --scope=@caravan/clients` to test and build
-- To start using this in another package, say `@caravan/coordinator` simply add it to the package.json with a `*`:
+- To start using this in another package, say `caravan-coordinator` simply add it to the package.json with a `*`:
 ```json
 {
   "dependencies": {
@@ -314,4 +314,3 @@ instead of
 ```ts
 import { reverseBuffer } from "bitcoinjs-lib/src/bufferutils.js";
 ```
-

apps/coordinator/Dockerfile

@@ -14,7 +14,7 @@ RUN npm install -g turbo
 COPY . .
 # Optimize caching with docker
 # https://turbo.build/repo/docs/handbook/deploying-with-docker
-RUN turbo prune @caravan/coordinator --docker
+RUN turbo prune caravan-coordinator --docker
 
 # Add lockfile and package.json's of isolated subworkspace
 FROM base AS installer
@@ -24,13 +24,13 @@ WORKDIR /app
 COPY .gitignore .gitignore
 COPY --from=builder /app/out/json/ .
 COPY --from=builder /app/out/package-lock.json ./package-lock.json
-RUN npm install
+RUN npm ci
 
 # Build the project
 COPY --from=builder /app/out/full/ .
 ENV NODE_OPTIONS=--max-old-space-size=32768
 
-RUN npx turbo run build --filter=coordinator...
+RUN npx turbo run build --filter=caravan-coordinator...
 
 # Serve the production build files via nginx (will be served at http://localhost:80/#
 # in docker vm. Map port 80 to a different port on the host machine to access the app)

package.json

@@ -3,7 +3,7 @@
   "private": true,
   "scripts": {
     "build": "turbo build",
-    "build:coordinator": "turbo build --filter=@caravan/coordinator",
+    "build:coordinator": "turbo build --filter=caravan-coordinator",
     "changeset": "changeset",
     "ci": "turbo run build lint test",
     "dev": "turbo dev",
@@ -12,7 +12,7 @@
     "lint": "turbo lint",
     "version": "turbo run build && turbo lint test && changeset version",
     "release": "turbo run build && turbo lint test && changeset publish",
-    "dev:coordinator": "turbo run dev --filter=@caravan/coordinator",
+    "dev:coordinator": "turbo run dev --filter=caravan-coordinator",
     "publish-tags": "changeset tag && git push --follow-tags"
   },
   "devDependencies": {

packages/caravan-wallets/src/trezor.ts

@@ -60,7 +60,7 @@ export const TREZOR = "trezor";
  * What's going on with this TrezorConnect import?
  * For some reason the way trezor/connect and trezor/connect-web export their default
  * export gets ignored from some build systems (it might be a webpack issue, but we haven't been
- * able to narrow it down exactly). In @caravan/coordinator, the vite build is able to find
+ * able to narrow it down exactly). In caravan-coordinator, the vite build is able to find
  * the default export correctly. In builds that don't respect the built @trezor/connect code,
  * the exports.default value and instead falls back to the tsbuild.__exportStar exports. When
  * this happens we need to pull the `TrezorConnect` object from the default property of the module.