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

Make -r RegExp Windows compatible #13

Merged
merged 1 commit into from
Jul 5, 2019
Merged

Conversation

depoulo
Copy link
Contributor

@depoulo depoulo commented Jul 5, 2019

This also removes the trailing slash from the path, I don't know exactly why but that made it fail in my repo.

This also removes the trailing slash from the path, I don't know exactly why but that made it fail in my repo.
@depoulo depoulo changed the title 🔧 Make -r RegExp Windows compatible Make -r RegExp Windows compatible Jul 5, 2019
@obahareth obahareth merged commit 6de44df into obahareth:master Jul 5, 2019
@obahareth
Copy link
Owner

Thank you so much @depoulo!

@depoulo
Copy link
Contributor Author

depoulo commented Jul 6, 2019

Thanks for merging. As for releasing, I'm no longer entirely sure regarding the trailing slash removal, will get back to that on Monday.

@depoulo depoulo deleted the patch-1 branch July 8, 2019 07:58
depoulo added a commit to depoulo/are-you-es5 that referenced this pull request Jul 8, 2019
I had removed it in obahareth#13 (sorry, I had been struck by yarnpkg/yarn#4722)

The behaviour _with_ the trailing path delimiter is more correct, as without it in theory modules starting with the same name as a non-ES5 node_module would be unneccessarily transpiled.

This is all assuming the leading and trailing slash before obahareth#13 were meant as path delimiters and not RegExp delimiters, meaning that anyone wanting to use the RegExp would (and will) have to add surrounding slashes or `new RegExp()` manually, as in `/<place-output-here>/` or `new RegExp('<place-output-here>')` (personally, I'm writing the output of _are-you-es5_ to a file on _postinstall_ and read it into a `new RegExp()` in the webpack config).
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.

2 participants