CLI and Tooling

Initializing a Project

# TypeScript
# Switch into directory
npm init .
tsc --init .

# Modify tsconfig.json and package.json as necessary

# Use templates
npx create vite .

# .NET
# List the types of projects
dotnet new list

# Create a project using a template
dotnet new webapi
dotnet new console

Building a Project

# TypeScript
# Assuming a script for "build" in package.json
npm run build

# .NET
dotnet build

Hot Reload

# TypeScript
# Assuming the project has been configured with a watcher in package.json
# Assuming the tsconfig.json has watchOptions set up.
npm run build:watch

# .NET
dotnet watch

# To avoid manually confirming "rude edits"
dotnet watch --non-interactive

Check it out in action here as we generate OpenAPI bindings on save:

Learn more about build-watch:

• TypeScript build-watch
• dotnet watch

Adding Packages

# TypeScript

# Local package is set up via package manager and config files.

# Remote package
yarn add some-package
yarn add -D some-package

npm install some-package
npm install --save-dev some-package

# .NET

# Local package
dotnet add reference ../other-project/my-other-project.csproj

# Remote package
dotnet add package SomeRemotePackage

Generally, workspace management for local package references requires configuration based on the package manager selected

• Yarn,
• NPM,
• pnpm