Inconsistent bundling of css assets between builds (Remix) #25
Comments
|
sorry to bother you as this is not directly related to the plugin. This line comes from the remix vite plugin, I'll try to investigate more about it. if (movedAssetPaths.length) {
viteConfig.logger.info(
[
"",
`${colors.green("✓")} ${movedAssetPaths.length} asset${
movedAssetPaths.length > 1 ? "s" : ""
} moved from Remix server build to client assets.`,
...movedAssetPaths.map((movedAssetPath) =>
colors.dim(path.relative(ctx.rootDirectory, movedAssetPath))
),
"",
].join("\n")
);
} |
|
I have been also follow this question :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using the
?urlimport, there seems to be a mismatch between the generated assets, resulting in two identical css files (with different hashes), with the mismatched included at the top of the<head/>. I think it started after the switch to Rollup bundler in some of the earlier releases.For some reason I cannot reproduce bug in the sandbox, I think it has to do with remix bundler. If you can point out where this is related, I could open the issue in the remix repo. With the remix example provided from this repo all is fine.
This happens occasionally between builds, so maybe it's due to some internal caching. When this mismatch occurs, this line outputs:
Logs:
The text was updated successfully, but these errors were encountered: