Generate package.json #1257
Assignees
Comments
gosom
pushed a commit
to gosom/coala-bears
that referenced
this issue
Jul 15, 2017
To avoid duplication and mainitaining consistency of version of npm packages used in bears and those in the package.json. - Add template file .ci/package.json.jinja2 and write the main package.json according to the npm requirements of the bears. - Add check in travis.yml for the changes in package.json - Update the existing package.json to match the one generated by this code (in alphabetical order) - Add remark-lint package meta data to Markdown Bear, typescript package to TSLint Bear, babel-eslint and eslint-plugin-import package to the ESLint Bear Closes coala#1257
This was referenced Mar 28, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Each coala bear that uses Node.js should include a
NpmRequirementto describe any Node dependencies.For example, TSLintBear includes:
REQUIREMENTS = {NpmRequirement('tslint', '3')}package.json also includes
"tslint": "~3".This is unnecessary duplication, and the task is to remove that duplication, or ensure the two versions are consistent.
This task is to create a script, or modify
.ci/generate_requirements.py, which is run aftercoala-bearsis installed and writes a newpackage.jsonusing theNpmRequirementinformation in the bears.There may be some extra entries in package.json ; a template
.ci/package.jsonshould be used, preferably using jinja template language, to hold extra content for the real package.json.The text was updated successfully, but these errors were encountered: