Upgrade: 0.1.0-beta.19

Rápidamente actualiza a la última versión ejecutando el siguiente comando

npm

npx @studiocms/upgrade

pnpm

pnpx @studiocms/upgrade

yarn

yarn dlx @studiocms/upgrade

Breaking Changes

• StudioCMS now only support NodeJS 20 and higher
• New Config structure, please verify your studiocms.config.* file when updating. Config files can also end in .js, .mjs, .ts, .mts now! Allowing flexibility, and full type-safety.
  For more information related to these changes checkout the new Config Reference
• Image Service has been migrated to the plugin system. If you were previously using the cloudinary-js image service you will need to migrate to utilizing the new @studiocms/cloudinary-image-service plugin, and configure your preferredImageService
• Integrated Effect^, and migrated most of the codebase to an Effect based structure. (old functions have been deprecated to allow migration to new Effects)
• Added support for @studiocms/web-vitals to replace @astrojs/web-vitals in the future. Note, Astro has deprecated @astrojs/web-vitals and asked us to maintain the package, please update to the new package to prevent future issues as we plan to remove support for the old package in a future update.
  For more information about web-vitals checkout our Web-Vitals plugin guide

Bug fixes

• Removed usage of remote google fonts for the dashboard, resolving potential network blocking issues.

Note

Please note that in beta.16 we introduced a breaking change with the password hashing algorithm. While previous passwords will still work, we recommend that users update their passwords after upgrading to beta.19. The legacy password hashing support will be removed in a future release.