v1.3.0 Release Notes

Posted on 11/21/2024 to release/v1

We are very pleased to announce the release of fusion.ssg v1.3.0. This release focusses on the developer experience and includes new features, enhancements, and a number of bug fixes.

Please note that as of this release release notes will now only highlight the most important new features, enhancements, bug fixes, and breaking changes. A detailed change log that includes all the issues and their associated labels addressed per release is now also separately maintained on https://github.com/4awpawz/fusion.ssg.

Sincerely,

The Team

v1.3.0 Highlights

New projects can now be created without scaffolding.

A new option, --bare, has been added to fusions.ssg's project generator, fpg, that allows you to generate new projects without scaffolding.

Example:

`fpg n | new --bare <target_folder>`

Tokens in inline scripts and code blocks are now ignored.

You can now safely use tokens in inline scripts and code blocks without fusion.ssg complaining that they are unresolved.

The reserved baseURL token can now be used in your project's css files.

If you are building a site that has background images and your project employs the use of fusion.ssg's reserved baseURL token with a value other than '', you no longer have to declare 2 URLs for the image, one for development builds, and one for release builds. Instead, you can now prepend the URL with fusion.ssg's reserved baseURL token and the URL will resolve properly for both development and release builds.

Example:

.hero {
    background-image: url({baseURL}/media/stretching-cat.png);
}

This distinction was not made in previous versions.

Metrics reporting to the console after each build cycle now defaults to a condensed set of metrics for both development and release builds.

The detailed metrics reporting of previous versions is still available via the --verbose option and can be applied to either development or release builds or to both.

New default metrics reporting example:

condensed metrics reporting

Metrics reporting with the --verbose option example:

verbose metrics reporting

Eliminate multiple "project does not contain a 404.html document" warnings when refreshing the browser.

Beginning with fusion.ssg v1.3.0 the warning about a missing 404.html file is no longer implemented in browsersync.js, and is handled internally by fusion.ssg.

If you are upgrading a project to v1.3.0 or greater then you should remove the following from your project's browsersync.js file which is located in your project's root folder:

console.log(chalk.yellowBright("Warning: this site is missing a 404.html doc - using default 404.html."));

Breaking Changes