最新消息:雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客

gulp打字稿时的TypeError

运维笔记admin12浏览0评论

gulp打字稿时的TypeError

gulp打字稿时的TypeError

我执行我的Typescript转换时遇到以下错误:

TypeError: file.isSymbolic is not a function
    at DestroyableTransform.normalize [as _transform] (D:\project\node_modules\vinyl-fs\lib\dest\prepare.js:31:15)
    at DestroyableTransform.Transform._read (D:\project\node_modules\vinyl-fs\node_modules\readable-stream\lib\_stream_transform.js:182:10)
    at DestroyableTransform.Transform._write (D:\project\node_modules\vinyl-fs\node_modules\readable-stream\lib\_stream_transform.js:170:83)
    at doWrite (D:\project\node_modules\vinyl-fs\node_modules\readable-stream\lib\_stream_writable.js:406:64)
    at writeOrBuffer (D:\project\node_modules\vinyl-fs\node_modules\readable-stream\lib\_stream_writable.js:395:5)
    at DestroyableTransform.Writable.write (D:\project\node_modules\vinyl-fs\node_modules\readable-stream\lib\_stream_writable.js:322:11)
    at Pumpify.Duplexify._write (D:\project\node_modules\pumpify\node_modules\duplexify\index.js:201:22)
    at doWrite (D:\project\node_modules\pumpify\node_modules\readable-stream\lib\_stream_writable.js:406:64)
    at writeOrBuffer (D:\project\node_modules\pumpify\node_modules\readable-stream\lib\_stream_writable.js:395:5)
    at Pumpify.Writable.write (D:\project\node_modules\pumpify\node_modules\readable-stream\lib\_stream_writable.js:322:11)

我的gulp任务看起来像这样:

gulp.task('tsc', function () {
    let tsResult =  gulp.src(srcPaths.tsFiles)
        .pipe(tsProject()); // tsProject created previously

    return tsResult.js
       .pipe(gulp.dest(buildPath)); // -> the gulp.dest(..) command causes the error
});

package.json devDependencies(只有gulp和ts相关的依赖项)如下所示:

{
  "devDependencies": {
    "gulp": "github:gulpjs/gulp#4.0",
    "gulp-sourcemaps": "^2.6.1",
    "gulp-tslint": "^8.1.2",
    "gulp-typescript": "^3.2.3",
    "tslint": "^5.8.0",
    "typescript": "^2.5.0",
  }
}

节点版本:8.9.3和npm版本:5.6.0

任何人都知道该怎么做?

回答如下:

从gulp repo(issue):

phated在5小时前评论过

您的插件需要更新才能使用更新的乙烯基。他们用来创建文件对象的那个真的很旧。

来自同一问题的另一个解决方案(它适用于我):

dozer75 4小时前评论过•编辑过

...您可以在#之后引用先前的提交ID而不是分支名称。最后一个是6d71a65

与本文相关的文章

发布评论

评论列表(0)

  1. 暂无评论