Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix Vercel deploy error related to sharp #139

Open
ReoHakase opened this issue May 1, 2024 · 0 comments
Open

Fix Vercel deploy error related to sharp #139

ReoHakase opened this issue May 1, 2024 · 0 comments

Comments

@ReoHakase
Copy link
Owner

No description provided.

ReoHakase added a commit that referenced this issue May 1, 2024
@ReoHakase
build: 📦️ Override sharp version to 0.33.3 (#139)
bf1513f
@ReoHakase ReoHakase mentioned this issue May 1, 2024
Open
ReoHakase added a commit that referenced this issue May 1, 2024
@ReoHakase
refactor: ♻️ (api) Optimize logger configuration for production (#139)
5ad2595 
- The previous one somehow made test coverage fall behind 90%
ReoHakase added a commit that referenced this issue May 1, 2024
@ReoHakase
build: 📦️ Make trusted dependencies explicit (#139)
93c29eb
ReoHakase added a commit that referenced this issue May 1, 2024
@ReoHakase
build: 📦️ Remove playwright install hook (#139)
1c72886
ReoHakase added a commit that referenced this issue May 1, 2024
@ReoHakase
wip: 🚧 Update lockfiles (#139)
6c19728
ReoHakase added a commit that referenced this issue May 1, 2024
@ReoHakase
fix: 🐛 Update husky usage to v9 (#139)
3c903dd
ReoHakase added a commit that referenced this issue May 4, 2024
@ReoHakase
feat: ⚰️ Remove api depending on Bun and revert to Node and pnpm (#139
e02a187 
)

- Because we could not resolve `sharp` installation issue

- Because we could not resolve `sharp` installation issue
ReoHakase added a commit that referenced this issue May 4, 2024
@ReoHakase
build: 📦️ Replace contentlayer to its maintained fork version (#139)
c7b89fa 
- Overrode `mdx-bundler` version to v9 since v10 does not work with `contentlayer2 build` properly
ReoHakase added a commit that referenced this issue May 4, 2024
@ReoHakase
build: 📦️ Downgrade pnpm to v8 (#139)
3a95cbb 
- Since Vercel only supports pnpm v6, v7, v8: https://vercel.com/docs/deployments/builds/package-managers
ReoHakase added a commit that referenced this issue May 5, 2024
@ReoHakase
build: 📦️ Downgrade Node to v18 (#139)
d7561bd 
- Since v20 possibly causes memory errors when deployed to Vercel
```
Fatal glibc error: malloc.c:3211 (__libc_malloc): assertion failed: !victim || chunk_is_mmapped (mem2chunk (victim)) || ar_ptr == arena_for_chunk (mem2chunk (victim))
```
ReoHakase added a commit that referenced this issue May 5, 2024
@ReoHakase
ci: 🦺 Fix build and sb:test ci (#139)
4f53b0f
ReoHakase added a commit that referenced this issue May 5, 2024
@ReoHakase
chore: 🔧 (web) Stop using experimental Next.js options (#139)
8d5ea60
ReoHakase added a commit that referenced this issue May 5, 2024
@ReoHakase
fix: 🚑️ (web) Fix contentlayer2 package specification (#139)
c53de4b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ReoHakase