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

Main configuration file (tsb.json) #17

Closed
basarat opened this issue Sep 23, 2015 · 3 comments
Closed

Main configuration file (tsb.json) #17

basarat opened this issue Sep 23, 2015 · 3 comments
Labels

Comments

@basarat
Copy link
Member

basarat commented Sep 23, 2015

People need multiple tsconfig.json files, but its difficult to know without user intervention what their plan is with all these files.

Spec out (and use) something like a tsproject.json (or call it tsb.json?)

Also support other things like:

  • tslint.json
  • package.json
  • tsd.json
  • formatCodeOptions
  • webpack config
  • launch.json

Refs (Most tsconfig issues):

Heirarchical tsconfig : microsoft/TypeScript#1928
Mutiple tsconfig : microsoft/TypeScript#4714
Medium sized projects dependencies : microsoft/TypeScript#3469
name property : microsoft/TypeScript#2938

@basarat
Copy link
Member Author

basarat commented Sep 24, 2015

Sample :

{
    "projects": [
        {
            "name": "somename",
            "tsconfig": "path to tsconfig.json",
            "launch" : "path to launch.json",
            "tsd" : "path to tsd.json",
            "package" : "path to package.json"
        }
    ]
}

@basarat basarat changed the title tsproject.json Main configuration file Sep 24, 2015
@basarat basarat changed the title Main configuration file Main configuration file (tsb.json) Oct 16, 2015
@basarat
Copy link
Member Author

basarat commented Oct 16, 2015

Also if there are multiple tsconfig.json people generally want to see errors from only one tsconfig.json. Otherwise the error panel becomes fairly useless fairly quickly

@basarat
Copy link
Member Author

basarat commented Nov 10, 2015

To decrease barrier to entry we went with just tsconfig.json detection for now

@basarat basarat closed this as completed Dec 24, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant