Site theme CSS is blocked in the browser

[T-Fletcher]

Hi, after installing Drupal and loading the site in the browser, no styles render. This happens with both the Minimal and Standard install profiles.

Checking the console shows the minified theme CSS is being blocked:

The resource from “css_1234.css" was blocked due to MIME type ("text/html") mismatch (X-Content-Type-Options: nosniff)

However accessing the CSS uri directly is met with a 500 error.

@simesy suggested running ddev exec yarn --cwd="core" from the post-install-actions item in the install.yaml script.

I'm not sure what this does, but it worked nicely and the theme CSS could load correctly.

---

Tested on:

• MacOS 14.0 Senoma, Intel core i9
• DDEV 1.22.7
• yarn 4.1.1 (after implementing this fix)
• Firefox 124.0

[simesy]

This happened at DrupalSouth code sprint, and i'm not 100% sure why it only happened for you @T-Fletcher !

yarn 4.1.1 (after implementing #12)

I assume after we fixed the yarn issue, we didn't run ddev get justafish/ddev-drupal-core-dev again, but I was switching between different people so i'm not sure.

I'll be reviewing the setup steps soon - I hadn't noticed the readme changes in cef0e47 until we started setting people up, but it was good improvement thanks @justafish

[T-Fletcher]

@simesy That may be the cause, I'll try a totally fresh run through the steps to confirm.

I always find it useful capturing what breaks the process e.g running through it once and reinstalling Drupal resulting in a database error, so there's less and less undocumented errors for people to encounter.

[rpkoller]

@simesy suggested running ddev exec yarn --cwd="core" from the post-install-actions item in the install.yaml script.

the command is executing yarn --cwd="core" inside the container root which is at /var/www/html, and --cwd="core" is basically telling yarn to run instead of in /var/www/html in /var/www/html/core instead.

[T-Fletcher]

I added in the core pack and yarn commands to the install steps, and tried several full runthroughs of the install steps and didn't encounter the issue again.

Bundled into #PR16

Thanks for the help everyone :)