how to solve this problem.
I run this commands make node-sdk on hyperledger/fabric folder (with sudo or without), still i am getting the same errors.
npm WARM hfc#0.6.2 license should be a valid SPDX license expression log file
this is harmless, the hfc module should still work despite the warning. By the way, if you are still developing with Hyperledger Fabric, there's a v1.0 release now. Checkout the details at hyperledger-fabric.readthedocs.io/en/latest/
Related
I'm trying to install rpm-build, but it seems there is some problems with dependencies:
The package that's installed is coming from a repo which is no longer available (linuxcoe_update_errata), I don't know what happened to it but the URL is no longer accessible, and the package that it wants to install is coming from another repo called core (this repo works just fine)
Seems like rpm-build need a lower version for rpm, which apparently should be not a problem. I tried dowgrading the version but is not working, again more conflicts, I tried to remove that package, but maybe because the repo that installed it is no longer available it does not uninstall anything.
How can I fix this? I need to install rpm-build in this machine, can't do it on another, but is not letting me. I think the problem has to be related to the repo which the package came from not being available anymore (linuxcoe_update_errata). I tried enabling notify_only=1 in /etc/yum/pluginconf.d/search-disabled-repos.conf so yum can try to resolve the error but itself, but still nothing. Any ideas? I'm really confused about this,
Problem Summary
So I'm trying to launch a new Gridsome project for local development. I've toyed with Gridsome in the past and had a great experience, so I decided to give it another shot.
This time around; however, when I run the gridsome create command, the system creates a new Gridsome site directory as expected but returns the following error message:
The instructions in this error message say to enter the newly-created site directory and run gridsome develop to start local development. However, after running cd my-gridsome-site and subsequently running gridsome develop, I then receive this error:
So far, I've tried running npm install --save from the site directory as well as yarn install, both to no avail. Thinking that this was possibly tied to my terminal, I switched from using the Zsh terminal to using the Bash terminal. This also did not work.
I'm at a loss here and could really use a hand.
Thank you for helping,
David
This seems to be an environment error. Gridsome requires Node.js (v8.3+) and recommends Yarn.
Make sure your Node.js version is v8.3+ and use only one package manager like Yarn.
to check node version: node -v
I had this same issue, but I resolved it after installing yarn and running the project with yarn instead of NPM. So you should try using yarn it will help,
I have cloned a GitHub repo and ran npm install as usual (I have it installed globally)
For some reason when I run start, the terminal gets stuck in build, though it did build with parcel (dist folders are created), also I can see the live server page. I can code, I can update.
The problem is that the terminal is stuck on the error message below and I have to start a new terminal every time.
error message on terminal
Building...(node:14216) ExperimentalWarning: Package name self resolution is an experimental feature. This feature could change at any time
/ Building CSSPlugin.js...(node:8680) ExperimentalWarning: Package name self resolution is an experimental feature. This feature
could change at any time
- Building bundle-url.js...(node:14220) ExperimentalWarning: Package name self resolution is an experimental feature. This feature could change at any time
Any idea why I am getting this and how to get rid of it?
Obs.: I have attempted to delete the folder and clone again, the same issue when running npm start for the first time.
Had the same behaviour on Node.js v13.9.0.
After updating Node.js to latest stable version, the warning message is gone and everything works fine.
I have an app created with Vue-Cli and it uses node-sass. Recently, I ran npm audit and is informing me there is a new advisory for node-sass with the following info:
All versions of node-sass are vulnerable to Denial of Service (DoS).
No fix is currently available. Consider using an alternative package
until a fix is made available.
Thus, I can't deploy my app to the company's enterprise cloud (DevOps pipeline).
Does anyone know how I can fix or replace node-sass with dart-sass and whether there are any specific updates or changes I need to do with my app?
Kinda shooting in the dark here...not much out there at the moment. Thanks.
This worked for me, follow the link below
https://www.priestch.com/replace-node-sass-with-dart-sass-in-vue-cli3-based-project/
Thanks
I use a vscode and our company is unable to connect to the internet due to security concerns. However, I want to use the jshint extension.
So, I made the jshint extension to .vsix, moved it to my company computer and installed it and it says npm install jshint.
As far as I know, npm is only available on Internet. So I looked again and found that there was npmbox.
https://serverfault.com/questions/559032/offline-install-of-npm-package
I created jshint.npmbox and istalled it as npmunbox.
This time I got getaddrinfo ENOTFOUND error.
Can not jshint be installed in an offline environment? Is there no way?
Better use,
Javascript Lint
which is available for offline usage. Hope, it is exactly providing similar support as jshint.
If you still want only jshint , then you may try forking jshint from github and try using it.