I get the following errors trying to install blueprintjs. What to do? I've installed react-addons-css-transition-group.
warning " > #blueprintjs/core#1.35.3" has unmet peer dependency "react-addons-css-transition-group#^15.0.1 || ^0.14".
warning "#blueprintjs/core > pure-render-decorator#1.2.1" has incorrect peer dependency "react#^15.0.0 || ^0.14.0".
If you're using yarn, it seems these warnings never go away, despite having correctly installed the dependencies. So if your app works then go ahead and ignore these warnings.
Related
Since I installed Ventura I've been having an impossible time with Yarn. This command works on a normal linux environment but will not work on either of my Ventura machines. I've tested this on all environments using the same version of yarn (i.e. 1.22.19) and of nodejs (i.e. 12.22.12).
% yarn add -D #quasar/quasar-app-extension-testing-unit-jest
yarn add v1.22.19
[1/5] Validating package.json...
[2/5] Resolving packages...
warning #quasar/quasar-app-extension-testing-unit-jest > babel-jest > #jest/transform > jest-haste-map > sane#4.1.0: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
warning #quasar/quasar-app-extension-testing-unit-jest > vue-jest > babel-plugin-transform-es2015-modules-commonjs > babel-runtime > core-js#2.6.12: core-js#<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
warning #quasar/quasar-app-extension-testing-unit-jest > jest > jest-cli > jest-config > jest-environment-jsdom > jsdom > w3c-hr-time#1.0.2: Use your platform's native performance.now() and performance.timeOrigin.
[3/5] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/typescript/-/typescript-4.2.2.tgz: incorrect data check".
info If you think this is a bug, please open a bug report with the information provided in "/Users/noeldacosta/repo/gitlab/netbuilder/cpd/cpd-portal/client/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
Following the guide here to install and use all needed utilities to use SELinux - https://wiki.archlinux.org/index.php/SELinux#Installing_SELinux and using the git repo, I get the following error:
warning: cannot resolve "python2-audit", a dependency of "selinux-python2"
:: The following package cannot be upgraded due to unresolvable dependencies:
selinux-python2
:: Do you want to skip the above package for this upgrade? [y/N]
error: failed to prepare transaction (could not satisfy dependencies)
:: unable to satisfy dependency 'python2-audit' required by selinux-python2
Error: the following command failed, sudo LANG=C pacman --noconfirm --ask=4 -U ./selinux-python/selinux-python2-2.9-1-x86_64.pkg.tar.xz ./selinux-python/selinux-python-2.9-1-x86_64.pkg.tar.xz
while running ./build_and_install_all.sh
I have the core repo enabled, and have tried refreshing the db repeatedly
Why is it saying that python2-audit is not available, when the wiki says it is available in the core repo?
And unless I can somehow get it installed, can I and how do I bypass that requirement?
I tried the steps for quick setup of firefox debugger at http://firefox-dev.tools/debugger/#quick-setup a few times but had the same problem.
I have pasted all my commands and warning (including error) messages in a gist at the bottom.
I suspect two things may cause the failure of the setting up.
when running curl -o- -L https://yarnpkg.com/install.sh | bash -s, I got warning message saying it is advised to not mix npm with yarn. However, I have not yet found out a way to separate them.
when running yarn, I got a lot of warning message saying the versions of packages are not matching, a lot of error messages for failing to run commands which I suspect to be the result of unmet packages but I can be wrong about it.
or what do you think the problem is?
could you give me some guidance on how to resolve this setting up problem? Thanks
please see the warning and error messages here in the gist.
https://gist.github.com/EmbraceLife/f84993112c5b4a894c30b0a4ba4bb4fc
it is advised to not mix npm with yarn
...in a single project. If you follow the instructions of cloning a clean repository and running yarn install inside, you should be fine.
I got a lot of warning message saying the versions of packages are not matching
I get these too, so I don't think anything is wrong on your end.
warning " > react-redux#5.0.7" has unmet peer dependency "redux#^2.0.0 || ^3.0.0 || ^4.0.0-0".
warning "devtools-launchpad > svg-inline-react#3.0.0" has incorrect peer dependency "react#^0.14.0 || ^15.0.0".
warning "devtools-launchpad > url-loader#0.5.9" has unmet peer dependency "file-loader#*".
warning " > eslint-plugin-mozilla#1.2.1" has unmet peer dependency "eslint-plugin-no-unsanitized#^3.0.0".
warning "devtools-reps > devtools-components > #storybook/react#3.4.8" has unmet peer dependency "babel-core#^6.26.0 || ^7.0.0-0".
warning "devtools-reps > devtools-components > #storybook/react#3.4.8" has unmet peer dependency "babel-runtime#>=6.0.0".
warning " > babel-jest#23.6.0" has unmet peer dependency "babel-core#^6.0.0 || ^7.0.0-0".
node-pre-gyp WARN Pre-built binaries not found for fsevents#1.2.4 and node#12.9.1 (node-v72 ABI, unknown) (falling back to source compile with node-gyp)
followed by a large number of build errors, ending with:
30 warnings and 14 errors generated.
make: *** [Release/obj.target/fse/fsevents.o] Error 1
gyp ERR! build error
...looks like a problem with your running node12 (the CI seems to be running with node10) but I'm not even sure lack of fsevents is fatal...
Listening for WS on localhost:8116, all traffic is proxied to localhost:6080
TCP connection failed: Error: connect ECONNREFUSED 127.0.0.1:6080
These messages in your output are expected - you're supposed to run a controlled instance of the browser that listens on port 6080, until you do the "launcher" page tries to connect and fails repeatedly.
Apart from the console messages, is there a problem or does the debugger work?
Installing Angluar CLI on MacOS (Sierra, 10.12.4), during which having the following dependency issue.
└─┬ angular-cli#1.0.0-beta.28.3
└── UNMET PEER DEPENDENCY rxjs#^5.0.1
node -v : v7.10.0
npm -v : 4.2.0
Tried removing rxjs completely and let it installed as a part of the dependency tree of the CLI, still gives the same error. Any ideas folks?
Cheer,
D
There is an issue with npm, you can check it out here:
https://github.com/npm/npm/issues/1341#issuecomment-20634338
You can fix your issue by manually installing rxjs#^5.0.1 globally with
npm install -g rxjs#^5.0.1
Hope this resolves your issue.
Trying to get a play 2.0.2 application going on heroku and it seems it is not yet supported.
Has anyone had any luck with this?
Error:
http://s3pository.heroku.com/maven-scala-tools-snapshots/org/scala-tools/sbt/sbt_2.9.1/0.11.3/sbt_2.9.1-0.11.3.pom
-- artifact org.scala-tools.sbt#sbt_2.9.1;0.11.3!sbt_2.9.1.jar:
http://s3pository.heroku.com/maven-scala-tools-snapshots/org/scala-tools/sbt/sbt_2.9.1/0.11.3/sbt_2.9.1-0.11.3.jar
::::::::::::::::::::::::::::::::::::::::::::::
:: UNRESOLVED DEPENDENCIES ::
::::::::::::::::::::::::::::::::::::::::::::::
:: org.scala-tools.sbt#sbt_2.9.1;0.11.3: not found
::::::::::::::::::::::::::::::::::::::::::::::
:: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
unresolved dependency: org.scala-tools.sbt#sbt_2.9.1;0.11.3: not found
Error during sbt execution: Error retrieving required libraries
(see /tmp/build_7sg3kay36u6a/project/boot/update.log for complete log)
Error: Could not retrieve sbt 0.11.3
! Failed to build app with SBT 0.11.0
! Heroku push rejected, failed to compile Scala app
This was happening because of old cache (my app had been deployed on heroku before, hence the old cache)
From the root of your play application, do
heroku config:add BUILDPACK_URL='https://github.com/heroku/heroku-buildpack-scala#cleancache'
then push your app again
This will drop all cached artifacts and the sbt jar and re-download up to date fresh ones.
Just remember to do heroku config:remove BUILDPACK_URL afterwards or each time you push the cache will be dropped and builds will take a while.
Kudos to scott # play googlegroups
https://groups.google.com/forum/#!topic/play-framework/yUDfW2UtBjs
This could be unrelated, but I had some conflicting plugin in myhomedir/.sbt/plugins/build.sbt that messed up my Play 2.0.2 build. Removing that fixed it for me.
I had this exact error on my Mac and it was because MacPorts did not install the correct version of SBT (sudo port install sbt gave me 0.11.2 not 0.11.3) - yes I updated my port tree. So I sudo port uninstalled sbt and used brew install sbt. This (Homebrew) installed 0.11.3 and the problem disappeared. I would suggest checking the sbt version on Heroku.
If you encounter this on play 2.0.4 (I know, this question is for play 2.0.2, but it's first on google):
change the sbt version to 0.11.3:
Change sbt version in project/build.properties to 0.11.3