Summary Looks like when I upgraded all of our dependencies and fix

Seems like the issue might have been introduced in <a class="commit-link" data-hoverca

Updating the build pipeline to include custom CMS templates for preview about one-click-hugo-cms HOT 1 CLOSED

maxcell commented on July 24, 2024

Updating the build pipeline to include custom CMS templates for preview

from one-click-hugo-cms.

Comments (1)

cgc commented on July 24, 2024 1

Seems like the issue might have been introduced in be22c5f, which loads netlify-cms from unpkg instead of the included cms.js file:

--- a/src/cms.html
+++ b/site/static/admin/index.html
@@ -9,6 +9,6 @@
   <script src="https://identity-js.netlify.com/v1/netlify-identity-widget.js"></script>
 </head>
 <body>
-  <script src="<%= htmlWebpackPlugin.files.chunks.cms.entry %>"></script>
+  <script src="https://unpkg.com/netlify-cms@^2.0.0/dist/netlify-cms.js"></script>
 </body>
 </html>

I was able to get a fix working on my site -- here are the changes pulled out into a commit cgc@97a313e. They deal with breaking changes in two packages during the version updates in #674:

date-fns - format strings changed in 2.0, the release notes have a table of changes here
html-webpack-plugin - htmlWebpackPlugin.files has a new format that disappointingly discards bundle names between 3.x and 4.x (documented in project readme, search for "htmlWebpackPlugin.files"). The change is a bit annoying because it means you have to assume the order of bundles. Since object property order is based on insertion order (in ES6), as long as that order isn't modified by webpack, the index in my commit is appropriate for the order of bundles in webpack.common.js (empirically, it also works). An issue to reverse this change (so, to once again access bundles by name) has been opened but is stale: jantimon/html-webpack-plugin#1369.

from one-click-hugo-cms.

Recommend Projects