2017-09-27 117 views
1

雖然在下面的錯誤產生使用離子CLI一個管道文件通過生成離子管誤差

ionic g pipe example 

結果:

Error: ENOENT: no such file or directory, open '<PROJECT_PATH>/src/PIPES/example.module.ts' 
    at Object.fs.openSync (fs.js:652:18) 
    at Object.fs.writeFileSync (fs.js:1299:33) 
    at createCommonModule (/home/future/Projects/SmartUpCode/smartupcrm-mobile/node_modules/@ionic/app-scripts/dist/generators/util.js:77:10) 
    at Object.<anonymous> (<PROJECT_PATH>/node_modules/@ionic/app-scripts/dist/generators/util.js:238:29) 
    at step (<PROJECT_PATH>e/node_modules/@ionic/app-scripts/dist/generators/util.js:32:23) 
    at Object.next (<PROJECT_PATH>/node_modules/@ionic/app-scripts/dist/generators/util.js:13:53) 
    at fulfilled (<PROJECT_PATH>/node_modules/@ionic/app-scripts/dist/generators/util.js:4:58) 
    at <anonymous> 

回答

1

這種「Error: ENOENT: no such file or directory,」的錯誤而產生的管道的發生是因爲使用錯誤的使用目錄路徑在本機ionic config.js文件中。

node_modules > @ionic > app-scripts > dist > util > config.js file

的問題可以通過在如下給出生成example.module.ts文件路徑改變大寫「PIPES」名稱以小寫的「管」來解決;

context.pipesNgModulePath = path_1.resolve(getConfigValue(context, '--pipesNgModulePath', null, Constants.ENV_PIPES_NG_MODULE_PATH, Constants.ENV_PIPES_NG_MODULE_PATH.toLowerCase(), path_1.join(context.srcDir, 'PIPES', 'pipes.module.ts'))); 

(context.srcDir, 'pipes', 'pipes.module.ts')

然後它工作得很好...