-
Notifications
You must be signed in to change notification settings - Fork 286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(webpack): prod build chokes on upgraded ssh2 binaries #1405
Labels
bug
Something isn't working
dependencies
Pull requests that update a dependency file
Developer_Experience
Milestone
Comments
petermetz
added
bug
Something isn't working
dependencies
Pull requests that update a dependency file
Developer_Experience
labels
Oct 2, 2021
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Oct 2, 2021
…-cacti#1405 This removes all webpack minified builds entirely. This has the benefits of faster and stabler builds. What we lose is efficiency of deployments in resource constrained environments where the bundle size would make a difference but the idea here is to crawl, walk and then run with having these minified bundles enabled being the running part of the equation. Root cause ========== If you update the yarn lock file to the latest & greatest it breaks the webpack prod build at the moment with this beauty: ERROR in ../../node_modules/ssh2/lib/protocol/crypto/build/Release/sshcrypto.node 1:0 Module parse failed: Unexpected character '' (1:0) You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders (Source code omitted for this binary file) @ ../../node_modules/ssh2/lib/protocol/crypto.js 30:12-60 @ ../../node_modules/ssh2/lib/client.js 34:29-60 @ ../../node_modules/ssh2/lib/index.js 27:10-32 @ ../../node_modules/docker-modem/lib/ssh.js 1:13-35 @ ../../node_modules/docker-modem/lib/modem.js 6:8-24 @ ../../node_modules/dockerode/lib/docker.js 2:10-33 @ ./src/main/typescript/besu/besu-test-ledger.ts 8:36-56 @ ./src/main/typescript/public-api.ts 20:25-59 @ ./src/main/typescript/index.ts 13:13-36 To Reproduce rm yarn.lock && yarn && yarn configure && yarn build Fixes hyperledger-cacti#1405 Signed-off-by: Peter Somogyvari <[email protected]>
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Oct 2, 2021
…-cacti#1405 This removes all webpack minified builds entirely. This has the benefits of faster and stabler builds. What we lose is efficiency of deployments in resource constrained environments where the bundle size would make a difference but the idea here is to crawl, walk and then run with having these minified bundles enabled being the running part of the equation. Root cause ========== If you update the yarn lock file to the latest & greatest it breaks the webpack prod build at the moment with this beauty: ERROR in ../../node_modules/ssh2/lib/protocol/crypto/build/Release/sshcrypto.node 1:0 Module parse failed: Unexpected character '' (1:0) You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders (Source code omitted for this binary file) @ ../../node_modules/ssh2/lib/protocol/crypto.js 30:12-60 @ ../../node_modules/ssh2/lib/client.js 34:29-60 @ ../../node_modules/ssh2/lib/index.js 27:10-32 @ ../../node_modules/docker-modem/lib/ssh.js 1:13-35 @ ../../node_modules/docker-modem/lib/modem.js 6:8-24 @ ../../node_modules/dockerode/lib/docker.js 2:10-33 @ ./src/main/typescript/besu/besu-test-ledger.ts 8:36-56 @ ./src/main/typescript/public-api.ts 20:25-59 @ ./src/main/typescript/index.ts 13:13-36 To Reproduce rm yarn.lock && yarn && yarn configure && yarn build Fixes hyperledger-cacti#1405 Signed-off-by: Peter Somogyvari <[email protected]>
petermetz
added a commit
that referenced
this issue
Oct 4, 2021
This removes all webpack minified builds entirely. This has the benefits of faster and stabler builds. What we lose is efficiency of deployments in resource constrained environments where the bundle size would make a difference but the idea here is to crawl, walk and then run with having these minified bundles enabled being the running part of the equation. Root cause ========== If you update the yarn lock file to the latest & greatest it breaks the webpack prod build at the moment with this beauty: ERROR in ../../node_modules/ssh2/lib/protocol/crypto/build/Release/sshcrypto.node 1:0 Module parse failed: Unexpected character '' (1:0) You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders (Source code omitted for this binary file) @ ../../node_modules/ssh2/lib/protocol/crypto.js 30:12-60 @ ../../node_modules/ssh2/lib/client.js 34:29-60 @ ../../node_modules/ssh2/lib/index.js 27:10-32 @ ../../node_modules/docker-modem/lib/ssh.js 1:13-35 @ ../../node_modules/docker-modem/lib/modem.js 6:8-24 @ ../../node_modules/dockerode/lib/docker.js 2:10-33 @ ./src/main/typescript/besu/besu-test-ledger.ts 8:36-56 @ ./src/main/typescript/public-api.ts 20:25-59 @ ./src/main/typescript/index.ts 13:13-36 To Reproduce rm yarn.lock && yarn && yarn configure && yarn build Fixes #1405 Signed-off-by: Peter Somogyvari <[email protected]>
RafaelAPB
pushed a commit
to RafaelAPB/blockchain-integration-framework
that referenced
this issue
Mar 9, 2022
…-cacti#1405 This removes all webpack minified builds entirely. This has the benefits of faster and stabler builds. What we lose is efficiency of deployments in resource constrained environments where the bundle size would make a difference but the idea here is to crawl, walk and then run with having these minified bundles enabled being the running part of the equation. Root cause ========== If you update the yarn lock file to the latest & greatest it breaks the webpack prod build at the moment with this beauty: ERROR in ../../node_modules/ssh2/lib/protocol/crypto/build/Release/sshcrypto.node 1:0 Module parse failed: Unexpected character '' (1:0) You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders (Source code omitted for this binary file) @ ../../node_modules/ssh2/lib/protocol/crypto.js 30:12-60 @ ../../node_modules/ssh2/lib/client.js 34:29-60 @ ../../node_modules/ssh2/lib/index.js 27:10-32 @ ../../node_modules/docker-modem/lib/ssh.js 1:13-35 @ ../../node_modules/docker-modem/lib/modem.js 6:8-24 @ ../../node_modules/dockerode/lib/docker.js 2:10-33 @ ./src/main/typescript/besu/besu-test-ledger.ts 8:36-56 @ ./src/main/typescript/public-api.ts 20:25-59 @ ./src/main/typescript/index.ts 13:13-36 To Reproduce rm yarn.lock && yarn && yarn configure && yarn build Fixes hyperledger-cacti#1405 Signed-off-by: Peter Somogyvari <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
dependencies
Pull requests that update a dependency file
Developer_Experience
Describe the bug
If you update the yarn lock file to the latest & greatest it breaks the webpack prod build at the moment with this beauty:
To Reproduce
Expected behavior
Build is stable/works.
Logs/Stack traces
Full logs:
2021-10-02-build-webpack-prod-error-ssh2.log
Cloud provider or hardware configuration:
GHA hosted runner + dev machine
Operating system name, version, build:
Ubuntu 20.04
Hyperledger Cactus release version or commit (git rev-parse --short HEAD):
0.10.0
The text was updated successfully, but these errors were encountered: