Skip to content

Eslint reports multiple problems and current npm reports vulnerabilities #5

Description

@JimBledsoe

The eslint script reports multiple warnings:

  • Hundreds reported on console or indentation problems on the examples bundles if you have run the test scripts - All bundles should be ignored, and console statements in the examples are not a critical thing.
  • The following are valid warnings:
    -- chrome-dev-webpack-plugin/test/02-json-loader-file.js
    26:9 error Unexpected console statement no-console
    30:9 error Unexpected console statement no-console
    -- chrome-dev-webpack-plugin/test/04-version-stamp.js
    104:37 error 'err' is defined but never used no-unused-vars
    -- chrome-dev-webpack-plugin/test/05-examples.js
    137:12 error 'i' is already defined no-redeclare
    137:19 error 'len' is already defined no-redeclare

Using npm 5 or 6 will report many vulnerabilities, one of which is critical. Mocha and nyc can be updated to eliminate the vulnerabilities.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions