[BUG]: latest update broke everything #4
Description
Description of the bug
Sorry, not sure how to debug what's happening. I was testing an image a few mins ago (before the update) and everything was working, then the docker image was updated, I saw docker downloading new layers, and now bun install doesn't work anymore
#8 [ 4/11] RUN bun install --frozen-lockfile
#8 0.086 bun install v1.0.8 (2a405f69)
#8 0.089 error: Unexpected installing @remix-run/dev
#8 0.089 error: Unexpected installing @remix-run/eslint-config
.... many other packages not being installed .....
.... many other packages not being installed .....
.... many other packages not being installed .....
#8 0.118 [35.00ms] done
#8 DONE 0.1s
Environment
System:
OS: macOS 14.0
CPU: (10) arm64 Apple M1 Max
Memory: 3.79 GB / 32.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 18.18.0 - ~/.nvm/versions/node/v18.18.0/bin/node
Yarn: 1.22.19 - ~/.nvm/versions/node/v18.18.0/bin/yarn
npm: 9.8.1 - ~/.nvm/versions/node/v18.18.0/bin/npm
pnpm: 8.8.0 - ~/Library/pnpm/pnpm
bun: 1.0.8 - ~/.bun/bin/bun
Languages:
Bash: 3.2.57 - /bin/bash
Perl: 5.30.3 - /usr/bin/perl
Python3: 3.9.6 - /usr/bin/python3
Ruby: 2.6.10 - /usr/bin/ruby
Browsers:
Chrome: 119.0.6045.105
Safari: 17.0
npmPackages:
@remix-run/dev: ^2.2.0 => 2.2.0
@remix-run/eslint-config: ^2.2.0 => 2.2.0
@remix-run/node: ^2.2.0 => 2.2.0
@remix-run/react: ^2.2.0 => 2.2.0
@remix-run/serve: ^2.2.0 => 2.2.0
@types/react: ^18.2.20 => 18.2.34
@types/react-dom: ^18.2.7 => 18.2.14
autoprefixer: ^10.4.16 => 10.4.16
eslint: ^8.38.0 => 8.53.0
isbot: ^3.6.8 => 3.7.0
miniflare: ^3.20231025.1 => 3.20231025.1
postcss: ^8.4.31 => 8.4.31
react: ^18.2.0 => 18.2.0
react-dom: ^18.2.0 => 18.2.0
tailwindcss: ^3.3.5 => 3.3.5
typescript: ^5.1.6 => 5.2.2
vite: ^4.5.0 => 4.5.0
vite-tsconfig-paths: ^4.2.1 => 4.2.1
Steps To Reproduce
FROM imbios/bun-node:20-slim
WORKDIR /usr/src/app
# Copy the package files and install dependencies
COPY . .
RUN bun install --frozen-lockfile
ENV NODE_ENV=production
RUN bun run build
Additional Information
No response
Validations
- Follow our Code of Conduct
- Read the Contributing Guide.
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
- The provided reproduction is a minimal reproducible of the bug.