NPM scripts fail in Windows because they are setting environment variables without using cross-env or similar. VS Code Dev Containers are probably the simplest way to make it work in Windows without any code changes, at least for Visual Studio Code users.
The commit contains a configuration file with the default image for TypeScript development with latest Node.js version and two extensions that make a lot of sense for the project:
The .gitattributes file forces LF line endings to avoid problems with phantom file changes when cloning the project in Windows and using Git inside the Dev Container.
Having these 2 files in the repository should make it much easier to get to a working development environment in Windows.
NPM scripts fail in Windows because they are setting environment variables without using cross-env or similar. VS Code Dev Containers are probably the simplest way to make it work in Windows without any code changes, at least for Visual Studio Code users.
The commit contains a configuration file with the default image for TypeScript development with latest Node.js version and two extensions that make a lot of sense for the project:
The
.gitattributesfile forces LF line endings to avoid problems with phantom file changes when cloning the project in Windows and using Git inside the Dev Container.Having these 2 files in the repository should make it much easier to get to a working development environment in Windows.