Old eslint version referenced in npm-published v1.5.0

[mosermanuel]

Version 1.5.0, which is published in the global npm-repository (https://www.npmjs.com/package/plato), has an old eslint version referenced (^0.7.4). This makes plato unpossible to use with current versions of eslint. Is there a way to publish a new version of plato, with a new eslint version referenced (like in master)?

Thx!

[p-bakker]

Ran into this as well, looks like more dependancies are out of date: https://www.versioneye.com/nodejs/plato/1.5.0

The version of fs-extra is so old, that is it incompatible with newer versions of Node.

I also wonder about Plato version 1.5.0 being availabel on NPM, while if I look under Releases in this repository on gitHub, the latest release is v1.2.1, with 3 newer tags going up to v1.4.0. No mention of a v1.5.0 in this repo at all. Wondering what is actually published on NPM

[syke80]

Hi Guys, (The Maintainers)

Could you please drop a comment here with an ETA on proposed resolution?
It's getting a quite important on some projects as ESLint is at v2.11.1

Thanks a lot!

[mosermanuel]

Hi Guys,

are there any plans for that task?

Thanks!

[jsoverson]

Sorry all, haven't been on top of github issues for some time. This project is (obviously) pretty much unmaintained right now and could use both someone to keep v1 alive (with PRs like this) and someone to advance it to modern best practices in a v2.

Any takers?