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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃殌 Move from custom logic to babel evaluate #27564

Closed

Conversation

kristoferbaxter
Copy link
Contributor

A followup to #27516. This PR removes much of the one-off logic and instead uses Babel's evaluate functionality.

Copy link
Contributor

@jridgewell jridgewell left a comment

Choose a reason for hiding this comment

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

Woo

@kristoferbaxter
Copy link
Contributor Author

Going to undo this change, path.skip frequency is lowering the usage of this plugin with the evaluate step.

Going to try and refactor to avoid conditions where evaluate would necessitate a path.skip().

@kristoferbaxter
Copy link
Contributor Author

Closing this pull request, we need better test cases for a refactor to meet the conditions of the current implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants