You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When deploying a project on Netlify that uses the Bun dependency manager, the build process fails if the dependencies include patches with encoded characters such as %2F. This issue seems to stem from Netlify's handling of URL-encoded characters within patch URLs, causing the installation process to break.
Steps to Reproduce
Create a Bun-managed project.
Add a dependency with a patch URL containing encoded characters (e.g., %2F).
Deploy the project on Netlify.
Observe the build process failing during the dependency installation phase.
What is the expected behavior?
Netlify should correctly handle and install dependencies with patches that include encoded characters.
What do you see instead?
The build process on Netlify fails, indicating an issue with the handling of encoded characters in the patch URLs.
Additional information
No response
The text was updated successfully, but these errors were encountered:
What version of Bun is running?
1.1.29
What platform is your computer?
Darwin 24.0.0 arm64 arm
What steps can reproduce the bug?
Description
When deploying a project on Netlify that uses the Bun dependency manager, the build process fails if the dependencies include patches with encoded characters such as %2F. This issue seems to stem from Netlify's handling of URL-encoded characters within patch URLs, causing the installation process to break.
Steps to Reproduce
Create a Bun-managed project.
Add a dependency with a patch URL containing encoded characters (e.g., %2F).
Deploy the project on Netlify.
Observe the build process failing during the dependency installation phase.
What is the expected behavior?
Netlify should correctly handle and install dependencies with patches that include encoded characters.
What do you see instead?
The build process on Netlify fails, indicating an issue with the handling of encoded characters in the patch URLs.
Additional information
No response
The text was updated successfully, but these errors were encountered: