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

Dependency Map? #3415

Closed
blendsdk opened this issue Jun 8, 2015 · 3 comments
Closed

Dependency Map? #3415

blendsdk opened this issue Jun 8, 2015 · 3 comments
Labels
Duplicate An existing issue was already created Question An issue which isn't directly actionable in code

Comments

@blendsdk
Copy link

blendsdk commented Jun 8, 2015

Hi,

Is there a "Dependency Map" export option in the ts compiler. I am working on a fairly large UI framework with many classes and modules. Applications using this framework are not going to use all the classes all the time. Next to that, many of these classes need their corresponding css files, for example: "My.Button" class needs "My.Button.css". It would be very useful to see which classes are "actually used" in the project so we can bundle only those classes/files when building the final .js file.

Any thoughts?

Regards,
Gevik.

@mhegazy
Copy link
Contributor

mhegazy commented Jun 8, 2015

The compiler does not provide this as a feature out-of-the box. there are tools that can do that for you. for instance @basarat's https://atom.io/packages/atom-typescript has a dependency graph view.

@mhegazy mhegazy added the Question An issue which isn't directly actionable in code label Jun 8, 2015
@danquirk
Copy link
Member

danquirk commented Jun 8, 2015

You probably want to +1 this issue #1479

@danquirk danquirk closed this as completed Jun 8, 2015
@danquirk danquirk added the Duplicate An existing issue was already created label Jun 8, 2015
@basarat
Copy link
Contributor

basarat commented May 19, 2016

Note : alm has this as well : https://basarat.gitbooks.io/alm/content/features/dependency.html 🌹

@microsoft microsoft locked and limited conversation to collaborators Jun 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Duplicate An existing issue was already created Question An issue which isn't directly actionable in code
Projects
None yet
Development

No branches or pull requests

4 participants