-
-
Notifications
You must be signed in to change notification settings - Fork 738
TypeScript dependency should be a version range #720
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
Comments
Hello @adidahiya, currently TypeDoc is not able to support version ranges for typescript because it uses internal apis that could break even on patch versions. I am considering using a peer dependency on typescript in the future but that wouldn't be anytime soon. I'd have to go through and try and limit the api surface area to avoid unnecessary errors. It might be worth checking out https://github.com/TypeStrong/typedoc/blob/master/UPDATING.md for updating your own projects. |
Thanks for the response and link to the docs.
I would appreciate a change to make typescript a You should also consider testing with multiple versions of typescript in CI, like we do in tslint's .circleci/config.yml. |
the typescript dependency of this package should be:
this allows patch versions, which downstream libraries should be allowed to pick up. I don't want multiple copies of
typescript
in my node_modules unnecessarily. this would fix #718.have you had issues with allowing such a version range in the past?
The text was updated successfully, but these errors were encountered: