Coralite v0.18.0
Coralite v0.18.0 delivers a focused update to improve module structure, type safety, and consistency across the project. This release centers on internal refactoring for better developer experience, with clear improvements in how libraries are imported and typed.
Key Improvements #
The primary changes in this release aim to streamline how developers interact with Coralite’s core functionality. By reorganizing exports and aligning import paths, we reduce friction when building and maintaining applications.
coremodules are now properly exported, enabling direct access to foundational utilities without needing to reference plugins.- Type exports have been added to the core package, improving TypeScript support and reducing type inference errors in IDEs.
- A default export has been added for
Coralite, simplifying usage in common scenarios where a single entry point is preferred. - A
tsconfig.jsonfile has been introduced to thecoralitepackage, ensuring consistent TypeScript compilation across projects.
Bug Fixes #
Several fixes ensure consistency in rendering, imports, and performance. These updates address subtle but impactful issues that could affect development workflows.
- The banner structure in test environments has been corrected to render properly and avoid layout inconsistencies.
- Imports within the codebase now consistently use the
coralitecore package instead of outdated plugin references. - The code highlight component now imports from the correct path:
coralite/utilsinstead ofcorallite/utils. - Fixed a typo in the
nested-componentsfixture:corallite-headerhas been renamed tocoralite-titlefor consistency. - Reduced image sizes in CSS templates to improve load performance and reduce bundle size.
How to Upgrade #
Upgrading to v0.18.0 is straightforward. Depending on your project setup, you’ll need to update one or both of the following packages:
npm install coralite@0.18.1
If you’re using coralite-scripts for scaffolding, update that as well:
npm install coralite-scripts@0.18.1
After upgrading, review any import paths in your code. The changes to core exports and module structure may require minor adjustments to ensure compatibility.
For a full list of changes, including detailed commit messages, view the full changelog.
