Repository navigation
Support for Typescript 2.0 (typescript@next) #149
Description
When attempting to use the latest nightly build (Version 1.9.0-dev.20160623-1.0) in place of the bundled typescript compiler, it fails with the following message:
[14:34:35] TypeError: Cannot read property 'useCaseSensitiveFileNames' of null at matchFileNames (c:\work\browesrify-test\node_modules\typescript\lib\typescript.js:45447:29) at getFileNames (c:\work\browesrify-test\node_modules\typescript\lib\typescript.js:45296:20) at parseJsonConfigFileContent (c:\work\browesrify-test\node_modules\typescript\lib\typescript.js:45244:18) at parseOptions (c:\work\browesrify-test\node_modules\tsify\lib\Tsifier.js:75:16) at new Tsifier (c:\work\browesrify-test\node_modules\tsify\lib\Tsifier.js:109:23) at tsify (c:\work\browesrify-test\node_modules\tsify\index.js:12:16) at Browserify.plugin (c:\work\browesrify-test\node_modules\browserify\index.js:351:9) at Gulp.<anonymous> (c:\work\browesrify-test\gulpfile.js:154:5) at module.exports (c:\work\browesrify-test\node_modules\orchestrator\lib\runTask.js:34:7) at Gulp.Orchestrator._runTask (c:\work\browesrify-test\node_modules\orchestrator\index.js:273:3)
Activity
Matthalp-zz commentedon Jun 23, 2016
+1
typescript@next makes managing Typescript definition files much easier, so it would be great to have support in tsify. More details here:
https://blogs.msdn.microsoft.com/typescript/2016/06/15/the-future-of-declaration-files/
loilo commentedon Jul 12, 2016
Isn't this solved by #154 ?
basarat commentedon Jul 12, 2016
Its been solved since
1.0.0. Enjoy 🌹 ❤️basarat commentedon Jul 12, 2016
Yup #154 and #155 were the relevant fixes 🌹
loilo commentedon Jul 13, 2016
That's great! 👍
This doesn't support TS 2.0 module resolution features though, does it? At least I can't get it running.
That's not too surprising though, TypeScript itself does not rewrite the paths to relative or absolute ones during compilation so tsify will need to take care of the baseUrl/paths/... configs itself.
OliverJAsh commentedon Jul 13, 2016
Works for me, thanks!
loilo commentedon Jul 14, 2016
This seems to be better handled by a new issue regarding that concrete topic. I just opened one.