Until I started the new polymer-cli my projects done in Polymer 1 was running as expected. Now, when I tried to start them via gulp serve I get error.
I tried updated by "bower update" and I got
bower polymer#1.11.3 ENOENT ENOENT: no such file or directory, lstat 'C:\Users\my-user\AppData\Local\Temp\tmp-28649quOp0xfcp3e\polymer-1.11.3'
Stack trace:
C:\Users\my-user\AppData\Roaming\npm\node_modules\bower\lib\node_modules\fstream\lib\dir-reader.js:96:25
C:\Users\my-user\AppData\Roaming\npm\node_modules\bower\lib\node_modules\graceful-fs\polyfills.js:284:29
FSReqWrap.oncomplete (fs.js:152:21)
Console trace:
Error
at StandardRenderer.error (C:\Users\my-user\AppData\Roaming\npm\node_modules\bower\lib\renderers\StandardRenderer.js:88:37)
at Logger.<anonymous> (C:\Users\my-user\AppData\Roaming\npm\node_modules\bower\lib\bin\bower.js:113:30)
at emitOne (events.js:116:13)
at Logger.emit (events.js:211:7)
at Logger.emit (C:\Users\my-user\AppData\Roaming\npm\node_modules\bower\lib\node_modules\bower-logger\lib\Logger.js:29:39)
at C:\Users\my-user\AppData\Roaming\npm\node_modules\bower\lib\commands\index.js:49:24
at _rejected (C:\Users\my-user\AppData\Roaming\npm\node_modules\bower\lib\node_modules\q\q.js:864:24)
at C:\Users\my-user\AppData\Roaming\npm\node_modules\bower\lib\node_modules\q\q.js:890:30
at Promise.when (C:\Users\my-user\AppData\Roaming\npm\node_modules\bower\lib\node_modules\q\q.js:1142:31)
at Promise.promise.promiseDispatch (C:\Users\my-user\AppData\Roaming\npm\node_modules\bower\lib\node_modules\q\q.js:808:41)
System info:
Bower version: 1.8.4
Node version: 8.11.1
OS: Windows_NT 6.1.7601 x64
Could that be related to the fact I installed "npm install -g polymer-cli#next"? What could I check around?
Related
PS D:\React Prep\E-com> npm start
ecom#0.1.0 start
react-scripts start
Failed to compile.
createSchemaValidation is not defined
error showing while npm start..
I'm trying to run "ng e2e" command with octopus with following configuration but getting below error all the time:
[07:20:37] E/launcher - session not created: This version of ChromeDriver only supports Chrome version 79
(Driver info: chromedriver=79.0.3945.16 (93fcc21110c10dbbd49bbff8f472335360e31d05-refs/branch-heads/3945#{#262}),platform=Windows NT 10.0.14393 x86_64)
[07:20:37] E/launcher - SessionNotCreatedError: session not created: This version of ChromeDriver only supports Chrome version 79
(Driver info: chromedriver=79.0.3945.16 (93fcc21110c10dbbd49bbff8f472335360e31d05-refs/branch-heads/3945#{#262}),platform=Windows NT 10.0.14393 x86_64)
at Object.checkLegacyResponse (D:\a\1\s\node_modules\selenium-webdriver\lib\error.js:546:15)
at parseHttpResponse (D:\a\1\s\node_modules\selenium-webdriver\lib\http.js:509:13)
at D:\a\1\s\node_modules\selenium-webdriver\lib\http.js:441:30
at processTicksAndRejections (internal/process/task_queues.js:93:5)
From: Task: WebDriver.createSession()
at Function.createSession (D:\a\1\s\node_modules\selenium-webdriver\lib\webdriver.js:769:24)
at Function.createSession (D:\a\1\s\node_modules\selenium-webdriver\chrome.js:761:15)
at Direct.getNewDriver (D:\a\1\s\node_modules\protractor\built\driverProviders\direct.js:77:33)
at Runner.createBrowser (D:\a\1\s\node_modules\protractor\built\runner.js:195:43)
at D:\a\1\s\node_modules\protractor\built\runner.js:339:29
at _fulfilled (D:\a\1\s\node_modules\protractor\node_modules\q\q.js:834:54)
at D:\a\1\s\node_modules\protractor\node_modules\q\q.js:863:30
at Promise.promise.promiseDispatch (D:\a\1\s\node_modules\protractor\node_modules\q\q.js:796:13)
at D:\a\1\s\node_modules\protractor\node_modules\q\q.js:556:49
at runSingle (D:\a\1\s\node_modules\protractor\node_modules\q\q.js:137:13)
[07:20:37] E/launcher - Process exited with error code 199
An unexpected error occurred: undefined
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! rebar-spa-v2-template#0.0.3 e2e: `ng e2e`
Configuration is:
user-agent = "npm/6.12.1 node/v12.13.1 win32 x64"
Protractor.conf.js:
capabilities: {
'browserName': 'chrome',
chromeOptions: {
args: ['--headless', '--disable-gpu', '--window-size=800,600']
}
},
Package.json: tried with both of solution
postinstall: webdriver-manager update --versions.chrome 79.0.3945.36
or
postinstall: cd ./node_modules/protractor && npm i webdriver-manager#latest
Any help will be appreciated.
This error message...
session not created: This version of ChromeDriver only supports Chrome version 79 (Driver info: chromedriver=79.0.3945.16 (93fcc21110c10dbbd49bbff8f472335360e31d05-refs/branch-heads/3945#{#262}),platform=Windows NT 10.0.14393 x86_64)
...implies that the ChromeDriver was unable to initiate/spawn a new Browsing Context i.e. Chrome Browser session.
Your main issue is the incompatibility between the version of the binaries you are using as follows:
You are using chromedriver=79.0.3945.16
Release Notes of chromedriver=79.0.3945.16 clearly mentions the following :
Supports Chrome v79
Presumably you are using a Chrome with a version other then chrome= 79.0
Possibly the following command fails:
webdriver-manager update --versions.chrome 79.0.3945.36
So there is a clear mismatch between the ChromeDriver v79.0 and your current Chrome Browser
Solution
Ensure the following mentioned steps will solve the issue:
You may need to clean up once:
webdriver-manager clean
You have the latest version of webdriver-manager and you can install the same using the command:
webdriver-manager#latest --save
Execute the following command will solve your issue:
webdriver-manager update
Upgrade Chrome to the latest stable release:
webdriver-manager update --versions.chrome 79.0.3945.88
I got this message when my system downloaded Chrome 90 in the background, even though my browser still said 89 (to be fair it was prompting me to update). I tried a few things but in the end I just ran npm uninstall chromedriver and then npm install chromedriver and everything started working again. Not ideal but I'm happy my tests are able to run.
EDIT:
I noticed that running the above commands updated my package.json file so it now said "chromedriver": "^90.0.0" in it. I'm guessing I could have made that version change myself and run npm install chromedriver to download the updated driver file. I'll try that next time.
The reason for me was that chromedriver was installed globally. Need just do npm i chromedriver -g
I am testing NetLify CMS for a project, but I am not able to work in my local environment, because gulp server crashs before it start, due to the error below:
$ npm start
> victor-hugo#1.0.0 start C:\Users\maufa\Documents\web-development\kaldi-hugo-cms-template
> gulp server
[14:17:07] Requiring external module babel-register
[14:17:08] Using gulpfile ~\Documents\web-development\kaldi-hugo-cms-template\gulpfile.babel.js
[14:17:08] Starting 'hugo'...
[14:17:08] Starting 'css'...
[14:17:09] Starting 'js'...
[14:17:09] Starting 'svg'...
[14:17:09] Starting 'cms'...
[14:17:09] Finished 'cms' after 150 ms
events.js:160
throw er; // Unhandled 'error' event
^
Error: spawn ./bin/hugo.win32 ENOENT
at exports._errnoException (util.js:1022:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
at onErrorNT (internal/child_process.js:359:16)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickCallback (internal/process/next_tick.js:98:9)
at Module.runMain (module.js:606:11)
at run (bootstrap_node.js:394:7)
at startup (bootstrap_node.js:149:9)
at bootstrap_node.js:509:3
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! victor-hugo#1.0.0 start: `gulp server`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the victor-hugo#1.0.0 start script 'gulp server'.
So, looks like it is trying to find hugo.win32 inside the bin folder.
However, inside this folder I ave:
hugo.darwin
hugo.exe
hugo.linux
Any clue?
It looks like this issue is particular to the Kaldi Hugo template. I installed on Windows and got the same error, then I tried renaming hugo.exe to hugo.win32, and it worked. I found the error in gulpfile.babel.js (incorrect string identifier for Windows), and submitted a PR. If you don't want to wait for the merge, feel free to change your version directly: https://github.com/netlify-templates/kaldi-hugo-cms-template/pull/3/files
I messed up my local project with Foundation 6 but I had everything on a remote web server so I downloaded my project to a local folder. When I tried to run foundation watch I got errors
sh: /myfolder/node_modules/.bin/gulp: Permission denied
Error: foundation-sites-template#1.0.0 start: `gulp`
Exit status 126
at EventEmitter.<anonymous> (/usr/local/lib/node_modules/foundation-cli/node_modules/npm/lib/utils/lifecycle.js:217:16)
at emitTwo (events.js:100:13)
at EventEmitter.emit (events.js:185:7)
at ChildProcess.<anonymous> (/usr/local/lib/node_modules/foundation-cli/node_modules/npm/lib/utils/spawn.js:24:14)
at emitTwo (events.js:100:13)
at ChildProcess.emit (events.js:185:7)
at maybeClose (internal/child_process.js:850:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)
Is that fixable?
Whatever means of copying you used probably messed up the executable bit of /myfolder/node_modules/.bin/gulp. Type the following in a terminal:
chmod a+x /myfolder/node_modules/.bin/gulp
There might be other files with permission issues, so it's probably best to just delete the the whole node_modules folder and npm install from scratch.
I am having a hard time figuring out what this error means.
I have the following bower.json:
...
"dependencies":{
"angular-route":"~1.2.18",
"angular":"~1.2.18"
}
Upon installing my bower packages through bower install I get the following error:
bower angular-route#~1.2.20 error Arguments to path.join must be strings
Stack trace:
TypeError: Arguments to path.join must be strings
at path.js:360:15
at Array.filter (native)
at Object.exports.join (path.js:358:36)
at GitHubResolver._checkout (/home/ubuntu/.nvm/v0.10.26/lib/node_modules/bower/lib/core/resolvers/GitHubResolver.js:54:21)
at /home/ubuntu/.nvm/v0.10.26/lib/node_modules/bower/lib/core/resolvers/GitResolver.js:69:21
at _fulfilled (/home/ubuntu/.nvm/v0.10.26/lib/node_modules/bower/node_modules/p-throttler/node_modules/q/q.js:798:54)
at self.promiseDispatch.done (/home/ubuntu/.nvm/v0.10.26/lib/node_modules/bower/node_modules/p-throttler/node_modules/q/q.js:827:30)
at Promise.promise.promiseDispatch (/home/ubuntu/.nvm/v0.10.26/lib/node_modules/bower/node_modules/p-throttler/node_modules/q/q.js:760:13)
at /home/ubuntu/.nvm/v0.10.26/lib/node_modules/bower/node_modules/p-throttler/node_modules/q/q.js:574:44
at flush (/home/ubuntu/.nvm/v0.10.26/lib/node_modules/bower/node_modules/p-throttler/node_modules/q/q.js:108:17)
Console trace:
Trace
at StandardRenderer.error (/home/ubuntu/.nvm/v0.10.26/lib/node_modules/bower/lib/renderers/StandardRenderer.js:72:17)
at Logger.<anonymous> (/home/ubuntu/.nvm/v0.10.26/lib/node_modules/bower/bin/bower:111:22)
at Logger.EventEmitter.emit (events.js:95:17)
at Logger.emit (/home/ubuntu/.nvm/v0.10.26/lib/node_modules/bower/node_modules/bower-logger/lib/Logger.js:29:39)
at /home/ubuntu/.nvm/v0.10.26/lib/node_modules/bower/lib/commands/index.js:40:20
at _rejected (/home/ubuntu/.nvm/v0.10.26/lib/node_modules/bower/node_modules/q/q.js:797:24)
at /home/ubuntu/.nvm/v0.10.26/lib/node_modules/bower/node_modules/q/q.js:823:30
at Promise.when (/home/ubuntu/.nvm/v0.10.26/lib/node_modules/bower/node_modules/q/q.js:1035:31)
at Promise.promise.promiseDispatch (/home/ubuntu/.nvm/v0.10.26/lib/node_modules/bower/node_modules/q/q.js:741:41)
at /home/ubuntu/.nvm/v0.10.26/lib/node_modules/bower/node_modules/q/q.js:557:44
System info:
Bower version: 1.3.7
Node version: 0.10.26
OS: Linux 3.13.0-29-generic x64
Now, I have to mention that I have done the same thing for about a week, and everything was working correctly, with exactly the same setup.
I have noticed that https://github.com/angular/angular.js has released a new version 1.2.20 recently, but even installing that I get the same error.
Some context: I am using nodejs, express and angular in my application. I can provide more info if needed (e.g., package.json, main server file).
Any help would be highly appreciated.
See the answer here: Bower - error when installing package "Arguments to path.join must be strings"
Fix: bower cache clean and update to Bower 1.3.8.