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.

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

feat(optimizer): allow users to specify their esbuild platform option #18611

Merged
merged 3 commits into from
Nov 8, 2024

Conversation

dario-piotrowicz
Copy link
Contributor

Description

This PR is trying to address the problem I mentioned here: https://github.com/vitejs/vite/pull/18395/files#r1832458011

(discord thread)

@sapphi-red sapphi-red added p3-downstream-blocker Blocking the downstream ecosystem to work properly (priority) regression The issue only appears after a new release feat: deps optimizer Esbuild Dependencies Optimization feat: environment API Vite Environment API labels Nov 7, 2024
@sapphi-red sapphi-red changed the title feat: allow users to specify their esbuild prebundling platform feat(optimizer): allow users to specify their esbuild platform option Nov 7, 2024
Copy link
Collaborator

@hi-ogawa hi-ogawa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! I was using esbuildOptions: { banner: undefined } hi-ogawa/vite-environment-examples#148, but it makes sense to be fixed here.

@sapphi-red sapphi-red merged commit 0924879 into vitejs:main Nov 8, 2024
20 checks passed
@dario-piotrowicz dario-piotrowicz deleted the dario/prebundling-platform branch November 8, 2024 09:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat: deps optimizer Esbuild Dependencies Optimization feat: environment API Vite Environment API p3-downstream-blocker Blocking the downstream ecosystem to work properly (priority) regression The issue only appears after a new release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants