fix: push-manifest.json CSS asset type

[rschristian]

What kind of change does this PR introduce?

bugfix

Did you add tests for your changes?

No

Summary

Bug introduced by typo in #1680

I believe this is more of a theoretical bug than a real issue at this time. Our test suite ensures everything is working as intended in the basic situations at least:

preact-cli/packages/cli/tests/images/build.js

Lines 219 to 237 in 6aba5d8

	{
	"/":{
	"bundle.\\w{5}.css":{
	"type":"style",
	"weight":1
	},
	"bundle.\\w{5}.js":{
	"type":"script",
	"weight":1
	},
	"route-home.chunk.\\w{5}.js":{
	"type":"script",
	"weight":0.9
	},
	"route-home.chunk.\\w{5}.css":{
	"type":"style",
	"weight":0.9
	}
	},

In order to handle async chunks generated by Webpack, we loop through the chunks and assign types accordingly. We don't skip the main route chunks while doing so despite them already being set (which maybe we should correct but not really important either way did it), so this corrected for the wrong type being set:

preact-cli/packages/cli/lib/lib/webpack/create-load-manifest.js

Lines 52 to 56 in 6aba5d8

	asyncFiles.chunks.forEach(asset => {
	asset.files = asset.files || [];
	asset.files.forEach(file => {
	if (/\.css$/.test(file)) {
	routeManifest[file] = { type: 'style', weight: 0.9 };

Does this PR introduce a breaking change?

No

[changeset-bot]

🦋 Changeset detected

Latest commit: 7723a12

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
preact-cli	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR