Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
no-restricted-modules doesn't check es6 modules #3196
Thanks for the issue! We get a lot of issues, so this message is automatically posted to each one to help you check that you've included all of the information we need to help you.
Reporting a bug? Please be sure to include:
Requesting a new rule? Please be sure to include:
Requesting a feature? Please be sure to include:
Including this information in your issue helps us to triage it and get you a response as quickly as possible.
Not in our case where we have a transitioning codebase, but I know you've
On Thu, Jul 30, 2015 at 2:13 PM Nicholas C. Zakas email@example.com
I'm just really worried about bundling these together when we don't know what format module strings will ultimately take. People "using" ES6 modules today are doing so built on the back of
If we do make a new rule, I guess we'd have to create a new rule and then deprecate this one?
One argument in favor of making them separate: AMD modules. If we wanted to add a
added a commit
Dec 1, 2015
I'm working on this.
Question. Trying to get
However can't produce any debug output. Any ideas on how to enable debug output when running a test?
Here is where I'm referencing it:
And here is where I'm using it: