Yarn install error

Question

Yarn install error

abalter opened this issue a year ago · 34 comments

Ubuntu 20.04, WSL2, Windows 11

(base) balter@expiyes:~/daedalOS$ yarn -v
4.0.2
(base) balter@expiyes:~/daedalOS$ yarn install
➤ YN0000: · Yarn 4.0.2
➤ YN0000: ┌ Resolution step
➤ YN0058: │ browserfs@https://github.com/jvilk/BrowserFS.git#commit=a96aa2d417995dac7d376987839bc4e95e218e06: Packing the package failed (exit code 1, logs can be found here: /tmp/xfs-e4bd089f/pack.log)
➤ YN0000: └ Completed in 43s 502ms
➤ YN0000: · Failed with errors in 43s 532ms

Suggestions?

Answer 1 · 2023-12-10T19:37:32.000Z

Hmm, well I did just change this line if you want to pull latest for it to try the "GitHub:" syntax. But I am unsure atm why it's doing that as I haven't tried Docker in a while. I will try it out asap to see, if you have any luck please post here.

Also maybe you can post the log it says is at tmp/xfs-e4bd089f/pack.log?

Answer 2 · 2023-12-10T20:06:51.000Z

What is the "Github:" syntax? :)

(base) balter@expiyes:~/daedalOS$ cat /tmp/xfs-f11cbf41/pack.log
Packing browserfs@https://github.com/jvilk/BrowserFS.git#commit=a96aa2d417995dac7d376987839bc4e95e218e06 from sources
Using Yarn Classic for bootstrap. Reason: "__metadata" key not found in yarn.lock, must be a Yarn classic lockfile

➤ YN0000: Downloading https://classic.yarnpkg.com/latest.js
➤ YN0000: Saving the new release in .yarn/releases/yarn-classic.cjs
➤ YN0000: Done in 1s 671ms

yarn install v1.22.19
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
[4/5] Linking dependencies...
[5/5] Building fresh packages...
$ npm run dist

> browserfs@2.0.0 dist
> npm-run-all build lint script:make_dist dist:build:node


> browserfs@2.0.0 build
> npm-run-all --parallel build:tsc build:scripts --sequential build:rollup --parallel build:webpack build:webpack-release


> browserfs@2.0.0 build:tsc
> tsc -p src


> browserfs@2.0.0 build:scripts
> tsc -p scripts


> browserfs@2.0.0 build:rollup
> rollup -c src/rollup.config.js


/tmp/xfs-4c926f80/build/temp/library/ts/index.js → build/temp/library/rollup/browserfs.rollup.js...
created build/temp/library/rollup/browserfs.rollup.js in 1.7s

> browserfs@2.0.0 build:webpack
> webpack --config src/webpack.config.js


> browserfs@2.0.0 build:webpack-release
> webpack -p --config src/webpack.config.js

