lit / lit/lit

Typescript Starter Project Not Linting

Open
#4,698 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
21.8k
Forks
1.1k
Avg merge
18h 25m
Merged PRs (30d)
2

Description

### Which package(s) are affected?

Other/unknown (please mention in description)

### Description

I'm testing out the linting script to see if I can get it to trigger. I described the setup and the results in this SO question:
https://stackoverflow.com/questions/78727953/catching-errors-with-the-linteslint-script-in-the-lit-typescript-starter-projec

### Reproduction

Please see this SO question:

https://stackoverflow.com/questions/78727953/catching-errors-with-the-linteslint-script-in-the-lit-typescript-starter-projec

In `my-element.ts` added a property with undefined any like this below the name property:

```
/**
* The name to say "Hello" to.
*/
@property()
name = 'World';

test;
```

And the vscode linter catches this, but when I run `npm run lint:eslint` it does not catch it.

### Workaround

Use the VSCode linter ....

### Is this a regression?

No or unsure. This never worked, or I haven't tried before.

### Affected versions

3.20

### Browser/OS/Node environment

MacOS Sonoma 14.5
Node v20.15.0
Latest Typescript Project

Contributor guide

Open the contributing guide

Research direction

Start with the TypeScript starter project's `npm run lint:eslint` entry point and the `my-element.ts` reproduction described in the issue. Compare its result with the VS Code linter for the added `test;` property; done means the command reports the same undefined-typed property problem.

Written by the indexing model from the issue text.

Assessment

Tech stack
eslint, typescript
Domain
tooling
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.