klaviercat / pretty-jscpd Goto Github PK

As a developer, I want to have a script in my npm package to deploy to gh-pages. So that it could be run as part of the automated process of deployment and save me time.

as a developer, I want to set up Prettier and ESLint as part of the project, so that I can run linting and formatting my code right from the project with ease.

as a developer, I want Travis build to be run against all my PR branches and upon merge into master, so that I can be sure my changes do not break existing implementation.

As a developer, I want to convert this project to npm, so that I can run my lint, test, deploy etc. easier.

As a developer of pretty-jscpd, I want the project to have unit tests set up, so that my future changes will not break existing changes, and it also provides some documentation for development.

As a potential user of the app, I want to know what information will be presented and how they will be presented once I've uploaded my JSCPD report, so that:
(1) I can gauge if the data visualisation provided by this app is useful for me
(2) I can get the most out of the visualisation provided by the app

As a developer of pretty-jscpd, I want to set up Babel, so that I can use any ES6+ features that suit me without worrying about my users being restricted by the specific version of ECMAScript their browsers support.

As a user, I want to have a landing page of the site, so that I can access the site without knowing a specified page.

This will also be a useful place to provide some general info about the project, esp. related to how to use it.

As a developer, I want to set up E2E, so that I can be sure latest changes do not affect existing implementation.