/tmp/xfs-4c926f80/node_modules/loader-runner/lib/LoaderRunner.js:133
                if(isError) throw e;
                            ^

Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:68:19)
    at Object.createHash (node:crypto:138:10)
    at module.exports (/tmp/xfs-4c926f80/node_modules/webpack/lib/util/createHash.js:90:53)
    at NormalModule._initBuildHash (/tmp/xfs-4c926f80/node_modules/webpack/lib/NormalModule.js:386:16)
    at handleParseError (/tmp/xfs-4c926f80/node_modules/webpack/lib/NormalModule.js:434:10)
    at /tmp/xfs-4c926f80/node_modules/webpack/lib/NormalModule.js:466:5
    at /tmp/xfs-4c926f80/node_modules/webpack/lib/NormalModule.js:327:12
    at /tmp/xfs-4c926f80/node_modules/loader-runner/lib/LoaderRunner.js:370:3
    at iterateNormalLoaders (/tmp/xfs-4c926f80/node_modules/loader-runner/lib/LoaderRunner.js:211:10)
    at iterateNormalLoaders (/tmp/xfs-4c926f80/node_modules/loader-runner/lib/LoaderRunner.js:218:10)
    at /tmp/xfs-4c926f80/node_modules/loader-runner/lib/LoaderRunner.js:233:3
    at context.callback (/tmp/xfs-4c926f80/node_modules/loader-runner/lib/LoaderRunner.js:111:13)
    at untouched (/tmp/xfs-4c926f80/node_modules/source-map-loader/index.js:63:3)
    at module.exports (/tmp/xfs-4c926f80/node_modules/source-map-loader/index.js:60:10)
    at LOADER_EXECUTION (/tmp/xfs-4c926f80/node_modules/loader-runner/lib/LoaderRunner.js:119:14)
    at runSyncOrAsync (/tmp/xfs-4c926f80/node_modules/loader-runner/lib/LoaderRunner.js:120:4)
    at iterateNormalLoaders (/tmp/xfs-4c926f80/node_modules/loader-runner/lib/LoaderRunner.js:229:2)
    at Array.<anonymous> (/tmp/xfs-4c926f80/node_modules/loader-runner/lib/LoaderRunner.js:202:4)
    at Storage.finished (/tmp/xfs-4c926f80/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:43:16)
    at /tmp/xfs-4c926f80/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:79:9
    at /tmp/xfs-4c926f80/node_modules/graceful-fs/graceful-fs.js:78:16
    at FSReqCallback.readFileAfterClose [as oncomplete] (node:internal/fs/read/context:68:3) {
  opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

Node.js v20.9.0
/tmp/xfs-4c926f80/node_modules/loader-runner/lib/LoaderRunner.js:133
                if(isError) throw e;
                            ^

Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:68:19)
    at Object.createHash (node:crypto:138:10)
    at module.exports (/tmp/xfs-4c926f80/node_modules/webpack/lib/util/createHash.js:90:53)
    at NormalModule._initBuildHash (/tmp/xfs-4c926f80/node_modules/webpack/lib/NormalModule.js:386:16)
    at handleParseError (/tmp/xfs-4c926f80/node_modules/webpack/lib/NormalModule.js:434:10)
    at /tmp/xfs-4c926f80/node_modules/webpack/lib/NormalModule.js:466:5
    at /tmp/xfs-4c926f80/node_modules/webpack/lib/NormalModule.js:327:12
    at /tmp/xfs-4c926f80/node_modules/loader-runner/lib/LoaderRunner.js:370:3
    at iterateNormalLoaders (/tmp/xfs-4c926f80/node_modules/loader-runner/lib/LoaderRunner.js:211:10)
    at iterateNormalLoaders (/tmp/xfs-4c926f80/node_modules/loader-runner/lib/LoaderRunner.js:218:10)
    at /tmp/xfs-4c926f80/node_modules/loader-runner/lib/LoaderRunner.js:233:3
    at context.callback (/tmp/xfs-4c926f80/node_modules/loader-runner/lib/LoaderRunner.js:111:13)
    at untouched (/tmp/xfs-4c926f80/node_modules/source-map-loader/index.js:63:3)
    at module.exports (/tmp/xfs-4c926f80/node_modules/source-map-loader/index.js:60:10)
    at LOADER_EXECUTION (/tmp/xfs-4c926f80/node_modules/loader-runner/lib/LoaderRunner.js:119:14)
    at runSyncOrAsync (/tmp/xfs-4c926f80/node_modules/loader-runner/lib/LoaderRunner.js:120:4)
    at iterateNormalLoaders (/tmp/xfs-4c926f80/node_modules/loader-runner/lib/LoaderRunner.js:229:2)
    at Array.<anonymous> (/tmp/xfs-4c926f80/node_modules/loader-runner/lib/LoaderRunner.js:202:4)
    at Storage.finished (/tmp/xfs-4c926f80/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:43:16)
    at /tmp/xfs-4c926f80/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:79:9
    at /tmp/xfs-4c926f80/node_modules/graceful-fs/graceful-fs.js:78:16
    at FSReqCallback.readFileAfterClose [as oncomplete] (node:internal/fs/read/context:68:3) {
  opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

Node.js v20.9.0
ERROR: "build:webpack" exited with 1.
ERROR: "build" exited with 1.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Answer 3 · 2023-12-10T20:09:26.000Z

(base) balter@expiyes:~/daedalOS$ git pull
remote: Enumerating objects: 17, done.
remote: Counting objects: 100% (17/17), done.
remote: Compressing objects: 100% (3/3), done.
remote: Total 10 (delta 7), reused 10 (delta 7), pack-reused 0
Unpacking objects: 100% (10/10), 1.47 KiB | 7.00 KiB/s, done.
From github.com:DustinBrett/daedalOS
   41c020f2..e4a8f3d4  main       -> origin/main
Updating 41c020f2..e4a8f3d4
Fast-forward
 package.json                                  |   2 +-
 public/Program Files/ClassiCube/ClassiCube.js |   4 ++
 yarn.lock                                     | 244 +++---------------------------------------------------------------------------------------------------
 3 files changed, 10 insertions(+), 240 deletions(-)
(base) balter@expiyes:~/daedalOS$ yarn install
➤ YN0000: · Yarn 4.0.2
➤ YN0000: ┌ Resolution step
➤ YN0058: │ browserfs@https://github.com/jvilk/BrowserFS.git#commit=a96aa2d417995dac7d376987839bc4e95e218e06: Packing the package failed (exit code 1, logs can be found here: /tmp/xfs-33d4e614/pack.log)
➤ YN0000: └ Completed in 48s 140ms
➤ YN0000: · Failed with errors in 48s 181ms
(base) balter@expiyes:~/daedalOS$ cat /tmp/xfs-33d4e614/pack.log
Packing browserfs@https://github.com/jvilk/BrowserFS.git#commit=a96aa2d417995dac7d376987839bc4e95e218e06 from sources
Using Yarn Classic for bootstrap. Reason: "__metadata" key not found in yarn.lock, must be a Yarn classic lockfile

➤ YN0000: Downloading https://classic.yarnpkg.com/latest.js
➤ YN0000: Saving the new release in .yarn/releases/yarn-classic.cjs
➤ YN0000: Done in 1s 570ms

yarn install v1.22.19
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
[4/5] Linking dependencies...
[5/5] Building fresh packages...
$ npm run dist

> browserfs@2.0.0 dist
> npm-run-all build lint script:make_dist dist:build:node


> browserfs@2.0.0 build
> npm-run-all --parallel build:tsc build:scripts --sequential build:rollup --parallel build:webpack build:webpack-release


> browserfs@2.0.0 build:scripts
> tsc -p scripts


> browserfs@2.0.0 build:tsc
> tsc -p src


> browserfs@2.0.0 build:rollup
> rollup -c src/rollup.config.js


/tmp/xfs-cbb91235/build/temp/library/ts/index.js → build/temp/library/rollup/browserfs.rollup.js...
created build/temp/library/rollup/browserfs.rollup.js in 1.6s

> browserfs@2.0.0 build:webpack-release
> webpack -p --config src/webpack.config.js


> browserfs@2.0.0 build:webpack
> webpack --config src/webpack.config.js

/tmp/xfs-cbb91235/node_modules/loader-runner/lib/LoaderRunner.js:133
                if(isError) throw e;
                            ^

Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:68:19)
    at Object.createHash (node:crypto:138:10)
    at module.exports (/tmp/xfs-cbb91235/node_modules/webpack/lib/util/createHash.js:90:53)
    at NormalModule._initBuildHash (/tmp/xfs-cbb91235/node_modules/webpack/lib/NormalModule.js:386:16)
    at handleParseError (/tmp/xfs-cbb91235/node_modules/webpack/lib/NormalModule.js:434:10)
    at /tmp/xfs-cbb91235/node_modules/webpack/lib/NormalModule.js:466:5
    at /tmp/xfs-cbb91235/node_modules/webpack/lib/NormalModule.js:327:12
    at /tmp/xfs-cbb91235/node_modules/loader-runner/lib/LoaderRunner.js:370:3
    at iterateNormalLoaders (/tmp/xfs-cbb91235/node_modules/loader-runner/lib/LoaderRunner.js:211:10)
    at iterateNormalLoaders (/tmp/xfs-cbb91235/node_modules/loader-runner/lib/LoaderRunner.js:218:10)
    at /tmp/xfs-cbb91235/node_modules/loader-runner/lib/LoaderRunner.js:233:3
    at context.callback (/tmp/xfs-cbb91235/node_modules/loader-runner/lib/LoaderRunner.js:111:13)
    at untouched (/tmp/xfs-cbb91235/node_modules/source-map-loader/index.js:63:3)
    at module.exports (/tmp/xfs-cbb91235/node_modules/source-map-loader/index.js:60:10)
    at LOADER_EXECUTION (/tmp/xfs-cbb91235/node_modules/loader-runner/lib/LoaderRunner.js:119:14)
    at runSyncOrAsync (/tmp/xfs-cbb91235/node_modules/loader-runner/lib/LoaderRunner.js:120:4)
    at iterateNormalLoaders (/tmp/xfs-cbb91235/node_modules/loader-runner/lib/LoaderRunner.js:229:2)
    at Array.<anonymous> (/tmp/xfs-cbb91235/node_modules/loader-runner/lib/LoaderRunner.js:202:4)
    at Storage.finished (/tmp/xfs-cbb91235/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:43:16)
    at /tmp/xfs-cbb91235/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:79:9
    at /tmp/xfs-cbb91235/node_modules/graceful-fs/graceful-fs.js:78:16
    at FSReqCallback.readFileAfterClose [as oncomplete] (node:internal/fs/read/context:68:3) {
  opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

Node.js v20.9.0
/tmp/xfs-cbb91235/node_modules/loader-runner/lib/LoaderRunner.js:133
                if(isError) throw e;
                            ^

Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:68:19)
    at Object.createHash (node:crypto:138:10)
    at module.exports (/tmp/xfs-cbb91235/node_modules/webpack/lib/util/createHash.js:90:53)
    at NormalModule._initBuildHash (/tmp/xfs-cbb91235/node_modules/webpack/lib/NormalModule.js:386:16)
    at handleParseError (/tmp/xfs-cbb91235/node_modules/webpack/lib/NormalModule.js:434:10)
    at /tmp/xfs-cbb91235/node_modules/webpack/lib/NormalModule.js:466:5
    at /tmp/xfs-cbb91235/node_modules/webpack/lib/NormalModule.js:327:12
    at /tmp/xfs-cbb91235/node_modules/loader-runner/lib/LoaderRunner.js:370:3
    at iterateNormalLoaders (/tmp/xfs-cbb91235/node_modules/loader-runner/lib/LoaderRunner.js:211:10)
    at iterateNormalLoaders (/tmp/xfs-cbb91235/node_modules/loader-runner/lib/LoaderRunner.js:218:10)
    at /tmp/xfs-cbb91235/node_modules/loader-runner/lib/LoaderRunner.js:233:3
    at context.callback (/tmp/xfs-cbb91235/node_modules/loader-runner/lib/LoaderRunner.js:111:13)
    at untouched (/tmp/xfs-cbb91235/node_modules/source-map-loader/index.js:63:3)
    at module.exports (/tmp/xfs-cbb91235/node_modules/source-map-loader/index.js:60:10)
    at LOADER_EXECUTION (/tmp/xfs-cbb91235/node_modules/loader-runner/lib/LoaderRunner.js:119:14)
    at runSyncOrAsync (/tmp/xfs-cbb91235/node_modules/loader-runner/lib/LoaderRunner.js:120:4)
    at iterateNormalLoaders (/tmp/xfs-cbb91235/node_modules/loader-runner/lib/LoaderRunner.js:229:2)
    at Array.<anonymous> (/tmp/xfs-cbb91235/node_modules/loader-runner/lib/LoaderRunner.js:202:4)
    at Storage.finished (/tmp/xfs-cbb91235/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:43:16)
    at /tmp/xfs-cbb91235/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:79:9
    at /tmp/xfs-cbb91235/node_modules/graceful-fs/graceful-fs.js:78:16
    at FSReqCallback.readFileAfterClose [as oncomplete] (node:internal/fs/read/context:68:3) {
  opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

Node.js v20.9.0
ERROR: "build:webpack" exited with 1.
ERROR: "build" exited with 1.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Answer 4 · 2023-12-10T20:09:32.000Z

Ah I know about this error. I thought it was fixed in Docker. The ERR_OSSL_EVP_UNSUPPORTED error is from OpenSSL and you need a special node flag which I thought I had in the Dockerfile. The "github:" syntax was me changing the URL in the package file, but your issue the OpenSSL bug.

https://github.com/DustinBrett/daedalOS#notes

Answer 5 · 2023-12-10T20:15:15.000Z

The dockerfile worked! I'm having trouble installing with yarn.

Answer 6 · 2023-12-10T20:18:39.000Z

I thought I'd try building from an earlier commit, but still errors. Sidetrack-->this is a real problem with both yarn and npm is that they seem like they could be package managers but actually only work as build tools. As a person who is not a developer, I find I am rarely able to test out software using npm and yarn---inevitably there are errors and I get into a back and forth with the developer about "ok, just do this and it will fix it....". That's not a workable workflow for non-developers wanting to test out software. Basically, npm and yarn builds just are not stably reproducible.

Back to reality.....Maybe you could have a dev branch you work on and a stable main branch?

(base) balter@expiyes:~/daedalOS$ git reset --hard 41c020f22bffbc0fa59c1143ba42c5f3fa603e13
HEAD is now at 41c020f2 Pkg upgrade
(base) balter@expiyes:~/daedalOS$ yarn install
➤ YN0087: Migrated your project to the latest Yarn version 🚀

➤ YN0000: · Yarn 4.0.2
➤ YN0000: ┌ Resolution step
➤ YN0058: │ browserfs@https://github.com/jvilk/BrowserFS.git#commit=a96aa2d417995dac7d376987839bc4e95e218e06: Packing the package failed (exit code 1, logs can be found here: /tmp/xfs-104b1b7a/pack.log)
➤ YN0000: └ Completed in 45s 592ms
➤ YN0000: · Failed with errors in 45s 627ms
(base) balter@expiyes:~/daedalOS$ cat  /tmp/xfs-104b1b7a/pack.log
Packing browserfs@https://github.com/jvilk/BrowserFS.git#commit=a96aa2d417995dac7d376987839bc4e95e218e06 from sources
Using Yarn Classic for bootstrap. Reason: "__metadata" key not found in yarn.lock, must be a Yarn classic lockfile

➤ YN0000: Downloading https://classic.yarnpkg.com/latest.js
➤ YN0000: Saving the new release in .yarn/releases/yarn-classic.cjs
➤ YN0000: Done in 1s 848ms

yarn install v1.22.19
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
[4/5] Linking dependencies...
[5/5] Building fresh packages...
$ npm run dist

> browserfs@2.0.0 dist
> npm-run-all build lint script:make_dist dist:build:node


> browserfs@2.0.0 build
> npm-run-all --parallel build:tsc build:scripts --sequential build:rollup --parallel build:webpack build:webpack-release


> browserfs@2.0.0 build:scripts
> tsc -p scripts


> browserfs@2.0.0 build:tsc
> tsc -p src


> browserfs@2.0.0 build:rollup
> rollup -c src/rollup.config.js


/tmp/xfs-da244bf4/build/temp/library/ts/index.js → build/temp/library/rollup/browserfs.rollup.js...
created build/temp/library/rollup/browserfs.rollup.js in 1.6s

> browserfs@2.0.0 build:webpack-release
> webpack -p --config src/webpack.config.js


> browserfs@2.0.0 build:webpack
> webpack --config src/webpack.config.js

/tmp/xfs-da244bf4/node_modules/loader-runner/lib/LoaderRunner.js:133
                if(isError) throw e;
                            ^

Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:68:19)
    at Object.createHash (node:crypto:138:10)
    at module.exports (/tmp/xfs-da244bf4/node_modules/webpack/lib/util/createHash.js:90:53)
    at NormalModule._initBuildHash (/tmp/xfs-da244bf4/node_modules/webpack/lib/NormalModule.js:386:16)
    at handleParseError (/tmp/xfs-da244bf4/node_modules/webpack/lib/NormalModule.js:434:10)
    at /tmp/xfs-da244bf4/node_modules/webpack/lib/NormalModule.js:466:5
    at /tmp/xfs-da244bf4/node_modules/webpack/lib/NormalModule.js:327:12
    at /tmp/xfs-da244bf4/node_modules/loader-runner/lib/LoaderRunner.js:370:3
    at iterateNormalLoaders (/tmp/xfs-da244bf4/node_modules/loader-runner/lib/LoaderRunner.js:211:10)
    at iterateNormalLoaders (/tmp/xfs-da244bf4/node_modules/loader-runner/lib/LoaderRunner.js:218:10)
    at /tmp/xfs-da244bf4/node_modules/loader-runner/lib/LoaderRunner.js:233:3
    at context.callback (/tmp/xfs-da244bf4/node_modules/loader-runner/lib/LoaderRunner.js:111:13)
    at untouched (/tmp/xfs-da244bf4/node_modules/source-map-loader/index.js:63:3)
    at module.exports (/tmp/xfs-da244bf4/node_modules/source-map-loader/index.js:60:10)
    at LOADER_EXECUTION (/tmp/xfs-da244bf4/node_modules/loader-runner/lib/LoaderRunner.js:119:14)
    at runSyncOrAsync (/tmp/xfs-da244bf4/node_modules/loader-runner/lib/LoaderRunner.js:120:4)
    at iterateNormalLoaders (/tmp/xfs-da244bf4/node_modules/loader-runner/lib/LoaderRunner.js:229:2)
    at Array.<anonymous> (/tmp/xfs-da244bf4/node_modules/loader-runner/lib/LoaderRunner.js:202:4)
    at Storage.finished (/tmp/xfs-da244bf4/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:43:16)
    at /tmp/xfs-da244bf4/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:79:9
    at /tmp/xfs-da244bf4/node_modules/graceful-fs/graceful-fs.js:78:16
    at FSReqCallback.readFileAfterClose [as oncomplete] (node:internal/fs/read/context:68:3) {
  opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

Node.js v20.9.0
/tmp/xfs-da244bf4/node_modules/loader-runner/lib/LoaderRunner.js:133
                if(isError) throw e;
                            ^

Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:68:19)
    at Object.createHash (node:crypto:138:10)
    at module.exports (/tmp/xfs-da244bf4/node_modules/webpack/lib/util/createHash.js:90:53)
    at NormalModule._initBuildHash (/tmp/xfs-da244bf4/node_modules/webpack/lib/NormalModule.js:386:16)
    at handleParseError (/tmp/xfs-da244bf4/node_modules/webpack/lib/NormalModule.js:434:10)
    at /tmp/xfs-da244bf4/node_modules/webpack/lib/NormalModule.js:466:5
    at /tmp/xfs-da244bf4/node_modules/webpack/lib/NormalModule.js:327:12
    at /tmp/xfs-da244bf4/node_modules/loader-runner/lib/LoaderRunner.js:370:3
    at iterateNormalLoaders (/tmp/xfs-da244bf4/node_modules/loader-runner/lib/LoaderRunner.js:211:10)
    at iterateNormalLoaders (/tmp/xfs-da244bf4/node_modules/loader-runner/lib/LoaderRunner.js:218:10)
    at /tmp/xfs-da244bf4/node_modules/loader-runner/lib/LoaderRunner.js:233:3
    at context.callback (/tmp/xfs-da244bf4/node_modules/loader-runner/lib/LoaderRunner.js:111:13)
    at untouched (/tmp/xfs-da244bf4/node_modules/source-map-loader/index.js:63:3)
    at module.exports (/tmp/xfs-da244bf4/node_modules/source-map-loader/index.js:60:10)
    at LOADER_EXECUTION (/tmp/xfs-da244bf4/node_modules/loader-runner/lib/LoaderRunner.js:119:14)
    at runSyncOrAsync (/tmp/xfs-da244bf4/node_modules/loader-runner/lib/LoaderRunner.js:120:4)
    at iterateNormalLoaders (/tmp/xfs-da244bf4/node_modules/loader-runner/lib/LoaderRunner.js:229:2)
    at Array.<anonymous> (/tmp/xfs-da244bf4/node_modules/loader-runner/lib/LoaderRunner.js:202:4)
    at Storage.finished (/tmp/xfs-da244bf4/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:43:16)
    at /tmp/xfs-da244bf4/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:79:9
    at /tmp/xfs-da244bf4/node_modules/graceful-fs/graceful-fs.js:78:16
    at FSReqCallback.readFileAfterClose [as oncomplete] (node:internal/fs/read/context:68:3) {
  opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

Node.js v20.9.0
ERROR: "build:webpack-release" exited with 1.
ERROR: "build" exited with 1.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Answer 7 · 2023-12-10T20:29:36.000Z

The docker file has a line to setup the environment so that yarn will work. I am unsure why it's not working but will look into it.

The line is:

ENV NODE_OPTIONS=--openssl-legacy-provider

Answer 8 · 2023-12-10T20:30:49.000Z

My branch is stable but Docker is unneeded and just for people who like it. The notes in the readme explain the issue and it's not avoidable and is part of yarn.

Answer 9 · 2023-12-10T20:33:04.000Z

I think getting into back and forth with developers has more to do with not understanding the tools or errors. There is indeed a barrier to entry for people who want to work with code, but the issue is documented and the line in the Dockerfile was working quite recently.

Answer 10 · 2023-12-10T20:37:41.000Z

If you want to use yarn try this note. I have had to deal with this issue for years as have others. If you know of a workaround that would be great.

https://github.com/DustinBrett/daedalOS#notes

https://stackoverflow.com/questions/69692842/error-message-error0308010cdigital-envelope-routinesunsupported/69699772#69699772

Answer 11 · 2023-12-10T20:40:43.000Z

Closing as duplicate of other reports of this OpenSSL issue. Afaik it's just the way it is if we want to use deps which use old OpenSSL deps while also using newer Node.

#257

Answer 12 · 2023-12-10T20:48:19.000Z

Just to reiterate: The docker image works!!!!!

I'm having trouble building form yarn. That was it will run on my bare operating system, not a container.

Answer 13 · 2023-12-10T20:49:43.000Z

Indeed it works because of the line I was mentioning. Use that line/code, also stated in notes.

Answer 14 · 2023-12-10T21:24:26.000Z

If you know of a workaround that would be great.

There are a number of updated answers and comments on the SO post.

https://stackoverflow.com/a/73027407/188963

Answer 15 · 2023-12-10T21:26:09.000Z

Indeed and they don't apply to my situation. I have looked at all typical answers and beyond. Feel free to clone the repo and try them out, but it's not a simple issue and there are many comment threads out there of people annoyed at this specific issue with Node/OpenSSL.

For example the response you posted in the screenshot is for the OP of the SO comment who used react-scripts. In my case the version of browserfs I am using needs to be locked at the specific commit it is at because it's changed a lot. Using resolutions to change the deps has also not worked.

Answer 16 · 2023-12-10T21:29:36.000Z

Crazy that issue hasn't gotten fixed.

Answer 17 · 2023-12-10T21:32:40.000Z

I just tried

npm_config_yes=true npx yarn-audit-fix

And now I get a different error---not related to openSSL:

(base) balter@expiyes:~/daedalOS$ rm yarn.lock
(base) balter@expiyes:~/daedalOS$ git pull
Updating 32449617..6de65ab1
Fast-forward
 package.json |  5 +++--
 yarn.lock    | 16 +++++++---------
 2 files changed, 10 insertions(+), 11 deletions(-)
(base) balter@expiyes:~/daedalOS$ yarn install
➤ YN0000: · Yarn 4.0.2
➤ YN0000: ┌ Resolution step
➤ YN0085: │ + 7z-wasm@npm:1.1.0, @axe-core/playwright@npm:4.8.2, @monaco-editor/react@npm:4.6.0, @next/bundle-analyzer@npm:14.0.4, and 1127 more.
➤ YN0000: └ Completed in 2s 74ms
➤ YN0000: ┌ Fetch step
➤ YN0013: │ A package was added to the project (+ 7.08 KiB).
➤ YN0000: └ Completed in 1s 662ms
➤ YN0000: ┌ Link step
➤ YN0000: └ Completed in 0s 369ms
➤ YN0000: · Done in 4s 334ms
(base) balter@expiyes:~/daedalOS$ yarn build
Creating file tree ...
Creating json ...

Failed to compile.

./components/apps/Terminal/processGit.ts
56:11  Error: Unsafe assignment of an `any` value.  @typescript-eslint/no-unsafe-assignment
57:11  Error: Unsafe assignment of an `any` value.  @typescript-eslint/no-unsafe-assignment
57:48  Error: This assertion is unnecessary since it does not change the type of the expression.  @typescript-eslint/no-unnecessary-type-assertion
57:48  Error: Unsafe call of an `any` typed value.  @typescript-eslint/no-unsafe-call
58:7  Error: 'any' overrides all other types in this intersection type.  @typescript-eslint/no-redundant-type-constituents
59:43  Error: Unsafe assignment of an `any` value.  @typescript-eslint/no-unsafe-assignment
59:53  Error: Unsafe assignment of an `any` value.  @typescript-eslint/no-unsafe-assignment
69:11  Error: Unsafe assignment of an `any` value.  @typescript-eslint/no-unsafe-assignment
83:17  Error: Unsafe member access ._ on an `any` value.  @typescript-eslint/no-unsafe-member-access
84:31  Error: Unsafe member access ._ on an `any` value.  @typescript-eslint/no-unsafe-member-access
85:17  Error: Unsafe member access ._ on an `any` value.  @typescript-eslint/no-unsafe-member-access
87:15  Error: Unsafe assignment of an `any` value.  @typescript-eslint/no-unsafe-assignment
87:31  Error: Unsafe member access ._ on an `any` value.  @typescript-eslint/no-unsafe-member-access

info  - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules
   Linting and checking validity of types  .(base) balter@expiyes:~/daedalOS$

Answer 18 · 2023-12-10T21:34:21.000Z

If I could run this as a web app and instantly have a desktop environment on any linux VM without using X11, that would be a very very cool thing.

Answer 19 · 2023-12-10T21:35:24.000Z

Ya I also did yarn-audit-fix but it didn't help.

Today looking into your issue I had done upgrades and changed to github syntax which sadly did actually break something. I have since fixed that also so you can pull latest.

When I am not trying to fix posted bugs it's usually quite stable when I leave it most nights. Should pass tests now too https://github.com/DustinBrett/daedalOS/actions/runs/7160337995

Answer 20 · 2023-12-10T21:36:32.000Z

If I could run this as a web app and instantly have a desktop environment on any linux VM without using X11, that would be a very very cool thing.

It's not the same as a desktop environment in some ways from the pov of it's access to the system it runs on. But otherwise in theory you can. As you said Docker worked and yarn works most days except for that OpenSSL note which has been an issue ever since I moved away from Node 16 and as you can see from the SO/GH comments it's an issue for 1,000+ devs.

Answer 21 · 2023-12-10T21:41:32.000Z

Suggestions?

balter@expiyes:~/daedalOS$ git pull
Already up to date.
(base) balter@expiyes:~/daedalOS$ export NODE_OPTIONS=--openssl-legacy-provider
(base) balter@expiyes:~/daedalOS$ yarn install

➤ YN0000: · Yarn 4.0.2
➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed in 0s 348ms
➤ YN0000: ┌ Fetch step
➤ YN0000: └ Completed in 1s 663ms
➤ YN0000: ┌ Link step
➤ YN0000: └ Completed in 0s 384ms
➤ YN0000: · Done in 2s 610ms
(base) balter@expiyes:~/daedalOS$
(base) balter@expiyes:~/daedalOS$ yarn build
Creating file tree ...
Creating json ...

Failed to compile.

./components/apps/Terminal/processGit.ts
56:11  Error: Unsafe assignment of an `any` value.  @typescript-eslint/no-unsafe-assignment
57:11  Error: Unsafe assignment of an `any` value.  @typescript-eslint/no-unsafe-assignment
57:48  Error: This assertion is unnecessary since it does not change the type of the expression.  @typescript-eslint/no-unnecessary-type-assertion
57:48  Error: Unsafe call of an `any` typed value.  @typescript-eslint/no-unsafe-call
58:7  Error: 'any' overrides all other types in this intersection type.  @typescript-eslint/no-redundant-type-constituents
59:43  Error: Unsafe assignment of an `any` value.  @typescript-eslint/no-unsafe-assignment
59:53  Error: Unsafe assignment of an `any` value.  @typescript-eslint/no-unsafe-assignment
69:11  Error: Unsafe assignment of an `any` value.  @typescript-eslint/no-unsafe-assignment
83:17  Error: Unsafe member access ._ on an `any` value.  @typescript-eslint/no-unsafe-member-access
84:31  Error: Unsafe member access ._ on an `any` value.  @typescript-eslint/no-unsafe-member-access
85:17  Error: Unsafe member access ._ on an `any` value.  @typescript-eslint/no-unsafe-member-access
87:15  Error: Unsafe assignment of an `any` value.  @typescript-eslint/no-unsafe-assignment
87:31  Error: Unsafe member access ._ on an `any` value.  @typescript-eslint/no-unsafe-member-access

info  - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules

Answer 22 · 2023-12-10T21:43:27.000Z

Suggestions?

balter@expiyes:~/daedalOS$ git pull
Already up to date.
(base) balter@expiyes:~/daedalOS$ export NODE_OPTIONS=--openssl-legacy-provider
(base) balter@expiyes:~/daedalOS$ yarn install

➤ YN0000: · Yarn 4.0.2
➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed in 0s 348ms
➤ YN0000: ┌ Fetch step
➤ YN0000: └ Completed in 1s 663ms
➤ YN0000: ┌ Link step
➤ YN0000: └ Completed in 0s 384ms
➤ YN0000: · Done in 2s 610ms
(base) balter@expiyes:~/daedalOS$
(base) balter@expiyes:~/daedalOS$ yarn build
Creating file tree ...
Creating json ...

Failed to compile.

./components/apps/Terminal/processGit.ts
56:11  Error: Unsafe assignment of an `any` value.  @typescript-eslint/no-unsafe-assignment
57:11  Error: Unsafe assignment of an `any` value.  @typescript-eslint/no-unsafe-assignment
57:48  Error: This assertion is unnecessary since it does not change the type of the expression.  @typescript-eslint/no-unnecessary-type-assertion
57:48  Error: Unsafe call of an `any` typed value.  @typescript-eslint/no-unsafe-call
58:7  Error: 'any' overrides all other types in this intersection type.  @typescript-eslint/no-redundant-type-constituents
59:43  Error: Unsafe assignment of an `any` value.  @typescript-eslint/no-unsafe-assignment
59:53  Error: Unsafe assignment of an `any` value.  @typescript-eslint/no-unsafe-assignment
69:11  Error: Unsafe assignment of an `any` value.  @typescript-eslint/no-unsafe-assignment
83:17  Error: Unsafe member access ._ on an `any` value.  @typescript-eslint/no-unsafe-member-access
84:31  Error: Unsafe member access ._ on an `any` value.  @typescript-eslint/no-unsafe-member-access
85:17  Error: Unsafe member access ._ on an `any` value.  @typescript-eslint/no-unsafe-member-access
87:15  Error: Unsafe assignment of an `any` value.  @typescript-eslint/no-unsafe-assignment
87:31  Error: Unsafe member access ._ on an `any` value.  @typescript-eslint/no-unsafe-member-access

info  - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules

Pull latest changes. The commit that passed was to fix this issue you are having. Today when you were having issues I pushed a package update/change to try and improve the situation but made it worse because a new package has removed it's typings and needed the @type package added for it.

Answer 23 · 2023-12-10T21:45:42.000Z

I think if you could figure out the two following use cases, this project would get the attention it deserves:

Add to any docker image. docker run .... go to localhost:3000. Have a desktop environment in your container that use can use for stuff.
sudo apt install dadalos -y, conda install daedalos -y etc. daedalous run (or whatever, or sudo service dadalous start). Visit <web URL>/daedalos and see your desktop environmenmt.

Answer 24 · 2023-12-10T21:46:19.000Z

git pull says I'm up to date.

Answer 25 · 2023-12-10T21:47:34.000Z

Thanks for those suggestions. I don't use docker so I hadn't tried the run command but I will look into adding it. I will look into new ways to install it. To be honest I am kind of ok with the attention it gets currently as there is still a lot I think it doesn't do that people who would want to "install" it are likely expecting.

Answer 26 · 2023-12-10T21:48:08.000Z

(base) balter@expiyes:~/daedalOS$ git log
commit 6de65ab172aed119574ac762152a12428d6d7775 (HEAD -> main, origin/main, origin/HEAD)
Author: Dustin Brett <dustinbrett@gmail.com>
Date:   Sun Dec 10 13:13:40 2023 -0800

    minimist seperated types

Answer 27 · 2023-12-10T21:48:37.000Z

If I could have an instant desktop env without X11, I would use it all the time :)

