I am trying to deploy a project to scrapinghub and here's the error I am getting
slackclient 1.3.2 has requirement websocket-client<0.55.0,>=0.35, but you have websocket-client 0.57.0.
Warning: Pip checks failed, please fix the conflicts.
WARNING: There're some errors when doing pip-check:
WARNING: The scripts pip, pip3 and pip3.8 are installed in '/app/python/bin' which is not on PATH.
Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
{"message": "Dependencies check exit code: 1", "details": "Pip checks failed, please fix the conflicts", "error": "requirements_error"}
{"status": "error", "message": "Requirements error"}
Deploy log location: /var/folders/p7/nwmq6_4138n6t3w2spdnpzfm0000gn/T/shub_deploy_5l9k3_nm.log
Error: Deploy failed: b'{"status": "error", "message": "Requirements error"}'
I can't figure out how to find the log file its saying?
I had this issue recently and the cause was that the stack I was using on the dash required specific, older versions of packages that were dependencies of ones in my requirements.
A good first step is to try installing the older version of websocket-client. If slackclient 1.3.2 works on the older version you;re good, otherwise you might need to try rolling back slackclient too.
Related
I've never been really familiar with the npx command but from my understanding it's just a way of executing NPM packages, which is required in the Getting started guide from Remix.run web framework.
It's really frustrating to just get stuck on the first step when I simply have to execute the npx create-remix#latest command. I get the following error:
Error: EEXIST: file already exists, mkdir 'C:\Users\Ruben'
command not found: create-remix
Not sure what happens underlying but I don't know why it's trying to create a folder in the C drive when I execute this on D:\Github\new-project
NPM/NPX version: 6.14.6
This seems to be a problem with your node/npm configuration rather then remix.run.
.npmrc file at C:\Users\Ruben
Do you have a .npmrc file? Maybe try and delete it as this answer details.
If you Google for "npx eexist file already exists", you will find several threads with the same issue and it seems to be a node/npm installation/configuration issue: 1, 2
I am trying to install the following package through yarn yarn add react-native-gesture-handler#1.10.2. I read multiple answers to this question yet none was of use. I think the problem might come from the fact I am on a windows computer yet don't know how to solve it.
Whenenever y try to do a yarn add ..#version I get the following error:
yarn add v1.22.11
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is
advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "C:\\Users\\...\\AppData\\Local\\Yarn\\Cache\\v6\\npm-unbox-primitive-1.0.1-085e215625ec3162574dc8859abee78a59b14471-integrity\\node_modules\\unbox-primitive\\.yarn-metadata.json:
Unexpected token \u0000 in JSON at position 0".
info If you think this is a bug, please open a bug report with the information provided in "C:\\Users\\...\\OneDrive\\Documents\\GitHub\\wc_app\\yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
I have same problem with installing next.js app many times
now its fixed
with clear cache of yarn
yarn cache clean
I have faced a similar problem while creating a latest react native project(0.65) in my Windows machine:
error An unexpected error occurred: "C:\Users\arefin\AppData\Local\Yarn\Cache\v6\npm-is-ci-3.0.0-c7e7be3c9d8eef7d0fa144390bd1e4b88dc4c994-integrity\node_modules\is-ci\.yarn-metadata.json: Unexpected token \u0000 in JSON at position 0".
My system configuration for react native development is as follows:
node --version: v15.7.0
yarn --version: 1.22.5
npm --version: 7.12.1
java --version: java 15.0.2 2021-01-19
I used these commands below, which finally solved the problem in my case:
yarn init && yarn add react-native && yarn react-native init
SpendnGain
which I found at here
Deployments worked fine before I installed FontAwesome. Locally it works fine even with FontAwesome. But with FontAwesome dependency installed Cloudflare fails.
Console log from Cloudflare Pages:
23:32:59.378 Installing NPM modules using Yarn version 1.22.4
23:32:59.751 yarn install v1.22.4
23:32:59.851 [1/4] Resolving packages...
23:33:00.491 [2/4] Fetching packages...
23:33:00.802 error An unexpected error occurred: "https://npm.fontawesome.com/#fortawesome/free-solid-svg-icons/-/5.15.3/free-solid-svg-icons-5.15.3.tgz: Request failed \"401 Unauthorized\"".
23:33:00.802 info If you think this is a bug, please open a bug report with the information provided in "/opt/buildhome/repo/yarn-error.log".
23:33:00.802 info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
23:33:23.195 Error during Yarn install
23:33:23.195 Failed: build command exited with code: 1
I just had this issue when trying build a Strapi app on DigitalOcean. I was able to fix it using this guide from the FontAwesome website.
Unfortunately, this workaround requires a valid auth token. Luckily for me, I was already an FA Pro subscriber.
Create an .npmrc file in the root of your project and add the below code, replacing "TOKEN" with your auth token. The auth token can be found on the guide linked above once logged into the FA website.
#fortawesome:registry=https://npm.fontawesome.com/
//npm.fontawesome.com/:_authToken=TOKEN
I'm not well versed enough in npm authentication to know why the free version would require this, but I'm sure there must be another workaround for free users of FA.
yesterday the VS Code informed me to update azure-functions-core-tools and after updating it, this error was displayed to me after I ran "func host start" :
Couldn't require bundle, falling back to Worker.js. Error: The gRPC binary module was not installed.This may be fixed by running "npm rebuild"
any idea on how to fix this?I tried npm rebuild and it does not worked.
This error often indicates that the grpc library was installed for a platform that is different from the one it is running on. The solution is to run npm install with extra arguments that describe the platform the library will run on. These options are described in the node-pre-gyp README.
For example, to install grpc for use on Node 10.0.0 on a 64-bit Linux that is not Alpine Linux, you can use the following command:
npm install --target=10.0.0 --target_arch=x64 --target_platform=linux --target_libc=glibc
Note: the target_libc option should be omitted for platforms other than Linux.
after 2 hours, installing x86 version of azure-functions-core-tools resolved the error. but this may not be the best solution.
Currently I am using the below commands for start the server (using Mocha framework) during second command am getting an error message. Please find the below and share your input
1. npm install selenium-standalone#latest -g
2. selenium-standalone install
3. selenium-standalone start
Error Log: During "selenium-standalone install"
firefox install:
from:
https://github.com/mozilla/geckodriver/releases/download/v0.13.0/geckodriv
er-v0.13.0-win64.zip to:
C:\Users\xxuser\AppData\Roaming\npm\node_modules\selenium-standalone.selen
ium\geckodriver\0.13.0-x64-geckodriver
C:\Users\xxuser\AppData\Roaming\npm\node_modules\selenium-standalone\bin\seleni
um-standalone:105
throw err;
^ Error: Could not download https://selenium-release.storage.googleapis.com/3.0/IE
DriverServer_x64_3.0.1.zip
at Request. (C:\Users\xxuser\AppData\Roaming\npm\node_modules\se
lenium-standalone\lib\install.js:273:21)
It is either an issue with google not having the file in the right place or selenium-standalone having the wrong url. If you go to https://github.com/mozilla/geckodriver/releases/download/v0.13.0/geckodriver-v0.13.0-win64.zip
it will download a zip file.
if you go to https://selenium-release.storage.googleapis.com/3.0/IE%20DriverServer_x64_3.0.1.zip
you get:
NoSuchKeyThe specified key does not exist.
The issue isn't firefox (gecko) driver it is internet explorer's driver.