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(no-release): add conditional support in #if #52

Merged
merged 3 commits into from
Oct 29, 2024

Conversation

KevinEady
Copy link
Contributor

Uses acorn to create an AST of the condition, then visit the AST to return a result of the conditional: true, false, or undefined (when a result cannot be guaranteed).

Fixes: #51

@KevinEady
Copy link
Contributor Author

I have merged this branch into my local fork, ran the Sync Headers job manually, and got this PR: KevinEady#73 which removes the experimental conditional.

I marked this change as no-release: Once this branch is merged, there will be an update to the headers file via the Sync Headers job. That merge will create a new version of this package. I think that makes sense?

@KevinEady KevinEady force-pushed the add-conditional-if-support branch from 391b3d2 to adce36c Compare October 13, 2024 21:04
@mhdawson
Copy link
Member

We discussed today in the team meeting, the concensus seemed to be to land this and we'll discuss the inclusion or not of experimental as a follow on discussion.

Copy link
Member

@mhdawson mhdawson left a comment

Choose a reason for hiding this comment

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

LGTM

@mhdawson mhdawson merged commit e1b8feb into nodejs:main Oct 29, 2024
1 check passed
@github-actions github-actions bot mentioned this pull request Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Experimental node_api_nogc_env is not stripped
2 participants