Ensures es6 Imports and Exports Don't Cause Errors

[ggwicz]

Before this change, let's say you have some simple code like the following atop a JS file:

import Cool from './Cool';
import Wow from './Wow';

Even with es6: true enabled in our coding standards' .eslintrc.js file, these trigger a linting error as follows:

Parsing error: 'import' and 'export' may appear only with 'sourceType: module'

This is an error that is often fixed just by adding sourceType: module to the .eslintrc.js's parserOptions option, but I've found that it required all of the changes seen in this file diff to make it work.

[aubreypwd]

@ggwicz Just acknowledging this. Are we sure that this doesn't affect es5 JS? Also do you think you could also add a patch for this in https://github.com/WebDevStudios/js-coding-standards which will be the future home of JS coding standards?

[ggwicz]

@aubreypwd To my knowledge there shouldn't be negative effects is using es5, since es6 is backwards compatible. And this change is additive—it just whitelists an es6 feature, essentially, no blacklisting of es5 features.

[ggwicz]

This is now recreated over in the JS Coding Standards repo → WebDevStudios/js-coding-standards#6

[aubreypwd]

With the new modern package js-coding-standards, I am not experiencing this:

Could you verify if this is still happening for you using the newer package?

[aubreypwd]

Closing out for WebDevStudios/eslint-config-js-coding-standards#6 since WDS-Coding-Standards will soon be deprecated.