Skip to content

issues Search Results · repo:mysticatea/eslint-plugin-node language:JavaScript

Filter by

250 results
 (1 s)

250 results

inmysticatea/eslint-plugin-node (press backspace or delete to remove)

mysticatea/eslint-plugin-node
Missing Usage Information in the docs

Currently using Visual Studio Code, and the .eslintrc.json is not used anymore. Not sure how to use this, but even running eslint in the console, it wont check for the missing require rules.
question
  • rcfrias
  • 2
  • Opened 
    on Aug 30, 2018
  • #136

mysticatea/eslint-plugin-node
Parsing error: 'import' and 'export' may appear only with 'sourceType: module'

What it means? Parsing error: import and export may appear only with sourceType: module
  • frederikhors
  • 1
  • Opened 
    on Aug 10, 2018
  • #135

mysticatea/eslint-plugin-node
node>=v9.9.0, assert should use strict mode

node =9.9.0 var assert = require( assert ); // invalid, should report an error var assert = require( assert ).strict; // valid
  • aladdin-add
  • 1
  • Opened 
    on Aug 2, 2018
  • #134

mysticatea/eslint-plugin-node
deprecated assert.fail()

https://nodejs.org/dist/v10.0.0/docs/api/assert.html#assert_assert_fail_actual_expected_message_operator_stackstartfunction
accepted
breaking
enhancement
  • aladdin-add
  • 1
  • Opened 
    on Aug 2, 2018
  • #133

mysticatea/eslint-plugin-node
no-unsupported-features replaced by some other rules

~another way is keep the old rules, but adding replacedBy field in meta (just like eslint does)~ it s not documented.
  • aladdin-add
  • 2
  • Opened 
    on Jul 17, 2018
  • #129

mysticatea/eslint-plugin-node
Ignore node features rule only for some files

The node/no-unsupported-features rule is quite useful but usually while you want to keep a published npm module compatible with old Node.js versions, you d still want to write tests using newer language ...
question
  • lirantal
  • 3
  • Opened 
    on Jul 17, 2018
  • #128

mysticatea/eslint-plugin-node
`no-unsupported-features` allows unsupported Array prototype methods on Node runtime version v4.x.x

I am running Node.js version v4.2.2 with the no-unsupported-features ruleset enabled. I use the engines field in my package.json as follows: engines : { node : 4.2.2 } According to the compatibility ...
  • pdulapalli
  • 1
  • Opened 
    on Jun 4, 2018
  • #121

mysticatea/eslint-plugin-node
Allow to pass a version range to `no-unsupported-features`'s `version` option

The no-unsupported-features rules allow to set the Node version with either the engines field in the package.json or the version option. If set via the engines field in the package.json a version range ...
  • pvdlg
  • 1
  • Opened 
    on May 22, 2018
  • #119

mysticatea/eslint-plugin-node
[request] no-unsupported-features supports Node.js APIs other than ES features

Currently no-unsupported-features only supports ES features. Moreover, I think that it s wonderful if the Node API is also supported. For example - new globals: URL, URLSearchParams (since v10.0) ...
  • teppeis
  • 3
  • Opened 
    on May 4, 2018
  • #118

mysticatea/eslint-plugin-node
Missing from documentation: .gitignore check

The documentation only mentions .npmignore, but the rule also checks .gitignore: https://github.com/mysticatea/eslint-plugin-node/blob/2e2d464d9afe0ce1e1e2ad8899c6f744d182b4bb/lib/util/get-npmignore.js#L124 ...
accepted
documents
help wanted
  • mjomble
  • 3
  • Opened 
    on Apr 30, 2018
  • #117
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Press the
/
key to activate the search input again and adjust your query.
Issue search results · GitHub