lirantal / lirantal/create-node-lib
Bug: a stock clone of the repo has issues with the linter
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 45
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
## Expected Behavior
I can commit all files after I scaffolded them
## Current Behavior
Right after generating the template, if I add and commit the files to the repo, the commit checks fail on a lint error that needs to be fixed:
```sh
✖ pnpm run lint:fix:
$ eslint . --fix /.changeset/config.json /.devcontainer/devcontainer.json /.prettierrc.json /eslint.config.js package.json tsconfig.json
.changeset/config.json
0:0 warning File ignored because no matching configuration was supplied
.devcontainer/devcontainer.json
0:0 warning File ignored because of a matching ignore pattern. Use "--no-ignore" to disable file ignore settings or use "--no-warn-ignored" to suppress this warning
.prettierrc.json
0:0 warning File ignored because no matching configuration was supplied
__tests__/app.test.ts
12:45 error 't' is defined but never used @typescript-eslint/no-unused-vars
package.json
0:0 warning File ignored because no matching configuration was supplied
tsconfig.json
0:0 warning File ignored because no matching configuration was supplied
✖ 6 problems (1 error, 5 warnings)
[ELIFECYCLE] Command failed with exit code 1.
husky - pre-commit script failed (code 1)
```
## Possible Solution
## Steps to Reproduce (for bugs)
1.
2.
3.
4.
## Context
## Your Environment
- Library Version used:
- Node.js version (e.g. Node.js 5.4):
- Operating System and version (desktop or mobile):
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running pnpm run lint:fix and inspect __tests__/app.test.ts, eslint.config.js, and the listed JSON configuration files. Determine why the unused t error and ignored-file warnings occur, then verify that the generated template's commit checks complete without a lint failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- eslint, javascript, nodejs, typescript
- Domain
- ci-cd, tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100