⚗️ Check if build is passing with npm instead of yarn

This commit is contained in:
Manuel
2023-08-29 22:08:26 +02:00
parent 516c5b41ea
commit aba42a1aa1
3 changed files with 8 additions and 6 deletions

View File

@@ -63,9 +63,9 @@ jobs:
restore-keys: | restore-keys: |
${{ runner.os }}-nextjs-${{ hashFiles('**/package-lock.json') }}- ${{ runner.os }}-nextjs-${{ hashFiles('**/package-lock.json') }}-
- run: yarn install --immutable - run: npm install --immutable
- run: yarn build - run: npm run build
- name: Docker meta - name: Docker meta
id: meta id: meta

View File

@@ -70,11 +70,11 @@ jobs:
path: .next/cache path: .next/cache
key: ${{ runner.os }}-build-${{ env.cache-name }} key: ${{ runner.os }}-build-${{ env.cache-name }}
- run: yarn install --immutable - run: npm install --immutable
- run: yarn turbo build - run: npm run build
- run: yarn test:run - run: npm run test:run
- name: Docker meta - name: Docker meta
if: github.event_name != 'pull_request' if: github.event_name != 'pull_request'

View File

@@ -19,8 +19,10 @@ COPY prisma/schema.prisma prisma/schema.prisma
COPY ./scripts/run.sh ./scripts/run.sh COPY ./scripts/run.sh ./scripts/run.sh
RUN npm config set unsafe-perm true
ARG NPM_CONFIG_LOGLEVEL=verbose ARG NPM_CONFIG_LOGLEVEL=verbose
RUN yarn global add prisma RUN npm i -g prisma
# RUN yarn global add prisma
RUN which prisma RUN which prisma
EXPOSE 7575 EXPOSE 7575