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

--watch flag does not watch .mjs files #6800

Closed
jacksonrayhamilton opened this Issue Nov 11, 2017 · 3 comments

Comments

Projects
None yet
5 participants
@jacksonrayhamilton

jacksonrayhamilton commented Nov 11, 2017

I've tried compiling continuously with babel-cli's --watch. It will continuously compile a file with a ".js" extension. But when I change the source file's extension to ".mjs", continuous compilation does not work; changes to files are not compiled.

I expect that any file I have specified to compile will automatically be watched, regardless of what extension it has.

@babel-bot

This comment has been minimized.

Show comment
Hide comment
@babel-bot

babel-bot Nov 11, 2017

Collaborator

Hey @jacksonrayhamilton! We really appreciate you taking the time to report an issue. The collaborators
on this project attempt to help as many people as possible, but we're a limited number of volunteers,
so it's possible this won't be addressed swiftly.

If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack
community that typically always has someone willing to help. You can sign-up here
for an invite.

Collaborator

babel-bot commented Nov 11, 2017

Hey @jacksonrayhamilton! We really appreciate you taking the time to report an issue. The collaborators
on this project attempt to help as many people as possible, but we're a limited number of volunteers,
so it's possible this won't be addressed swiftly.

If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack
community that typically always has someone willing to help. You can sign-up here
for an invite.

@jacksonrayhamilton

This comment has been minimized.

Show comment
Hide comment
@jacksonrayhamilton

jacksonrayhamilton Nov 11, 2017

For the record, I found that I could work around this with --extensions ".mjs",".js".

Still, I believe that it'd be more intuitive if the files specified in the command were watched, regardless of their extensions. Seems like changing this code would effect that change?

Also, I think the documentation for the --extensions flag should be more precise. "List of extensions to hook into" is not an informative description.

Also, I think the default value for the --extensions flag should be updated to include ".mjs", since this is the extension that Node is using now.

jacksonrayhamilton commented Nov 11, 2017

For the record, I found that I could work around this with --extensions ".mjs",".js".

Still, I believe that it'd be more intuitive if the files specified in the command were watched, regardless of their extensions. Seems like changing this code would effect that change?

Also, I think the documentation for the --extensions flag should be more precise. "List of extensions to hook into" is not an informative description.

Also, I think the default value for the --extensions flag should be updated to include ".mjs", since this is the extension that Node is using now.

@jaydenseric

This comment has been minimized.

Show comment
Hide comment
@jaydenseric

jaydenseric Feb 7, 2018

I'm using v7.0.0-beta.39 and this issue seems to be fixed, can it be closed?

jaydenseric commented Feb 7, 2018

I'm using v7.0.0-beta.39 and this issue seems to be fixed, can it be closed?

@loganfsmyth loganfsmyth closed this Mar 5, 2018

@lock lock bot added the outdated label Jun 4, 2018

@lock lock bot locked as resolved and limited conversation to collaborators Jun 4, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.