blitz-js / blitz-js/legacy-framework

Integrate `eslint-plugin-node/no-unsupported-features/node-builtins` once it's up par

Open
#43 1 comment 0 reactions 0 assignees View on GitHub
kind/bad-experience kind/meta legacy-framework status/blocked
Dominant language
JavaScript
Stars
3
Forks
2
PR merge metrics
No merged PRs in 30d

Description

### What do you want and why?

We already wanted to introduce `eslint-plugin-node/no-unsupported-features` in https://github.com/blitz-js/blitz/pull/454, bit it turned out that there's not really feature parity with what we expect.
Once that's up par, we should integrate it to provide a better DX.

### Possible implementation(s)

1. `yarn add -D -W eslint-plugin-node`
2. Add plugin to `.eslintrc`
3. Fix newly found linting bugs
### Additional context

![A dancing bug](https://media.giphy.com/media/xYVvUN8BBUbuw/source.gif)

Contributor guide

Open the contributing guide

Research direction

Start by checking whether eslint-plugin-node now provides the feature parity described in the issue. Then inspect the workspace dependency configuration and .eslintrc, enable the rule, and run the existing lint checks to identify any newly reported bugs. Done means the plugin is integrated and linting passes after the required fixes.

Written by the indexing model from the issue text.

Assessment

Tech stack
eslint, javascript
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.