@sveltia/cms 0.115.0 → 0.115.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -142,7 +142,9 @@ Sveltia CMS is the only project that doesn’t inherit the complexity, technical
142
142
 
143
143
  This “total reboot” allows us to implement [hundreds of improvements](#differentiators) without getting stuck in a legacy system.
144
144
 
145
- We are continuing to address the [issues](https://github.com/decaporg/decap-cms/issues) reported in the predecessor’s repository and deliver the enhancements that Netlify CMS users have desired for a long time. Of the 3 successors, only Sveltia CMS is continuously developed, with [regular updates](https://github.com/sveltia/sveltia-cms/releases) and a [clear roadmap](#roadmap). For that reason, Sveltia CMS is the **true successor to Netlify CMS** — not just a spiritual successor or a mere alternative.
145
+ We are continuing to address the [issues](https://github.com/decaporg/decap-cms/issues) reported in the predecessor’s repository and deliver the enhancements that Netlify CMS users have long desired. We are dedicating significant time and effort to improving compatibility and enhancing every aspect of the product. Of the 3 successors, only Sveltia CMS is receiving consistent development, making outstanding progress, and providing [regular updates](https://github.com/sveltia/sveltia-cms/releases) and a [clear roadmap](#roadmap).
146
+
147
+ That’s why Sveltia CMS is the **true successor to Netlify CMS** — not just a spiritual successor or a mere alternative.
146
148
 
147
149
  ### Our goals
148
150
 
@@ -283,6 +285,7 @@ We’ve made various improvements to help you get your work done faster and more
283
285
  - Also supports [multiple configuration files](#providing-multiple-configuration-files) to allow developers to modularize the configuration.[^197]
284
286
  - We provide an [up-to-date JSON schema](#enabling-autocomplete-and-validation-for-the-configuration-file) for YAML/JSON configuration files, which enables autocomplete and validation in VS Code and other editors.[^253] If you use [deprecated options](#deprecations) in a supported code editor, you should receive a warning.
285
287
  - Improved TypeScript support: We keep our type definitions for `CMS.init()` and other methods complete, accurate, up-to-date and annotated.[^190][^191][^192][^193][^227] This makes it easier to provide a site config object when [manually initializing](https://decapcms.org/docs/manual-initialization/) the CMS.
288
+ - Sveltia CMS alerts you when there is a mismatch between the `format` and `extension` options of a collection.
286
289
 
287
290
  ### Better backend support
288
291
 
@@ -306,6 +309,7 @@ The [GitHub](https://decapcms.org/docs/github-backend/), [GitLab](https://decapc
306
309
  - We have implemented a workaround for a [GraphQL complexity limit issue](https://github.com/sveltia/sveltia-cms/issues/525) in GitLab 18.4.2, while Netlify/Decap CMS continues to suffer from the same problem.[^301]
307
310
  - Our Gitea/Forgejo backend is high-performing because it retrieves multiple entries at once. It also supports Git LFS ([documentation](https://docs.gitea.com/administration/git-lfs-setup)). Additionally, the backend won’t cause 400 Bad Request errors due to the presence of `DRAFT_MEDIA_FILES` in file paths.[^222]
308
311
  - Features the all-new [local repository workflow](#working-with-a-local-git-repository) for a better DX. See the [productivity section](#better-productivity) above.
312
+ - An indicator is displayed in the account menu when using the local repository workflow.[^302]
309
313
  - Developers can select the local and remote backends while working on a local server.
310
314
  - The Test backend saves entries and assets in the browser’s [origin private file system](https://web.dev/articles/origin-private-file-system) (OPFS) so that changes are not discarded when the browser tab is closed or reloaded.[^194] The persistent storage support works with all modern browsers [except Safari](https://bugs.webkit.org/show_bug.cgi?id=254726).
311
315
 
@@ -2671,3 +2675,5 @@ This project would not have been possible without the open source Netlify CMS pr
2671
2675
  [^300]: Netlify/Decap CMS [#7257](https://github.com/decaporg/decap-cms/issues/7257)
2672
2676
 
2673
2677
  [^301]: Netlify/Decap CMS [#7627](https://github.com/decaporg/decap-cms/issues/7627)
2678
+
2679
+ [^302]: Netlify/Decap CMS [#3286](https://github.com/decaporg/decap-cms/issues/3286)