Answer 28 · 2023-12-10T21:48:42.000Z

git pull says I'm up to date.

Not sure but the error you are having was coming from minimist typings which somehow got removed when I had changed an unrelated package. You can try nuking the entire repo and starting fresh as this change is to the lock file and might not be reflected if you don't do another yarn install.

6de65ab

Answer 29 · 2023-12-10T21:49:18.000Z

If I could have an instant desktop env without X11, I would use it all the time :)

That would be cool indeed. I think the thing to remember is that this is a desktop environment but very localized in what access it has to it's containing system.

Answer 30 · 2023-12-10T21:52:17.000Z

I gotta get to the next thing, but I'll try nuke and rebuild later.

That would be cool indeed. I think the thing to remember is that this is a desktop environment but very localized in what access it has to it's containing system.

I think that's a given. But consider that I spin up RStudio and Jupyter all the time and visit them through the browser. They can do anything to the os. So, in principle, your app is just another webapp.

Answer 31 · 2023-12-10T21:54:36.000Z

It's quite different because there is no conventional server unlike the other examples you have. It is purely client side and runs 100% in the browser. The only thing being served locally are HTML/JS/CSS files. Your examples callback to servers running on systems with system level access. If you are willing to add servers which do those things then yes indeed we can have system level access.

Answer 32 · 2023-12-11T02:16:34.000Z

Wait, if it is 100% client side, then why does it need to spin up a server? Jupyter, for example, has just a bare minimum of server stuff---just enough to run the language kernels (e.g. Python). No node or nginx or apache etc.

If it really runs 100% client side, would it be possible to put it in my /var/www/html/ folder and go to localhost/daedalos, for example. Or even, depending on how it's written, just open ......daedalos/index.html?

Answer 33 · 2023-12-11T02:18:40.000Z

Yes once it's built you can take the out folder and host it in /www/html.

Answer 34 · 2023-12-11T02:20:11.000Z

Sweet! Maybe I'll take a stab at getting file system access.