-
Notifications
You must be signed in to change notification settings - Fork 232
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
Enable npm init @cadl-lang using @cadl-lang/create package #1041
Comments
|
does |
|
pri: 0 |
I was supposed to split this up, but didn't yet, but looks like @timotheeguerin filed #1116 already. |
So this one can be about the init part and that one can be about needing global cadl to resolve local one unnecessarily. |
est: 3 |
Two issues are discussed below but this one tracks only getting
npm init @cadl-lang
to work as a nicer/easier to remember command-line thannpx -p @cadl-lang/compiler cadl init
The other issue, making local cadl resolve without a global cadl is tracked by #1116
It would be nice if you could play with cadl without installing it globally via npm install -g.
I tried these steps:
This errors starting the language server, it can't find the cadl-server executable. We should be able to make it find it off workspace root without relying on the global executable to run its resolver for this case. That should be a relatievely straight-forward fix. (EDIT: tracked by #1116)
The other problem I see in this scenario is that I can't use
npx cadl init
to get started because I need to npm install @cadl-lang/compiler first whilecadl init
templates help me to do that. Chicken and egg. (Edit: we can makenpm init @cadl-lang
work with a@cadl-lang/create
package, this issue now tracks that.)We should probably fix the reliance on global cadl to find local cadl (EDIT: tracked by #1116) and then at least document an alternate flow that doesn't require npm install -g.
The text was updated successfully, but these errors were encountered: