You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 8, 2024. It is now read-only.
Would it make sense to build-in functionality to grunt-tsd that checks if all specified typings are present in the typings folder, and install them if any are missing?
This seems like a very fundamental use case, then you can put grunt-tsd-verify in the build task and developers never have to think about their typing files or tsd.
The text was updated successfully, but these errors were encountered:
So, the use case is I setup a project and don't check the typing files into git, and then when someone downloads the library and runs grunt, it will detect that the typing files are missing and install them automagically.
This could be solved by just checking the definitions into git which probably makes more sense. I don't like to do that because it messes up Github's language statistics and lines-of-code counter.
If you use TSD and install your definitions using --save, and check-in your tsd.json you can do this already (unless I miss-read your case).
When somebody downloads your project they can run TSD (either from cli or from grunt-tsd) and use reinstall (or update) and it will read the tsd.json and get those files.
Reinstall is safest as it is pinned to a commit-sha1 on DefinitelyTyped: sometimes definitions have breaking changes so a 'blind' update is risky.
If you want this automated you could look into npm scripts (post-install) and run grunt-tsd from there.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Would it make sense to build-in functionality to grunt-tsd that checks if all specified typings are present in the typings folder, and install them if any are missing?
This seems like a very fundamental use case, then you can put grunt-tsd-verify in the build task and developers never have to think about their typing files or tsd.
The text was updated successfully, but these errors were encountered: