Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vscode warnings when editing freshly generated project #385

Open
BurtHarris opened this issue Jul 15, 2022 · 1 comment
Open

vscode warnings when editing freshly generated project #385

BurtHarris opened this issue Jul 15, 2022 · 1 comment

Comments

@BurtHarris
Copy link

Describe the bug
After generating a project with create-nodejs-ts, when I open the project using Microsoft Visual Studio Code (vscode) several error messages are popping up saying that some of the add-ins are terminating.

To Reproduce
Steps to reproduce the behavior:

  1. From c:\try I execute npm create nodejs-ts, creating a \try\my-app directory
  2. code my-app opens the vscode editor

** Observed **
VSCode has outputs errors related to jest. It is complaining that an external process running jest has terminated. The text says:

'"jest.cmd"' is not recognized as an internal or external command,
operable program or batch file.
Jest process "watch-tests" ended unexpectedly
 see troubleshooting: https://github.com/jest-community/vscode-jest/blob/master/README.md#troubleshooting

Expected behavior
Normal VsCode startup

Diagnosed Issue
The template seemed to have left out two steps VsCode assumes have been done.

  • git init
  • npm install (or equivalant)

It obviously wasn't a big deal to figure that out, but for less experienced devs, executing those steps would be great.

Screenshots
If applicable, add screenshots to help explain your problem.

image

Environment (please complete the following information):

  • OS: Windows 11 Pro. version 22H2, (OS Build 22621.232)
PS C:\Try\my-app> npm -v
8.13.2
\\PS C:\Try\my-app> node -v
v18.5.0
PS C:\Try\my-app> code -v
1.69.1
b06ae3b2d2dbfe28bca3134cc6be65935cdfea6a
x64

Additional context

Thanks, for your efforts so far. This is obviously only a minor glitch.

@vitorsalgado
Copy link
Owner

Hello @BurtHarris
I'll try to check this soon. busy week here 🥲

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants