Strapi Release: 4.0.0-beta.9

TL;DR

Strapi v4.0.0-beta.9 introduces significant improvements to the template system, now hosting templates on npm instead of GitHub, along with various UI quality assurance fixes and enhancements to the component management system. This release streamlines template usage, improves the webhook and role management interfaces, and fixes several UI issues.

Highlight of the Release

• Templates now hosted on npm instead of GitHub for better distribution and versioning
• Improved component management with displayName replacing name property
• Enhanced webhook table interface with better usability
• Fixed UI issues in role management list views
• Added static list of reserved names for better developer experience

Migration Guide

Template System Changes

If you were using custom templates with Strapi v4 beta.8, you'll need to adapt to the new npm-based template system:

1. Templates should now be published to npm instead of hosted on GitHub
2. Make sure your templates follow the new allowed content rules
3. For local template development, refer to the updated template structure

Component Property Renaming

If you were working with components programmatically:

1. Update any code referencing component name to use displayName instead
2. Update any UI components that display component names to use the new property
3. Check for any custom code that might be affected by this naming change

Upgrade Recommendations

This beta release contains significant improvements to the template system and UI fixes. We recommend all Strapi v4 beta users upgrade to this version, especially if you:

• Use or create Strapi templates
• Work extensively with components
• Manage webhooks or roles through the admin interface

To upgrade:

npm install [email protected]

or

yarn add [email protected]

After upgrading, test your application thoroughly, especially if you have custom templates or components.

Bug Fixes

UI Fixes

• Fixed WYSIWYG link button sizing issues
• Fixed ellipsis truncation on name and description in settings role list view
• Made webhook table boxes clickable to add entries
• Fixed component addition functionality
• Fixed middleware generator

Other Fixes

• Fixed isFile check in template system
• Updated dependencies and yarn lock files
• Fixed tests across multiple components

New Features

Template System Overhaul

• Templates are now hosted on npm instead of GitHub for better distribution and versioning
• Added semver template checking to ensure compatibility
• Support for local templates has been improved
• Re-enabled template functionality with updated allowed content rules
• Added a static list of reserved names to prevent conflicts

Component Management Improvements

• Renamed component name property to displayName for better clarity
• Updated all related interfaces to use the new naming convention
• Improved component addition functionality

Security Updates

No specific security fixes were mentioned in this release.

Performance Improvements

Template System Performance

• Improved template loading and processing with npm-based distribution
• Optimized template merging process

UI Responsiveness

• Enhanced rendering of list views for roles and webhooks
• Improved component management interface responsiveness

Impact Summary

This beta release represents a significant step forward in Strapi v4's development, particularly for the template system which now leverages npm for distribution instead of GitHub. This change improves template versioning, accessibility, and management.

The renaming of component properties from name to displayName improves clarity but may require updates to custom code. Various UI improvements enhance the experience for content managers and administrators, particularly in the webhooks and role management interfaces.

While this is still a beta release and not recommended for production environments, it provides important refinements to the developer and administrator experience as Strapi v4 moves closer to a stable release.

Full Release Notes