Skip to content
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

CI: Webpack build throws with an error: [webpack-cli] Error: error:0308010C:digital envelope routines::unsupported #1985

Closed
PEZ opened this issue Nov 30, 2022 · 5 comments

Comments

@PEZ
Copy link
Collaborator

PEZ commented Nov 30, 2022

The CI build step crashes like so:

https://app.circleci.com/pipelines/github/BetterThanTomorrow/calva/5846/workflows/ced2b29e-da91-4410-ae5a-e4276b7d8845/jobs/27100

[webpack-cli] Error: error:0308010C:digital envelope routines::unsupported

Originally posted by @bpringe in #1983 (comment)

I find this issue, which seems to have cause a ruckus in the Webpack community:

It is many, many pages of comments. Seems like the conclusion is to upgrade to Webpack 5. Which sucks a bit for us, because that is what we are using! But anyway, now I am not as scared by this error. I'm sure we'll at least find a workaround with some sensible amount of work.

@PEZ
Copy link
Collaborator Author

PEZ commented Nov 30, 2022

I've reproduced the error in a separate branch. Let's see if I can figure out a way to fix it.

@PEZ
Copy link
Collaborator Author

PEZ commented Nov 30, 2022

Bumping the webpack dependency made it start to work: https://app.circleci.com/pipelines/github/BetterThanTomorrow/calva/5848/workflows/a177ebb5-a61b-444c-88dd-845b9a1e44b0

But I think the actual error is hidden now that we have a different build artifact. Reading the original error message more carefully, I see that the message comes from webpack-cli, where we actually still are on a version 4, while there is a version 5.0.0 available. I will try with bumping that as well.

@PEZ
Copy link
Collaborator Author

PEZ commented Nov 30, 2022

Using webpack-cli 5.0.0 also gives us a green build. I think that even if this is not the real fix, I am a bit too blind about the underlying cause to figure out what the real fix is and that we should make do with this hiding of the symptoms for now. (And it actually might be the real fix, it was pretty clear in that Webpack issue that using Webpack 5 is the fix.)

PEZ added a commit that referenced this issue Nov 30, 2022
Fixes #1985

See also: #1983
@PEZ PEZ mentioned this issue Nov 30, 2022
15 tasks
@bpringe
Copy link
Member

bpringe commented Dec 3, 2022

Why did it suddenly just break anyway? Was there a breaking change in a minor or patch update?

@PEZ
Copy link
Collaborator Author

PEZ commented Dec 5, 2022

I don't know, tbh. I think some cache was either invalidated or stale.

@PEZ PEZ closed this as completed Dec 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants