remove eslint-plugin-standard

[dartcafe]

fix #101

[dartcafe]

@skjnldsv How are the rules, does the author of the PR the merge after review or someone like a release manager?

[skjnldsv]

You can merge :)

[skjnldsv]

Then you edit the CHANGELOG, and tag a new release with npm version and push --tags

[dartcafe]

@skjnldsv Hope, I did as expected. BTW: 5.0.0 changelog is missing. 😉

Hmmm. I guess, I did somethin wrong. I tried to push the changelog and the version update to the master branch, but is was rejected (understandable). As a result the package has a wrong version number (still 5.0.0)

Sorry to spam this PR The package seems to be ok, but how does the tree https://github.com/nextcloud/eslint-config/tree/v5.1.0 get merged to the master branch??

[skjnldsv]

Hmmm. I guess, I did somethin wrong. I tried to push the changelog and the version update to the master branch, but is was rejected (understandable). As a result the package has a wrong version number (still 5.0.0)

You should have done the changelog before the npm version.
Then you need to push the commit straight to master.
Or create a pr and once it's merged, create a release tagging the current master.

But creating a release automatically compile and publish the release to npm 🙈

[dartcafe]

I changed the changelog and did an npm version minor followed by push --tags. Trying to push to the master branch was rejected (no access?). Therefore I created #111.

The release package here is created from the tag and contains version 5.1.0. The package on npm still countains version 5.0.0.

[dartcafe]

But creating a release automatically compile and publish the release to npm 🙈

Yes. Learned that now... 😉

[skjnldsv]

The package on npm still countains version 5.0.0

Time to merge and release 5.1.1 🙈

[dartcafe]

Time to merge and release 5.1.1

Who? Me? Serious???? I don't grant for anything. 🤣