semi-colons are not removed when import('./file') is used

[faceyspacey]

It appears the new import().next syntax breaks prettier-standard--at least when using it without an .eslintrc.js file.

[sheerun]

What eslint or prettier configuration can fix it?

[sheerun]

Hmm, it seems semicolons won't be removed if eslint encounters syntax error while parsing..

[sheerun]

@faceyspacey This needs to be fixed in here: https://github.com/prettier/prettier-eslint/issues

Could you raise this issue there?

[flybayer]

I think I'm having a similar issue.

Semicolons are not removed when I have ES6 classes with something = something else syntax like

  state = {
    ...
  }

  startRecording = (data) => {
    ...
  }

I tried using babel/semi as suggested in prettier/prettier-eslint#32 and prettier/prettier-eslint#56 but that's not working.

I have

  "eslintConfig": {
    "plugins": [
      "babel"
    ],
    "rules": {
      "babel/semi": [
        "error",
        "never"
      ]
    }
  },

[sheerun]

@flybayer Could you raise this issue to https://github.com/prettier/prettier-eslint/issues ?

[justsee]

@flybayer thanks for the head's up on the relevant tickets.

babel/eslint-plugin-babel#121 was merged and the test case supplied outlines an appropriate .eslintrc.

Once that's in place and eslint-plugin-babel is installed files should be processed correctly.

[flybayer]

@justsee thank you for the .eslintrc link!

I got it working!

On top of prettier-standard, you must install babel-eslint and eslint-plugin-babel.

Then add this to package.json:

  "eslintConfig": {
    "parser": "babel-eslint",
    "plugins": [
      "babel"
    ],
    "rules": {
      "babel/semi": [
        2,
        "never"
      ]
    }
  }

[danawoodman]

This is unfortunate as now it means you cannot use prettier-standard out of the gate with any project without configuration. Will this no longer be relevant when prettier-eslint fixes things or is this always going to be the case?

[sheerun]

I'll try to keep this module useful without configuration. Going to update in upcoming days

…

On Mon, 17 Apr 2017 at 02:56, Dana Woodman ***@***.***> wrote: This is unfortunate as now it means you can use prettier-standard out of the gate with any project without configuration. Will this no longer be relevant when prettier-eslint fixes things or is this always going to be the case? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAR2DRSnn6_x9ZjuiWLT_2BWKZjWSvTZks5rwri4gaJpZM4MmFUG> .

[sheerun]

This issue on prettier-eslint needs to be fixed first, please help to make it so:

prettier/prettier-eslint#68

[sheerun]

@faceyspacey This should be fixed in 4.1.0, could you check?

[sheerun]

Also, please feel free to add yourself to contributors list

[danawoodman]

@sheerun nice, this seems to do it! Thanks! 🍻