Any idea how to fix the attached errors after npm install and npm start lightning chart typescript example from github,
running on Windows 11, the Manu Help shows Node.js: 16.14.2, but the vsc terminal node --version shows 18.12.0
Visual Studio Code > Help
Version: 1.73.0 (user setup)
Electron: 19.0.17
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Windows_NT x64 10.0.22000
Sandboxed: No
Opened a New Terminal in VSC:
npm install
/////////////////////npm install
PS C:\Users\XYZ\Downloads\lcjs-typescript-example-master\lcjs-typescript-example-master> npm install
npm WARN deprecated urix#0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated chokidar#2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated resolve-url#0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated source-map-url#0.4.0: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated debug#4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug#4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug#4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug#3.2.6: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug#3.2.6: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated querystring#0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated uuid#3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated source-map-resolve#0.5.2: See https://github.com/lydell/source-map-resolve#deprecated
added 655 packages, and audited 656 packages in 8s
19 packages are looking for funding
run `npm fund` for details
14 vulnerabilities (1 moderate, 12 high, 1 critical)
To address all issues, run:
npm audit fix
Run `npm audit` for details.
///////////////////////npm start
PS C:\Users\XYZ\Downloads\lcjs-typescript-example-master\lcjs-typescript-example-master> npm start
> lcjs-typescript-example#1.0.0 start
> webpack-dev-server
(node:23548) [DEP0111] DeprecationWarning: Access to process.binding('http_parser') is deprecated.
(Use `node --trace-deprecation ...` to show where the warning was created)
i ｢wds｣: Project is running at http://localhost:8080/
i ｢wds｣: webpack output is served from /
i ｢wds｣: Content not from webpack is served from C:\Users\XYZ\Downloads\lcjs-typescript-example-master\lcjs-typescript-example-master\dist
Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:71:19)
at Object.createHash (node:crypto:133:10)
at module.exports (C:\Users\XYZ\Downloads\lcjs-typescript-example-master\lcjs-typescript-example-master\node_modules\webpack\lib\util\createHash.js:135:53)
at NormalModule._initBuildHash (C:\Users\XYZ\Downloads\lcjs-typescript-example-master\lcjs-typescript-example-master\node_modules\webpack\lib\NormalModule.js:417:16)
at handleParseError (C:\Users\XYZ\Downloads\lcjs-typescript-example-master\lcjs-typescript-example-master\node_modules\webpack\lib\NormalModule.js:471:10)
at C:\Users\XYZ\Downloads\lcjs-typescript-example-master\lcjs-typescript-example-master\node_modules\webpack\lib\NormalModule.js:503:5
at C:\Users\XYZ\Downloads\lcjs-typescript-example-master\lcjs-typescript-example-master\node_modules\webpack\lib\NormalModule.js:358:12
at C:\Users\XYZ\Downloads\lcjs-typescript-example-master\lcjs-typescript-example-master\node_modules\loader-runner\lib\LoaderRunner.js:373:3
at iterateNormalLoaders (C:\Users\XYZ\Downloads\lcjs-typescript-example-master\lcjs-typescript-example-master\node_modules\loader-runner\lib\LoaderRunner.js:214:10)
at iterateNormalLoaders (C:\Users\XYZ\Downloads\lcjs-typescript-example-master\lcjs-typescript-example-master\node_modules\loader-runner\lib\LoaderRunner.js:221:10)
node:internal/crypto/hash:71
this[kHandle] = new _Hash(algorithm, xofLen);
^
Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:71:19)
at Object.createHash (node:crypto:133:10)
at module.exports (C:\Users\XYZ\Downloads\lcjs-typescript-example-master\lcjs-typescript-example-master\node_modules\webpack\lib\util\createHash.js:135:53)
at NormalModule._initBuildHash (C:\Users\XYZ\Downloads\lcjs-typescript-example-master\lcjs-typescript-example-master\node_modules\webpack\lib\NormalModule.js:417:16)
at handleParseError (C:\Users\XYZ\Downloads\lcjs-typescript-example-master\lcjs-typescript-example-master\node_modules\webpack\lib\NormalModule.js:471:10)
at C:\Users\XYZ\Downloads\lcjs-typescript-example-master\lcjs-typescript-example-master\node_modules\webpack\lib\NormalModule.js:503:5
at C:\Users\XYZ\Downloads\lcjs-typescript-example-master\lcjs-typescript-example-master\node_modules\webpack\lib\NormalModule.js:358:12
at C:\Users\XYZ\Downloads\lcjs-typescript-example-master\lcjs-typescript-example-master\node_modules\loader-runner\lib\LoaderRunner.js:373:3
at iterateNormalLoaders (C:\Users\XYZ\Downloads\lcjs-typescript-example-master\lcjs-typescript-example-master\node_modules\loader-runner\lib\LoaderRunner.js:214:10)
at Array.<anonymous> (C:\Users\XYZ\Downloads\lcjs-typescript-example-master\lcjs-typescript-example-master\node_modules\loader-runner\lib\LoaderRunner.js:205:4) {
opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
library: 'digital envelope routines',
reason: 'unsupported',
code: 'ERR_OSSL_EVP_UNSUPPORTED'
}
Node.js v18.12.0
PS C:\Users\XYZ\Downloads\lcjs-typescript-example-master\lcjs-typescript-example-master> node --version
v18.12.0
This issue seems to come from WebPack using MD5 hashes by default which OpenSSL has deprecated. I have pushed a change to the lcjs-typescript-example repository that hopefully fixes this issue for you.
If it doesn't help then take a look at this other discussion on StackOverflow https://stackoverflow.com/a/69746937/6198227
You should be able to use --openssl-legacy-provider node option to use older version of OpenSSL that supports the deprecated hashing methods.
Related
we executed the same workflow an hour apart. The initial run was successful and then we received the following error in the subsequent execution:
This CDK CLI is not compatible with the CDK library used by your
application. Please upgrade the CLI to the latest version. (Cloud
assembly schema version mismatch: Maximum schema version supported is
15.0.0, but found 16.0.0)
This error occurs in the cdk synth stage. As far as I can tell, we are installing aws-cdk#latest (2.5.0) and our requirements.txt is installing a number of packages. When I compared the dependencies between the two runs I found the following:
Successful build:
Collecting aws-cdk.cloud-assembly-schema==1.138.2
Downloading aws_cdk.cloud_assembly_schema-1.138.2-py3-none-any.whl (150 kB)
Failed build:
Collecting aws-cdk.cloud-assembly-schema==1.139.0
Downloading aws_cdk.cloud_assembly_schema-1.139.0-py3-none-any.whl (153 kB)
I'm assuming the "latest" version was picked up? However, how can I track this type of information? I have tried a number of searches include aws-cdk versions, aws-cdk 1.139.0 release date, etc... Perhaps, I don't understand the package versioning?
Any feedback is appreciated. Thank you!
This is because the new 1.139 release upgraded the schema version to 16.0.0, whereas 2.5.0 is still on 15.0.0. 16.0.0 in CDKv2 will be included in a future release. In the meantime, install the 1.139 version of the CLI, it will work.
A general way to solve this would be to upgrade your constructs to v2 to never have this mismatch.
GitHub issue.
UPDATE: The latest CDK CLI 2.9.0 supports schema version 16.0.0.
I have a dockerfile using registry.redhat.io/ubi8/ubi-minimal as base image. Installed git using microdnf, downloaded few packages, but while trying to remove using microdnf remove git, I get these errors.
microdnf --enablerepo=ubi-8-baseos --enablerepo=ubi-8-appstream install git
error: Could not depsolve transaction; 2 problems detected:
Problem 1: package git-core-2.27.0-1.el8.x86_64 requires less, but none of the providers can be installed
- conflicting requests
- problem with installed package git-core-2.27.0-1.el8.x86_64
Problem 2: package git-core-2.27.0-1.el8.x86_64 requires openssh-clients, but none of the providers can be installed
- package git-core-doc-2.27.0-1.el8.noarch requires git-core = 2.27.0-1.el8, but none of the providers can be installed
- conflicting requests
- problem with installed package git-core-doc-2.27.0-1.el8.noarch
Reordering the package dependencies helped to resolve the issue.
microdnf remove libedit openssh openssh-clients git-core git-core-doc git less helped.
Wish microdnf also supported dnf's autoremove :(
I have recently encountered an issue with building my ember project with bitbucket pipelines:
+ ember build --environment="production"
Could not start watchman
Visit https://ember-cli.com/user-guide/#watchman for more info.
Building
Environment: production
cleaning up
cleaning up...
Build Error (broccoli-persistent-filter:Babel > [Babel: ember-data]) in ember-data/adapters/json-api.js
Cannot use the decorators and decorators-legacy plugin together
I am currently using ember-cli version 3.8.1.
The issue occurs with all build environments, not just production.
What baffles me is that no new npm package or ember addon was added between last successful build and the ones that have been failing since - and now if I re-run the successful build, that will also fail.
I have gone back in the commit history to a commit that worked, then fast-forward into the present step-by-step - always deleting the node_modules and reinstalling the packages. It always works locally, but it will always fail when the pipeline is run.
I have also tried updating my docker image.
I have already gone through and tried the solutions listed here - but it seems like they have already been addressed in version 3.8.1.
Also, if it is any help, this is my bitbucket-pipelines.yml:
pipelines:
branches:
master:
- step:
name: Building Ember Project
script:
- npm install
- npm install firebase-tools
- ember build --environment="production"
- step:
trigger: manual
deployment: production
name: Deploy to Production
script:
- firebase use prod
- firebase deploy --non-interactive --token ${FIREBASE_TOKEN}
Thank you all in advance!
This sounds like a sub-dependency changing on the fly under the hood. Do you have an npm or yarn lockfile commited as part of your repo? Lockfiles are specifically designed to keep from hitting snags like this
I have gone through the below errors,
Build error : “Cannot use the decorators and decorators-legacy plugin together”
Build error: 'relationshipStateFor' is not exported by -private\system\record-data-for.js
On browser got Expected store.createRecordDataFor to be implemented but it wasn't.
Reason for the above error is with ember-data addon and mismatch in ember-cli version installed for my project.
In your package.json, You might have defined ember-cli version( "ember-cli": "^3.11.0",) with ^ symbol this means it will install latest version which is less than the 4.0.0. So your ember-cli in node_modules might be installed to the latest version.
The above mentioned error is caused by the ember-cli version which was installed and pointed to 3.15.0. So I have removed the ^ and updated "ember-cli": "3.11.0", and removed node_modules and did npm install that solves the above problem.
On my system, ArchLinux x86_64, I have installed the package opam-git which was working the last time I used it.
The following command opam update fail with this message:
opam update
=-=- Updating package repositories =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[ERROR] curl: code 404 while downloading https://opam.ocaml.org/1.3/urls.txt
[ERROR] Could not update repository default
In this link https://github.com/ocaml/opam-repository/issues/6231 they say:
it is 2.0.dev now
What should I do to resolve my problem?
This is a git devel version of opam, did I get this right? Current opam release is 1.2.
And it is from Arch AUR?
It looks like AUR published an inconsistent opam dev state from git.
Once the git is consistent (pull request done) file a bug report, wait for the update, and do a new opam install from AUR.
Or just rely on the current versions from ocaml.org, IMO the premier source.
BTW when encountering problems with your local .opam directory and the compiled ocaml packages: the whole stuff can be deleted and reinstalled without any side effects (provided your own source is somewhere else). This is the functional paradigm.
/Str.
install environment:
windows 7 64 bit/XP 32bit
zend stutdio 9.0.2
org.eclipse.egit.repository-3.1.0.201310021548-r
I want to use git in zend studio 9.0.2 .but my PC can not connect to the internet.so i download egit 3.1.0 package.i try to install this package in "install new software",but failed with error:
Cannot complete the install because one or more required items could not be found.
Software being installed: Eclipse Git Team Provider 3.1.0.201310021548-r (org.eclipse.egit.feature.group 3.1.0.201310021548-r)
Missing requirement: Git Team Provider UI 3.1.0.201310021548-r (org.eclipse.egit.ui 3.1.0.201310021548-r) requires 'bundle org.eclipse.team.core [3.6.100,4.0.0)' but it could not be found
Cannot satisfy dependency:
From: Eclipse Git Team Provider 3.1.0.201310021548-r (org.eclipse.egit.feature.group 3.1.0.201310021548-r)
To: org.eclipse.egit.ui [3.1.0.201310021548-r]
can anyone help me?
This answer might be applicable to you: Can Install EGit: Missing requirement: Git Team Provider Core In other words, it is an internal version conflict between parts of Eclipse.