-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Investigate deprecation of --compilers #2493
Comments
I just looked at the code, and it doesn't seem like Mocha is actually doing anything to associate the particular compiler with the particular extension, just |
I am a bot that watches issues for inactivity. |
I just double-checked control of As far as I can see, we should go ahead and document that |
@ScottFreeCode is this issue resolved? Does it require further action? |
As far as I recall, we figured out how to entirely replace |
@ScottFreeCode excellent! |
Created #3005 to prove with testing that one can glob multiple extensions, works in both OSes. The glob has changed since my prior investigation, due to upgrading the Glob package; it is now |
closed via #3038 |
--compilers
may be useless with later versions of Node.js, and commonly--require
is sufficient instead. Example:Is better written as
I don't know if this
Is equivalent to this:
If so, it's probably only true for some versions of Node.js and/or
coffee-script
.If you use a different extension with Babel--say
.es6
--I think you would need--compilers
? How does this work with TypeScript?Regardless,
--compilers js:some_module
may always be better written with--require
if that extension is.js
. Something similar is noted in the docs.The text was updated successfully, but these errors were encountered: