Strapi Release: 1.1.0

TL;DR

Strapi v1.1.0: Simplified Architecture & Improved Developer Experience

Strapi v1.1.0 introduces a significant architectural change by removing the modules concept and improving the API structure. This release focuses on simplifying the developer experience with better onboarding, more flexible version requirements, and enhanced tooling. The update also includes improvements to the Strapi Studio integration and fixes several issues related to the admin panel and generators.

Highlight of the Release

• Simplified application architecture by removing modules concept
• Improved API structure for better organization and maintainability
• More permissive Node.js and npm version requirements
• Enhanced developer experience with better onboarding documentation
• Automatic installation of new adapters in development environment

Migration Guide

Migration from v1.0.6 to v1.1.0

Modules to API Migration

The most significant change in this release is the removal of the modules concept in favor of a more straightforward API structure. To migrate:

1. Move your module code to the new API structure
2. Update any references to modules in your codebase
3. Follow the new API organization guidelines

Custom Generators

If you were using custom generators, they should now work properly with the $ strapi update command. No additional configuration is needed.

Admin Panel Access

The admin panel is now consistently served at the /admin path. If you had custom routing or proxying for the admin panel, you may need to update your configuration.

Strapi Studio Integration

If you wish to disable Strapi Studio integration, you can now do so through configuration. Check the updated documentation for details.

Upgrade Recommendations

This release contains significant architectural improvements and is recommended for all Strapi users. The removal of the modules concept and improved API structure will benefit all projects in terms of maintainability and clarity.

How to Upgrade

1. Backup your project
2. Update your Strapi version to v1.1.0
3. Follow the migration guide to adapt to the new API structure (if you were using modules)
4. Test thoroughly in a development environment before deploying to production

The upgrade should be straightforward for most users, but those with heavy customization of the module structure will need to spend more time adapting to the new API organization.

Bug Fixes

• Admin Panel Access: Fixed issue with admin panel access by ensuring it's consistently served at the /admin path.
• API Registration: Fixed issue where deleted APIs were still being registered during rebuild.
• ORM Configuration: Ensured ORM configurations are properly maintained during rebuilds.
• Router Tests: Fixed outdated router tests to match current implementation.
• Travis CI Compatibility: Fixed issues with Travis CI testing across different Node.js versions.
• Generator Updates: Fixed update process for custom generators.
• File Extraction: Improved file extraction by executing unzip function in the correct order of the files array.

New Features

Architectural Improvements

• Removed Modules Concept: Simplified the application structure by removing the modules concept in favor of a more straightforward API structure.
• Improved API Organization: Restructured APIs for better maintainability and clearer organization.
• Automatic Adapter Installation: New adapters are now automatically installed in development environments.
• Custom Generator Support: Developers can now use custom generators with the $ strapi update command.
• Studio Integration Control: Added ability for developers to disable Strapi Studio integration if desired.

Developer Experience

• Relaxed Version Requirements: More permissive about Node.js and npm versions to accommodate more development environments.
• Improved Documentation: Enhanced wording and steps for getting started with Strapi.
• Updated Strapi Studio: Improved wording and guidelines for the SaaS offering (Strapi Studio).

Security Updates

No specific security fixes were mentioned in this release. However, keeping your Strapi installation updated to the latest version is always recommended for security best practices.

Performance Improvements

• Bootstrap Timeout: Increased bootstrap timeout to allow for more complex initialization processes.
• Simplified Architecture: The removal of the modules concept and improved API structure should result in better performance and reduced overhead.
• File Processing: Improved file extraction process by ensuring proper ordering during unzip operations.
• Build Process: Optimized build process with better handling of binary file permissions.

Impact Summary

Strapi v1.1.0 represents a significant step forward in simplifying the framework's architecture and improving the developer experience. By removing the modules concept and enhancing the API structure, Strapi becomes more intuitive and maintainable.

The more permissive Node.js and npm version requirements make Strapi accessible to a wider range of development environments. Automatic adapter installation in development and improved onboarding documentation reduce friction for new developers.

For existing users, the migration path is clear but will require some effort if modules were heavily used in your application. The benefits of the new structure should outweigh the migration costs in the long term.

The improvements to the admin panel access and Strapi Studio integration provide more flexibility and control for developers and administrators. Overall, this release focuses on making Strapi more developer-friendly while maintaining its powerful capabilities.

Full Release Notes