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 }}
Repository navigation
ng fails on Version.assertPostWebpackVersion() on 1.0.0-beta.14 #2135
OS?
Arch Linux with latest kernel and Node 6.5.0 through NVM
Versions:
angular-cli: 1.0.0-beta.14
node: 6.5.0
os: linux x64
Repro steps.
Local installation, empty folder:
npm i angular-cli
./node_modules/.bin/ng init # fails
The log given by the failure.
fs.js:640
return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
^
TypeError: path must be a string or Buffer
at TypeError (native)
at Object.fs.openSync (fs.js:640:18)
at Object.fs.readFileSync (fs.js:508:33)
at Function.Version.fromProject (/sec/Dev/Link/scripts/web_files_py/flask_ged/ng/node_modules/angular-cli/upgrade/version.js:87:31)
at Function.Version.isPreWebpack (/sec/Dev/Link/scripts/web_files_py/flask_ged/ng/node_modules/angular-cli/upgrade/version.js:111:31)
at Function.Version.assertPostWebpackVersion (/sec/Dev/Link/scripts/web_files_py/flask_ged/ng/node_modules/angular-cli/upgrade/version.js:97:18)
at /sec/Dev/Link/scripts/web_files_py/flask_ged/ng/node_modules/angular-cli/bin/ng:25:15
at /sec/Dev/Link/scripts/web_files_py/flask_ged/ng/node_modules/resolve/lib/async.js:44:21
at ondir (/sec/Dev/Link/scripts/web_files_py/flask_ged/ng/node_modules/resolve/lib/async.js:187:31)
at /sec/Dev/Link/scripts/web_files_py/flask_ged/ng/node_modules/resolve/lib/async.js:153:3
Mention any other details that might be useful.
Commenting out the line 25 on angular-cli/bin/ng makes everything work again.
This with the check Version.assertPostWebpackVersion(), was added on commit 21003b1 .
Installed latest version (*-beta.14)
tried ng --help
same error:
ng --help
fs.js:640
return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
^
TypeError: path must be a string or Buffer
at TypeError (native)
at Object.fs.openSync (fs.js:640:18)
at Object.fs.readFileSync (fs.js:508:33)
at Function.Version.fromProject (/usr/local/lib/node_modules/angular-cli/upgrade/version.js:87:31)
at Function.Version.isPreWebpack (/usr/local/lib/node_modules/angular-cli/upgrade/version.js:111:31)
at Function.Version.assertPostWebpackVersion (/usr/local/lib/node_modules/angular-cli/upgrade/version.js:97:18)
at /usr/local/lib/node_modules/angular-cli/bin/ng:25:15
at /usr/local/lib/node_modules/angular-cli/node_modules/resolve/lib/async.js:44:21
at ondir (/usr/local/lib/node_modules/angular-cli/node_modules/resolve/lib/async.js:187:31)
at /usr/local/lib/node_modules/angular-cli/node_modules/resolve/lib/async.js:153:39
@Aorewen Simplest workaround to continue working in your project is comment line 25 of node_modules/angular-cli/bin/ng :
// Version.assertPostWebpackVersion();
Until it is fixed properly.
Reacted by Owen Bodley, Bradley Jackson, VAD OST and Felix Griewald
Reacted by Jesse Nayak, Kevin Coleman and Kirtan Gajjar
I just commented out line 25 on angular-cli/bin/ng .
but now ng hangs if I call ng --help
a new line is displayed and I can enter any text but n nothing happens.
I quit the call with ^C.
I do not know if this has to do anything with this nam error message I got after installing angular-cli:
peer dep missing: webpack@1.x.x || 2.x.x, required by string-replace-loader@1.0.3
In the meanwhile I installed web pack:
npm ls webpack -g
/usr/local/lib
└── webpack@1.13.2
But I still get this error:
npm ls angular-cli
angular-cli@1.0.0-beta.14 /usr/local/lib/node_modules/angular-cli
└── UNMET PEER DEPENDENCY webpack@2.1.0-beta.22
Installed web pack@2.1.0-beta.22 but now I get the "old" message:
npm ls angular-cli
....
npm ERR! peer dep missing: webpack@1.x.x || 2.x.x, required by string-replace-loader@1.0.3
➜ angular nvm exec 6.6.0 ng
Running node v6.6.0 (npm v3.10.7)
fs.js:640
return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
^
TypeError: path must be a string or Buffer
at TypeError (native)
at Object.fs.openSync (fs.js:640:18)
at Object.fs.readFileSync (fs.js:508:33)
at Function.Version.fromProject (/home/jelf/.nvm/versions/node/v6.6.0/lib/node_modules/angular-cli/upgrade/version.js:87:31)
at Function.Version.isPreWebpack (/home/jelf/.nvm/versions/node/v6.6.0/lib/node_modules/angular-cli/upgrade/version.js:111:31)
at Function.Version.assertPostWebpackVersion (/home/jelf/.nvm/versions/node/v6.6.0/lib/node_modules/angular-cli/upgrade/version.js:97:18)
at /home/jelf/.nvm/versions/node/v6.6.0/lib/node_modules/angular-cli/bin/ng:25:15
at /home/jelf/.nvm/versions/node/v6.6.0/lib/node_modules/angular-cli/node_modules/resolve/lib/async.js:44:21
at ondir (/home/jelf/.nvm/versions/node/v6.6.0/lib/node_modules/angular-cli/node_modules/resolve/lib/async.js:187:31)
at /home/jelf/.nvm/versions/node/v6.6.0/lib/node_modules/angular-cli/node_modules/resolve/lib/async.js:153:39
Same issue for me on node 6.6.0, windows 10, I just get the upgrade warning and I'm asking for the latest version of angular-cli, I've done about 5 re-install cycles now.
I'm on a linux machine and this happens in one directory but not in another. Weird.
Edit: The directory that worked was an existing project. The one that didn't work was an empty project (ng init hadn't been ran). I didn't some investigation and it's looking for the angular-cli.json file. That file doesn't exist until you run "ng init". This seems like a bug. It's impossible to create new projects.
I'm not sure how this would ever work for new projects. The ng bin script checks looks for an angular-cli.json first thing and blows up when it doesn't find it.
That line should either check if the file exists or be moved into the try block below (line 82). It's trying to read in angular-cli.json. I'm not sure that's the best fix, but I changed it locally and it works.
I can confirm that this is happening on Mac when trying to bump from .15 to .16
Visit http://ember-cli.com/user-guide/#watchman for more info.
angular-cli: 1.0.0-beta.16
node: 6.3.1
os: darwin x64
Failing with this error.
Path must be a string. Received null
TypeError: Path must be a string. Received null
at assertPath (path.js:7:11)
at Object.resolve (path.js:1148:7)
at Class.exports.default.Task.extend.run (/Users/zchapple/code/wfa_ng2/node_modules/angular-cli/tasks/build-webpack-watch.js:14:26)
at Class.Command.extend.run (/Users/zchapple/code/wfa_ng2/node_modules/angular-cli/commands/build.js:50:26)
at Class.<anonymous> (/Users/zchapple/code/wfa_ng2/node_modules/angular-cli/lib/models/command.js:152:17)
at tryCatch (/Users/zchapple/code/wfa_ng2/node_modules/rsvp/dist/lib/rsvp/-internal.js:215:12)
at invokeCallback (/Users/zchapple/code/wfa_ng2/node_modules/rsvp/dist/lib/rsvp/-internal.js:230:13)
at publish (/Users/zchapple/code/wfa_ng2/node_modules/rsvp/dist/lib/rsvp/-internal.js:198:7)
at flush (/Users/zchapple/code/wfa_ng2/node_modules/rsvp/dist/lib/rsvp/asap.js:82:5)
at _combinedTickCallback (internal/process/next_tick.js:67:7)
at process._tickCallback (internal/process/next_tick.js:98:9)
Not sure if this is the same issue, but I'm getting this error:
Path must be a string. Received { source: 'environments/environment.ts',
dev: 'environments/environment.ts',
prod: 'environments/environment.prod.ts' }
Activity
BenoitFroment commentedon Sep 15, 2016
Same with both Windows 7 and Windows 8.1
node version : 6.5
npm version : 3.10.3
Steps :
npm install -g angular-cli@latest
go in work directory
npm install angular-cli@latest
ng new
sterlingfs commentedon Sep 15, 2016
same on macOS
alexverdaguer commentedon Sep 15, 2016
same here on Mac OS sierra with node 6.5.0
iuliust commentedon Sep 16, 2016
same on Linux Mint with node 6.5
Mattee commentedon Sep 16, 2016
Same here on Mac OSX Yosemite and Windows 10 with node 6.5.0.
BenoitFroment commentedon Sep 16, 2016
any news or trick about this?
hopefullToo commentedon Sep 16, 2016
Same on OS X El Capitan
node v6.6.0
npm 3.10.7
Installed latest version (*-beta.14)
tried ng --help
same error:
ng --help
fs.js:640
return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
^
TypeError: path must be a string or Buffer
at TypeError (native)
at Object.fs.openSync (fs.js:640:18)
at Object.fs.readFileSync (fs.js:508:33)
at Function.Version.fromProject (/usr/local/lib/node_modules/angular-cli/upgrade/version.js:87:31)
at Function.Version.isPreWebpack (/usr/local/lib/node_modules/angular-cli/upgrade/version.js:111:31)
at Function.Version.assertPostWebpackVersion (/usr/local/lib/node_modules/angular-cli/upgrade/version.js:97:18)
at /usr/local/lib/node_modules/angular-cli/bin/ng:25:15
at /usr/local/lib/node_modules/angular-cli/node_modules/resolve/lib/async.js:44:21
at ondir (/usr/local/lib/node_modules/angular-cli/node_modules/resolve/lib/async.js:187:31)
at /usr/local/lib/node_modules/angular-cli/node_modules/resolve/lib/async.js:153:39
andrevmatos commentedon Sep 16, 2016
@Aorewen Simplest workaround to continue working in your project is comment line 25 of node_modules/angular-cli/bin/ng :
// Version.assertPostWebpackVersion();
Until it is fixed properly.
hopefullToo commentedon Sep 16, 2016
I just commented out line 25 on angular-cli/bin/ng .
but now ng hangs if I call ng --help
a new line is displayed and I can enter any text but n nothing happens.
I quit the call with ^C.
I do not know if this has to do anything with this nam error message I got after installing angular-cli:
peer dep missing: webpack@1.x.x || 2.x.x, required by string-replace-loader@1.0.3
In the meanwhile I installed web pack:
npm ls webpack -g
/usr/local/lib
└── webpack@1.13.2
But I still get this error:
npm ls angular-cli
angular-cli@1.0.0-beta.14 /usr/local/lib/node_modules/angular-cli
└── UNMET PEER DEPENDENCY webpack@2.1.0-beta.22
Installed web pack@2.1.0-beta.22 but now I get the "old" message:
npm ls angular-cli
....
npm ERR! peer dep missing: webpack@1.x.x || 2.x.x, required by string-replace-loader@1.0.3
alexverdaguer commentedon Sep 16, 2016
Updated node to v6.6.0 and now it works !
ValeryVS commentedon Sep 16, 2016
I fix this for node 6.5.0 with #2178
JelF commentedon Sep 20, 2016
Persisted in v6.6.0 for me
OS gentoo linux, angular-cli@1.0.0-beta.15
mikedsharp commentedon Sep 20, 2016
Same issue for me on node 6.6.0, windows 10, I just get the upgrade warning and I'm asking for the latest version of angular-cli, I've done about 5 re-install cycles now.
caseyhoward commentedon Sep 21, 2016
I'm on a linux machine and this happens in one directory but not in another. Weird.
Edit: The directory that worked was an existing project. The one that didn't work was an empty project (ng init hadn't been ran). I didn't some investigation and it's looking for the angular-cli.json file. That file doesn't exist until you run "ng init". This seems like a bug. It's impossible to create new projects.
I'm not sure how this would ever work for new projects. The ng bin script checks looks for an angular-cli.json first thing and blows up when it doesn't find it.
caseyhoward commentedon Sep 21, 2016
Upon further review, I think I see the error:
https://github.com/angular/angular-cli/blob/master/packages/angular-cli/upgrade/version.ts#L79
That line should either check if the file exists or be moved into the try block below (line 82). It's trying to read in angular-cli.json. I'm not sure that's the best fix, but I changed it locally and it works.
16 remaining items
zackarychapple commentedon Oct 3, 2016
I can confirm that this is happening on Mac when trying to bump from .15 to .16
Failing with this error.
fix: check for old version of the CLI on empty project
fix: check for old version of the CLI on empty project
fix: check for old version of the CLI on empty project
fix: check for old version of the CLI on empty project
datrinh commentedon Jan 13, 2017
Not sure if this is the same issue, but I'm getting this error:
Newly installed ng-cli with these version:
Barely did any coding. Added 4 components and one service, also angular/material and now this error is thrown when I run
ng serveangular-automatic-lock-bot commentedon Sep 6, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.
fix: check for old version of the CLI on empty project