The cms build is compiled by webpack on a separate configuration #6391
Conversation
|
Deploy preview for using-drupal ready! Built with commit d3dddec |
|
Deploy preview for gatsbygram ready! Built with commit d3dddec |
|
Thanks for digging so far into this @emanueleperuffo! I didn't try the development build, but production builds are still pulling the main application styles in alongside the cms styles. |
|
Really? That doesn't happen to my cms builds... /cms.fd9333d1614f87e0d2b2.css here contains only code from netlify-cms. <!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8">
<title>Content Manager</title>
<link href="/cms.fd9333d1614f87e0d2b2.css" rel="stylesheet"></head>
<body>
<script type="text/javascript" src="/cms-938562dcd7f063f4c1d7.js"></script></body>
</html>Or maybe you meant that in your main application you find css from netlify? |
|
It's a single bundle, but it includes the styles from the main application. This may depend on plugins, which has long been the problem with CMS styles in Gatsby. I'm using the Gatsby Netlify CMS starter to test against, which uses the sass plugin. Sent with GitHawk |
|
@emanueleperuffo it looks like this can be closed now that #6356 has landed? Please-reopen if I've got it wrong. |
|
Perfect |
This tries to fix the netlify-cms plugin for v2 creating a separate webpack compilation