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 Apr 30, 2019. It is now read-only.
If I have a package named company/my-package, tsd does not like it:
$ ./node_modules/.bin/tsd reinstall
-> running reinstall
path not in index, attempt-adding: company/my-package.d.ts
-> an error occured!
Cannot read property 'commit' of null
TypeError: Cannot read property 'commit' of null
at ContentLoader.loadContent (/Users/brad/company/my-package/node_modules/tsd/build/tsd/logic/ContentLoader.js:44:63)
at /Users/brad/company/my-package/node_modules/tsd/build/tsd/logic/Installer.js:75:39
at tryCatch1 (/Users/brad/company/my-package/node_modules/tsd/node_modules/bluebird/js/main/util.js:63:19)
at Promise$_callHandler [as _callHandler] (/Users/brad/company/my-package/node_modules/tsd/node_modules/bluebird/js/main/promise.js:695:13)
at Promise$_settlePromiseFromHandler [as _settlePromiseFromHandler] (/Users/brad/company/my-package/node_modules/tsd/node_modules/bluebird/js/main/promise.js:711:18)
at Promise$_settlePromiseAt [as _settlePromiseAt] (/Users/brad/company/my-package/node_modules/tsd/node_modules/bluebird/js/main/promise.js:868:14)
at Promise$_settlePromises [as _settlePromises] (/Users/brad/company/my-package/node_modules/tsd/node_modules/bluebird/js/main/promise.js:1006:14)
at Async$_consumeFunctionBuffer [as _consumeFunctionBuffer] (/Users/brad/company/my-package/node_modules/tsd/node_modules/bluebird/js/main/async.js:74:12)
at Async$consumeFunctionBuffer (/Users/brad/company/my-package/node_modules/tsd/node_modules/bluebird/js/main/async.js:37:14)
at process._tickCallback (node.js:355:11)
Do we want to add support for these types of packages? In my case I've got a bunch of smaller projects that I want to share definition files between them. They're published on NPM under a scope @company, so for example I would do npm install @company/my-package.
The text was updated successfully, but these errors were encountered:
@bradleyayers Yes, I think this is something that should be supported. I'm going to be looking into and proposing some updates soon, so I'll keep you posted as I work on this.
If I have a package named
company/my-package
, tsd does not like it:In my
tsd.json
I have:Do we want to add support for these types of packages? In my case I've got a bunch of smaller projects that I want to share definition files between them. They're published on NPM under a scope
@company
, so for example I would donpm install @company/my-package
.The text was updated successfully, but these errors were encountered: