Host @types packages individually on GitHub
See original GitHub issue@types packages are generated from DefinitelyTyped and published to the npm registry. These packages are included by listing them as a dependency in a project’s package.json
, just like any other npm dependency. Unlike most npm dependencies, however, there is no simple way to fork an @types package and declare the fork as a dependency.
As an example, I’ve had need of an updated type definition for vega, so I started working on a PR to DT, except there was no easy way to develop this update (save going into my node modules folder and making changes). I would be incredibly useful if I could find a repository for the published package at a known location (linked to in the package.json), so I could fork it and list the fork as a dependency (for example: "@types/vega": "weswigham/AtTypes-vega"
) in my package.json while I work on it/while I wait for the PR to be reviewed.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:8
- Comments:11 (11 by maintainers)
Top GitHub Comments
Something like https://github.com/Microsoft/types-publisher/issues/4?
@weswigham That doesn’t help contributing back. What would that look like? Fork it, make changes, push, fork DefinitelyTyped, copy and paste changes, make PR, pull from fork when
types-publisher
runs, repeat? How does anyone use the definition while waiting for their PR to DefinitelyTyped to be merged?