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

Mixing Deno with (Non-Deno) TypeScript - Different File Extension for Deno? #408

Closed
hediet opened this issue May 2, 2021 · 1 comment
Closed
Labels
duplicate This issue or pull request already exists

Comments

@hediet
Copy link

hediet commented May 2, 2021

Hi! Thanks for working on this awesome extension!

I am evaluating to use Deno for some build-scripts along a non-deno NodeJS + Browser TypeScript project. I like that it is very easy to bring in powerful and more importantly typed dependencies (unlike GitHub Actions, where there is no type system). This enables single-file scripts (without any package.json, tsconfig, node_modules, yarn.lock etc.).

However, it seems to me that the Deno language server and the TypeScript/JavaScript language server are mutually exclusive per project.
I guess this is due to both Deno and NodeJS files using the *.ts file extension.

What is you story for mixing Deno scripts with non-Deno TypeScript files?
Maybe it would be helpful if a custom file extension for Deno could be established.

@kitsonk kitsonk added the duplicate This issue or pull request already exists label May 2, 2021
@kitsonk
Copy link
Contributor

kitsonk commented May 2, 2021

This is a duplicate of #314 and am currently working on resolving.

@kitsonk kitsonk closed this as completed May 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants