Standalone TypeSpec Editing

[ByronMayne]

Hey Folks,

First off, this is a super neat project and we have been adopting it at my company to user for our internal services. The services we work on are mostly Asp.Net core so that is the lens I am framing my question from.

Question: Is it possible to have the VSCode extension provide the alias without having to use any package management system?

Take for example the code below;

import "@typespec/http";
using TypeSpec.Http;

Without doing tsp init which copies the node modules you will have compiler errors because it can't resolve the types. This make the TypeSpec files not as portable as they could be. For example when working with OpenApi you just need to have the schema and you can author it anywhere, where as TypeScript requires a ton of boilerplate in a ecosystem that would not be familiar to all.

The workflow I am trying to get is what already exists with OpenApi and [NSwag[(https://github.com/RicoSuter/NSwag). The idea being that you could write TypeSpec with intelisense in one place and have a Source Generator run TypeSpec compiler.

Does this seem like a too crazy idea?