Skip to content

Downgrade grunt-concurrent to last working version - #48377

Merged
maddiedierker merged 1 commit into
stagingfrom
fix-webpack-build-output
Sep 30, 2022
Merged

Downgrade grunt-concurrent to last working version#48377
maddiedierker merged 1 commit into
stagingfrom
fix-webpack-build-output

Conversation

@maddiedierker

@maddiedierker maddiedierker commented Sep 29, 2022

Copy link
Copy Markdown
Contributor

Follow-up to #48105.

Upgrading grunt-concurrent broke the output for the webpack build that displays % building message. This plugin isn't actively developed anymore (the latest version, 3.0.0, was published 3 years ago). I tried downgrading to 2.x.x, but it had the same issue. I did some digging to find whether there was a configuration change or something that's causing this, but couldn't find anything, so I'm downgrading to the last known working version.

Now, when you run yarn start, which runs 2 concurrent watch tasks:

code-dot-org/apps/Gruntfile.js

Lines 1228 to 1239 in bed3874

(config.concurrent = {
// run our two watch tasks concurrently so that they dont block each other
watch: {
tasks: [
'watch',
envConstants.HOT ? 'webpack-dev-server:watch' : 'webpack:watch'
],
options: {
logConcurrentOutput: true
}
}
}),

...you see the expected output as the concurrent tasks are building:

Screen.Recording.2022-09-29.at.3.58.18.PM.mov

@maddiedierker
maddiedierker requested a review from a team September 29, 2022 23:06
Comment thread apps/yarn.lock
version "1.5.2"
resolved "https://registry.yarnpkg.com/async/-/async-1.5.2.tgz#ec6a61ae56480c0c3cb241c95618e20892f9672a"
integrity sha1-7GphrlZIDAw8skHJVhjiCJL5Zyo=
integrity sha512-nSVgobk4rv61R9PUSDtYt7mPVB2olxNR5RWJcAsH676/ef11bUZwvu7+RGYrYauVdDPcO519v68wRhXQtxsV9w==

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For my learning –– do you know how it's determined which sha function is used for these? No worries if not

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is kind of a guess based on some light reading, but i think it depends on two things:

  1. the version of yarn. with yarn 2.0, sha512 became the default, but was available in earlier versions with the unsafe-disable-integrity-migration option
  2. the sha that the package has available. i don't feel like i really understand this piece 😄 but someone mentions it in this stack overflow. maybe this piece depends on the version of yarn/NPM that the package publisher is using?

@megcrenshaw megcrenshaw left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clever solution!

@maddiedierker
maddiedierker merged commit cf02e72 into staging Sep 30, 2022
@maddiedierker
maddiedierker deleted the fix-webpack-build-output branch September 30, 2022 18:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants