Zuplo Changelog

The Zuplo CLI now has the option to enable debug logs for greater visibility into errors and warnings.

Supported flags are:

• -v enables verbose output (warnings and errors)
• -vv enables very verbose output (info, warnings and errors)
• -vvv enables extremely verbose output (debug, info, warnings and errors)

These flags are available in @zuplo/cli@6.51.50 or newer. You can also upgrade by running npm i @zuplo/cli@latest.

The ability to use the Zuplo CLI on Windows is now available in beta as of @zuplo/cli@6.51.0.

This change means that the CLI will work natively on the Windows operating system, outside of the WSL.

This release includes important improvements to error handling, and bug fixes to the GitLab integration. We've also made improvements to our project templates and development tooling.

New Features 🎉#

• Improved error messages for invalid module imports - When importing modules incorrectly in your Zuplo project, you'll now receive more helpful and descriptive error messages that make it easier to identify and fix import issues. This enhancement improves the developer experience when working with custom modules and policies.

Bug Fixes 🐛#

• Fixed virtual module namespace collisions - Resolved an issue where virtual modules could conflict with each other due to namespace collisions. Virtual modules are now properly namespaced to ensure they work reliably alongside other modules in your project.

• Fixed GitLab integration infinite loop - Corrected a critical issue where fetching from GitLab repositories could cause infinite loops under certain conditions. This fix ensures stable and reliable synchronization with your GitLab repositories when using Zuplo's source control integration.

Documentation 📚#

• Added /hello route to project template - The default project template now includes a /hello route example, making it easier for new users to understand how to create and configure routes in their Zuplo API gateway.

Other Changes 🔄#

• Zudoku template enhancements - Updated the Zudoku documentation template to properly set Zuplo flags on scripts, ensuring better integration between Zuplo and the Dev Portal.

When your API throws an error in local development, you will now see a formatted output that includes the error message and stack trace in a more readable format. This will help you quickly identify the issue and debug your application.

We have overhauled the local development logs to provide a cleaner and more useful output. The new logs make it easier to see the HTTP method, route, and status code for each request. This will help you quickly identify issues and debug your application.

The logs are now color-coded to make it easier to distinguish between different HTTP methods and errors are highlighted in red. Additionally, the logs are now formatted in a more readable way, making it easier to scan through the output.

We have made a number of improvements to the create-zuplo-api package to make it even easier to start a Zuplo API project locally. The updated package includes the following enhancements:

• Option to include ESLint and Prettier configuration files in the project
• Improved error handling and messaging
• Automatically installing dependencies after project creation