electron / electron/forge

Is there a way to get type-checking errors back on the command line?

Open
#3,085 2 comments 4 reactions 0 assignees View on GitHub
cli question typescript
Dominant language
TypeScript
Stars
7.1k
Forks
641
Avg merge
3d 1h
Merged PRs (30d)
30

Description

### Pre-flight checklist

- [X] I have read the [contribution documentation](https://github.com/electron/forge/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [code of conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project uses.
- [X] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

### Problem description

Love the project, appreciate all your work on it.
This may better fit as a "question", but sadly I've not been able to access your Discord.

The question:
Is there a way to get type-checking errors back on the command line?

I had been using version `6.0.0-beta.65` for some time, and when running `electron-forge start` I regularly got terminal feedback along these lines for type errors:

```
ERROR in editor.ts
../EditorCore/src/editor.ts 134:21-25
[tsl] ERROR in editor.ts(134,22)
TS2552: Cannot find name 'msg_'. Did you mean 'msg'?
@ ../EditorCore/src/start.tsx 18:17-36
@ ../EditorCore/src/index.ts 7:14-32
@ ./src/renderer.js 8:0-35 26:0-5
```

(That's just an intentionally-added error, misspelling a variable FWIW.)

After upgrading to v6.0.3 I still get that feedback - but over the Electron GUI, not in the terminal.
Is there a way to re-enable this on the terminal?

I did see this (now pretty old) issue and comment:
https://github.com/electron-userland/electron-forge-templates/issues/27#issuecomment-294277496
and elsewhere saw the recommendation to (just) separately run `tsc --watch` or similar. Which I can do. But would love if there's a switch or option for `electron-forge` to enable it while running the dev server.

### Proposed solution

-

### Alternatives considered

-

### Additional information

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.