Can't install Truffle sweet via Powershell on Windows 10. Get mkdirp 5.x deprecated and no more mainetained - powershell

When I want to install the Truffle sweet with npm install -g Truffle I get warnings which say that the mkdirp is deprecated and the package is broken and not maintained anymore.
So I think it won't install the truffle sweet.
What should I do to get the broken package fixed?
I am totally new to Ethereum programming.
The PowerShell code:
mkdirp-promise#5.0.1: This package is broken and no longer maintained. 'mkdirp' itself supports promises now, please switch to that.
npm WARN deprecated request#2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator#5.1.5: this library is no longer supported
npm WARN deprecated multicodec#0.5.7: stable api reached

Related

SAPUI5 KARMA CI GitLab

I'm trying to set up a CI pipeline for a SAPUI5 application using the CI/CD in GitLab.
I've decided to go with the following tools:
UI5 Tooling
UIVeri5
Karma
So far the build with the UI5 Tooling was successful.
Most likely I have issues with the testing part.
Please have a look at the following files:
.gitlab-ci.yml:
image: geertjanklaps/node-cf-cli:latest
cache:
paths:
- node_modules/
stages:
- test
- build
ESLint:
stage: test
before_script:
- npm install
- npm install --global #ui5/uiveri5
- npm install -g karma-cli
- npm install --save-dev karma karma-ui5
- npm install --save-dev karma-chrome-launcher
script:
- karma start --singleRun=true
#Build MTA File:
stage: build
before_script:
- npm install --global #ui5/cli
script:
- ui5 build --all
only:
- master
karma.conf.js:
module.exports = function(config) {
config.set({
frameworks: [ "ui5" ],
ui5: {
mode: "script",
tests: [ "webapp/test/" ]
},
browsers: [ "MyHeadlessChrome" ],
singleRun: true,
customLaunchers: {
MyHeadlessChrome: {
base: 'ChromeHeadless',
flags: [
'--disable-translate',
'--disable-extensions',
'--remote-debugging-port=9223',
'--no-sandbox'
]
},
},
});
};
For deeper analyses, please look at my repo here.
Now to the problem
The job stops with the following info:
ReferenceError: sap is not defined
at node_modules/karma-ui5/lib/client/autorun.js:16:2
at node_modules/karma-ui5/lib/client/autorun.js:22:3
Please see full job log for more infos:
[0KRunning with gitlab-runner 13.5.0-rc2 (71c90c86)
[0;m[0K on docker-auto-scale fa6cab46
[0;msection_start:1603897730:resolve_secrets
[0K[0K[36;1mResolving secrets[0;m
[0;msection_end:1603897730:resolve_secrets
[0Ksection_start:1603897730:prepare_executor
[0K[0K[36;1mPreparing the "docker+machine" executor[0;m
[0;m[0KUsing Docker executor with image geertjanklaps/node-cf-cli:latest ...
[0;m[0KPulling docker image geertjanklaps/node-cf-cli:latest ...
[0;m[0KUsing docker image sha256:4d8a2c0623c41c1b33b2d9505d88a0712615ca0dc12b1deb05ea5f9ebfb43757 for geertjanklaps/node-cf-cli:latest with digest geertjanklaps/node-cf-cli#sha256:6bc976fbfae34d9d982b39331bfd842518e28da02cfacf76a2c83bab67ffb31b ...
[0;msection_end:1603897771:prepare_executor
[0Ksection_start:1603897771:prepare_script
[0K[0K[36;1mPreparing environment[0;m
[0;mRunning on runner-fa6cab46-project-22032692-concurrent-0 via runner-fa6cab46-srm-1603897681-955e55b1...
section_end:1603897774:prepare_script
[0Ksection_start:1603897774:get_sources
[0K[0K[36;1mGetting source from Git repository[0;m
[0;m[32;1m$ eval "$CI_PRE_CLONE_SCRIPT"[0;m
[32;1mFetching changes with git depth set to 50...[0;m
Initialized empty Git repository in /builds/MarvinsRoom/testproject-1/.git/
[32;1mCreated fresh repository.[0;m
[32;1mChecking out 2cde8a5a as master...[0;m
[32;1mSkipping Git submodules setup[0;m
section_end:1603897776:get_sources
[0Ksection_start:1603897776:restore_cache
[0K[0K[36;1mRestoring cache[0;m
[0;m[32;1mChecking cache for default...[0;m
Downloading cache.zip from https://storage.googleapis.com/gitlab-com-runners-cache/project/22032692/default[0;m
[32;1mSuccessfully extracted cache[0;m
section_end:1603897777:restore_cache
[0Ksection_start:1603897777:step_script
[0K[0K[36;1mExecuting "step_script" stage of the job script[0;m
[0;m[32;1m$ npm install[0;m
npm WARN deprecated http2#3.3.7: Use the built-in module in node 9.0.0 or newer, instead
npm WARN deprecated istanbul#0.4.5: This module is no longer maintained, try this instead:
npm WARN deprecated npm i nyc
npm WARN deprecated Visit https://istanbul.js.org/integrations for other alternatives.
npm WARN deprecated chokidar#1.7.0: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated core-js#2.6.11: core-js#<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js#3.
npm WARN deprecated fsevents#1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated circular-json#0.5.9: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated nodemailer#2.7.2: All versions below 4.0.1 of Nodemailer are deprecated. See https://nodemailer.com/status/
npm WARN deprecated samsam#1.3.0: This package has been deprecated in favour of #sinonjs/samsam
npm WARN deprecated uws#9.14.0: New code is available at github.com/uNetworking/uWebSockets.js
npm WARN deprecated request#2.75.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated mailcomposer#4.0.1: This project is unmaintained
npm WARN deprecated socks#1.1.9: If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introduced in 2.1.0
npm WARN deprecated har-validator#2.0.6: this library is no longer supported
npm WARN deprecated hawk#3.1.3: This module moved to #hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated node-uuid#1.4.8: Use uuid module instead
npm WARN deprecated buildmail#4.0.1: This project is unmaintained
npm WARN deprecated hoek#2.16.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated sntp#1.0.9: This module moved to #hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated boom#2.10.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated cryptiles#2.0.5: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
> uws#9.14.0 install /builds/MarvinsRoom/testproject-1/node_modules/uws
> node-gyp rebuild > build_log.txt 2>&1 || exit 0
> core-js#2.6.11 postinstall /builds/MarvinsRoom/testproject-1/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"
> sinon#4.4.8 postinstall /builds/MarvinsRoom/testproject-1/node_modules/sinon
> node scripts/support-sinon.js
Have some â¤ï¸ for Sinon? You can support the project via Open Collective:
> https://opencollective.com/sinon/donate
npm WARN notsup Unsupported engine for http2#3.3.7: wanted: {"node":">=0.12.0 <9.0.0"} (current: {"node":"12.16.1","npm":"6.14.1"})
npm WARN notsup Not compatible with your version of node/npm: http2#3.3.7
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
added 944 packages from 1379 contributors and audited 940 packages in 42.322s
2 packages are looking for funding
run `npm fund` for details
found 116 vulnerabilities (52 low, 20 moderate, 44 high)
run `npm audit fix` to fix them, or `npm audit` for details
[32;1m$ npm install --global #ui5/uiveri5[0;m
npm WARN deprecated request#2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated minimatch#2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated har-validator#5.1.5: this library is no longer supported
/usr/bin/uiveri5 -> /usr/lib/node_modules/#ui5/uiveri5/bin/uiveri5
+ #ui5/uiveri5#1.45.1
added 182 packages from 231 contributors in 9.259s
[32;1m$ npm install -g karma-cli[0;m
/usr/bin/karma -> /usr/lib/node_modules/karma-cli/bin/karma
+ karma-cli#2.0.0
added 6 packages from 21 contributors in 0.74s
[32;1m$ npm install --save-dev karma karma-ui5[0;m
npm WARN deprecated request#2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated chokidar#1.7.0: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated core-js#2.6.11: core-js#<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js#3.
npm WARN deprecated fsevents#1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated nodemailer#2.7.2: All versions below 4.0.1 of Nodemailer are deprecated. See https://nodemailer.com/status/
npm WARN deprecated circular-json#0.5.9: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated request#2.75.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator#2.0.6: this library is no longer supported
npm WARN deprecated hawk#3.1.3: This module moved to #hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated node-uuid#1.4.8: Use uuid module instead
npm WARN deprecated hoek#2.16.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated boom#2.10.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated sntp#1.0.9: This module moved to #hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated cryptiles#2.0.5: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated socks#1.1.9: If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introduced in 2.1.0
npm WARN deprecated mailcomposer#4.0.1: This project is unmaintained
npm WARN deprecated buildmail#4.0.1: This project is unmaintained
npm WARN deprecated uws#9.14.0: New code is available at github.com/uNetworking/uWebSockets.js
npm WARN rm not removing /builds/MarvinsRoom/testproject-1/node_modules/.bin/uuid as it wasn't installed by /builds/MarvinsRoom/testproject-1/node_modules/node-uuid
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#~2.1.2 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.0.0 (node_modules/#sap/grunt-sapui5-bestpractice-test/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
+ karma#5.2.3
+ karma-ui5#2.3.1
added 445 packages from 660 contributors, removed 14 packages, updated 38 packages, moved 27 packages and audited 1376 packages in 32.8s
32 packages are looking for funding
run `npm fund` for details
found 127 vulnerabilities (64 low, 20 moderate, 43 high)
run `npm audit fix` to fix them, or `npm audit` for details
[32;1m$ npm install --save-dev karma-chrome-launcher[0;m
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.13 (node_modules/#sap/grunt-sapui5-bestpractice-test/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#2.1.3 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
+ karma-chrome-launcher#3.1.0
added 2 packages from 29 contributors, updated 1 package and audited 1378 packages in 12.365s
34 packages are looking for funding
run `npm fund` for details
found 127 vulnerabilities (64 low, 20 moderate, 43 high)
run `npm audit fix` to fix them, or `npm audit` for details
[32;1m$ karma start --singleRun=true[0;m
[32m28 10 2020 15:11:21.695:INFO [karma-server]: [39mKarma v5.2.3 server started at http://localhost:9876/
[32m28 10 2020 15:11:21.698:INFO [launcher]: [39mLaunching browsers MyHeadlessChrome with concurrency unlimited
[32m28 10 2020 15:11:21.702:INFO [launcher]: [39mStarting browser ChromeHeadless
[32m28 10 2020 15:11:22.071:INFO [Chromium 80.0.3987.87 (Ubuntu 0.0.0)]: [39mConnected on socket PNW35HCgiwnOH-7cAAAA with id 80702627
[33m28 10 2020 15:11:22.137:WARN [web-server]: [39m404: /resources/sap-ui-core.js
[31mChromium 80.0.3987.87 (Ubuntu 0.0.0) ERROR[39m
Uncaught ReferenceError: sap is not defined
at node_modules/karma-ui5/lib/client/autorun.js:16:2
ReferenceError: sap is not defined
at node_modules/karma-ui5/lib/client/autorun.js:16:2
at node_modules/karma-ui5/lib/client/autorun.js:22:3
section_end:1603897883:step_script
[0Ksection_start:1603897883:cleanup_file_variables
[0K[0K[36;1mCleaning up file based variables[0;m
[0;msection_end:1603897885:cleanup_file_variables
[0K[31;1mERROR: Job failed: exit code 1
[0;m
Did you configure your karma-ci.conf.js according to https://github.com/SAP/karma-ui5?
It should look like:
module.exports = function(config) {
config.set({
frameworks: ["ui5", "qunit", "sinon"],
ui5: {
url: "https://openui5.hana.ondemand.com",
mode: "script",
config: {
async: true,
resourceRoots: {
"sap.ui.demo.todo": "./base/webapp"
}
},
tests: [
"sap/ui/demo/todo/test/unit/AllTests"
]
},
browsers: [ "Chrome" ]
});
};

Yeoman SharePoint generator installation problem. (unsupported engine)

I followed Microsoft docs for setting the SharePoint framework. https://learn.microsoft.com/en-us/sharepoint/dev/spfx/set-up-your-development-environment But when I got to the point where you are supposed to install the generator it gives me this error.
>>
PS C:\Users\jakub.yaghob> npm install #microsoft/generator-sharepoint -g
>>
npm WARN notsup Unsupported engine for got#5.7.1: wanted: {"node":">=0.10.0 <7"}
(current: {"node":"12.13.0","npm":"6.13.0"})
>>
npm WARN notsup Not compatible with your version of node/npm: got#5.7.1
>>
+ #microsoft/generator-sharepoint#1.9.1
updated 1 package in 8.851s
I have tried older versions of node.js but either they were too old for them to work with the new npm or they were too new to work with the generator.
Any help would be greatly appreciated. Thanks!
The current supported LTS version of NodeJS for the SharePoint Framework is both Node.js v8.x and Node.js v10.x. You need install Node.js for v8.x or v10.x.
Download Node.js: https://nodejs.org/en/download/releases/
I was also facing this issue. I found if Installed version 8.x.x of Node and then ran
npm install -g npm#5
This would lower the version of npm and allow me to install the generator.
I'm only getting started with Node and npm so have no idea what the impact of doing this is. However, it did work as I was able to run npm list -g --depth=0 and see the generator had been installed.

Error running purescript example

I'm trying to learn purescript starting with the simple "Hello World" from "Purescript by Example".
Issuing a "pulp run" throws this error:
* Building project in /home/peter/devel/purescript/my-project
Error found:
at bower_components/purescript-psci-support/src/PSCI/Support.purs line 21, column 1 - line 21, column 1
Unable to parse module:
unexpected "else"
expecting declaration or end of input
purs is of version 0.11.7, Pulp is version 12.2.0.
What am I doing wrong?
Thanks for your help.
The recent release of PureScript 0.12 has introduced breaking changes. Several new package versions will not work on older compilers. If you want to stay pre-0.12, and you are using bower, then do this to your project:
Delete all contents in the bower_components directory.
Downgrade all package versions in bower.json to pre-0.12 versions, such as prelude 3.2.0, console 3.0.0, and psci-support 3.0.0. You can use Pursuit and look at older bower.json files on GitHub to figure out these versions.
Run bower install.
Run pulp build.
Alternatively, you can upgrade to 0.12 with PureScript Version Manager. At this time 0.12 is not available on npm. To do this you can follow these installation instructions but in short is:
Uninstall the old compiler: npm uninstall -g purescript.
Install PSVM: npm install -g psvm.
Download 0.12: psvm install-latest.
Install 0.12: psvm use v0.12.0
Add PSVM's bin directory to your PATH which is C:\Users\<username>\.psvm\current\bin on Windows. Make sure your current session is updated with this new PATH variable.
Test out the new compiler: purs --version.
I'm working through PureScript by Example and ran into the same issue today. I stumbled across issue 3367, where gabejohnson directs us to the blog post, Working with 0.11.7 in a 0.12 world.
Long story short, it seems like PureScript 0.12 has introduced breaking changes, just like erisco said, and we should use psc-package instead of bower if we want to stay on 0.11.7 (because pulp doesn't work with PureScript 0.12 at the moment and bower is giving the team issues with dependency management).
You can install psc-package either with the binary or using npm install -g psc-package.
After that, you will need to tell pulp to use psc-package when you init a new project using pulp --psc-package init. Finally, install the lists package with psc-package install lists.
Keep in mind that packages do not have the purescript- prefix when using psc-package, so you just pass in the package name.
This is what got me back on track and I hope this helps you too.

I am getting following error when I run npm install -g ionic

I am getting following errors when I run npm install -g ionic :-
npm WARN deprecated cross-spawn-async#2.1.9: cross-spawn no longer requires a build toolchain, use it instead!
npm WARN deprecated lodash#2.1.0: lodash#<3.0.0 is no longer maintained. Upgrade to lodash#^4.0.0.
npm WARN deprecated minimatch#0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch#0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch#2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated lodash#1.0.2: lodash#<3.0.0 is no longer maintained. Upgrade to lodash#^4.0.0.
npm WARN deprecated graceful-fs#1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs#^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
Can anybody help me with this?

'gulp watch' Syntax error unexpected token illegal v3.8.10

I updated gulp and this is what I am getting now when I try 'gulp watch'
CLI version 3.8.10
Local version 3.8.10
Image of error:
http://s3.postimg.org/e6usiz1k3/issue.png
Your gulpfile.coffee is being interpreted as a JavaScript file. Node complains about the first comment - # is not a valid character in JS.
A while ago, the proposed solution by the gulp folks to use CoffeeScript was to use a gulpfile.js that requires CoffeeScript and your gulpfile.js. For example, the approach discussed here: https://github.com/gulpjs/gulp/issues/103
However, it seems that since 3.7 transpilers are automagically detected, as long as they are installed in your node_modules/. See https://github.com/gulpjs/gulp/blob/ae98edfbfbe8341f20c7cb5d4d4b8ec339ee44ae/CHANGELOG.md#370
added support for transpilers via liftoff 0.11 and interpret just npm
install your compiler (coffee-script for example) and it will work out
of the box
So you should
Check that your gulp is more recent than 3.7 with npm ls
Try running npm install coffee-script