jeffijoe
TypeSync
Install missing TypeScript typings for dependencies in your package.json.
Install
npm install -g typesyncYou can also use it directly with npx which will install it for you:
npx typesyncUsage
typesync [path/to/package.json] [--dry]Path is relative to the current working directory. If omitted, defaults to package.json.
Note: TypeSync only modifies your package.json - you still need to run an installer.
--dry[=fail]
If --dry is specified, will not actually write to the file, it only prints added/removed typings.
The same is true for --dry=fail, with the additional effect of failing the command in case there are changes.
This is useful for CI scenarios.
--ignoredeps
To ignore certain sections, you can use the --ignoredeps= flag. For example, to ignore devDependencies, use --ignoredeps=dev. To ignore multiple, comma-separate them, like this: --ignoredeps=deps,peer (ignores dependencies and peerDependencies).
--ignoredeps=deps— ignoresdependencies--ignoredeps=dev— ignoresdevDependencies--ignoredeps=peer— ignorespeerDependencies--ignoredeps=optional— ignoresoptionalDependencies
--ignorepackages
To ignore certain packages, you can use the --ignorepackages= flag. For example, to ignore nodemon, use --ignorepackages=nodemon.
To ignore multiple, comma-separate them, like this: --ignorepackages=nodemon,whatever (ignores nodemon and whatever).
Using a config file
Alternatively, you can use a TypeSync config file: .typesyncrc or a "typesync" section in your package.json. TypeSync will automatically search for configuration files. See cosmiconfig for details.
// .typesyncrc
{
"ignoreDeps": ["dev"],
"ignorePackages": ["nodemon"]
}Run TypeSync automatically after every install
To run TypeSync and install packages automatically after every package install, create a file called install-with-types.sh with the following content:
npm install $1
npx typesync
npm installIf you use yarn, use this instead:
yarn add $1
yarn typesync
yarnRun this command to make the file executable:
chmod +x install-with-types.shAdd the following to package.json:
{
"scripts": {
"i": "./install-with-types.sh"
}
}Then install packages like this:
npm run i <pkg name>
# Or with Yarn:
yarn i <pkg name>Typings packages
TypeSync will add typings for packages that:
- have a
@types/packageavailable - don't already provide typings internally (the
typingsandtypesfield inpackage.json)
TypeSync will try to respect SemVer parity for the code and typings packages, and will fall back to the latest available typings package.
When writing the typings package version to package.json, the ~ SemVer range is used. This is because typings published via DefinitelyTyped align typings versions with library versions using major and minor only.
For example, if you depend on react@^16.14.0, then TypeSync will only look for typings packages that match 16.14.*.
Monorepos
TypeSync added support for monorepos in v0.4.0. It will look at packages/workspaces globs in package.json and sync every matching file in one fell swoop.
Why?
Installing typings manually sucks. Flow has flow-typed which installs type definitions by looking at a package.json, which would be cool to have for TypeScript. Now we do!
Changelog
See CHANGELOG.md
Author
Jeff Hansen - @Jeffijoe