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

fix(parcel-core): only allow client-side env to be included #493

Merged

Conversation

louisgv
Copy link
Contributor

@louisgv louisgv commented Mar 9, 2023

Details

Code of Conduct

@louisgv louisgv self-assigned this Mar 9, 2023
@louisgv louisgv linked an issue Mar 9, 2023 that may be closed by this pull request
2 tasks
@louisgv louisgv requested a review from ColdSauce March 9, 2023 18:11
@louisgv
Copy link
Contributor Author

louisgv commented Mar 9, 2023

There was a discussion on whether this should be a patch on top of parcel/core instead of a fork.

Patching will allow us to have minimal footprint and make it easier to maintain/apply future upstream commit.

My rationale for forking it is that it will encourage/forcing us to learn the internal in and out of parcel/core, since it powers the bulk of our compiler. The translation between flow -> TS will also allow us to have better grasp at the typing, instead of relying on Parcel usptream flow implementation.

@louisgv louisgv merged commit e4aecdd into main Mar 9, 2023
@louisgv louisgv deleted the 492-bug-private-env-are-being-written-into-final-bundle branch March 9, 2023 18:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] Private env are being written into final bundle
2 participants