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

Make setting up a tuned TypeScript project easy as 🥧 #121345

Open
Tracked by #118402
JacksonKearl opened this issue Apr 15, 2021 · 7 comments
Open
Tracked by #118402

Make setting up a tuned TypeScript project easy as 🥧 #121345

JacksonKearl opened this issue Apr 15, 2021 · 7 comments
Assignees
Labels
feature-request Request for new features or functionality getting-started
Milestone

Comments

@JacksonKearl
Copy link
Contributor

Currently it takes quite a bit of product knowledge to set up a TypeScript project and get all the nice features VS Code has to offer. Examples:

  • What should my tsconfig.json include?
  • How can I run my project?
  • How can I get debugging to work?
  • How should I run my build/watch?
  • How can I set up tests?
  • How should I lint/format the code?

And probably lots more...

This issue tracks making these questions easy to answer, the starting point for this will be developing start list contributions to instantiate template folders that have been tuned to make the development/build/test/debug process as seamless as possible.

@JacksonKearl
Copy link
Contributor Author

cc @gcrev93, @DanielRosenwasser

@connor4312
Copy link
Member

connor4312 commented Apr 19, 2021

Something that would remove one toekick for generic TS setup (mainly in the 'debugging' step) would be if the compiler would create sourcemaps by default. I'm sure there's reasoning behind why it's not the case, but I couldn't find it and I think sourcemaps are desired in vastly more cases nowadays than they're undesired.

@digitarald
Copy link
Contributor

Adding to the list of ideas:

  • Detecting/installing Node/NPM & typescript package
  • TS Playground

@gcrev93
Copy link

gcrev93 commented Jul 21, 2021

Just chiming in:

I think we can help with the tsconfig question by using the basic tsconfig created when you run tsc --init ! Its well commented and gives explanation on each option in the file

It would also be great for Compile and Running your projects to potientially be as easy as a button click.

I do agree node packages being detected/installed as well.

@gcrev93
Copy link

gcrev93 commented Aug 25, 2021

As a starting solution, we discussed a simple solution:

Having a welcome page for TypeScript that has the following steps:

  1. Tells users how to download TS
  2. Has a button that allows users to create a simple TS solution . (This will use tsc --init to create a base tsconfig and then
  3. Shows users how to compile their code with tsc

I think our simple solution can also assist here #124280 . it is mentioned that the having a base tsconfig can speed up the run/debug

I would love to hear your thoughts @JacksonKearl @DanielRosenwasser @digitarald

Also going to mention @connor4312 since its his comment I am referring to

@DanielRosenwasser
Copy link
Member

I think making sure that a user has Node.js installed is a good one to note too.

@yume-chan
Copy link
Contributor

How about editing tsconfig.json with the built-in settings editor #104044?

@mjbvz mjbvz added the feature-request Request for new features or functionality label Oct 11, 2021
@lramos15 lramos15 assigned lramos15 and unassigned JacksonKearl May 25, 2022
@bhavyaus bhavyaus assigned bhavyaus and unassigned lramos15 Dec 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features or functionality getting-started
Projects
None yet
Development

No branches or pull requests

9 participants