Hot off the heels of the [2.4.10 release](/updates/2021-03-29-component-updates/) we have updated some components, and updated the some pages on the documentation site. There are also a couple of `alpha` and `beta` releases of components making use of our layout components rather than component specifc CSS as well as deprecating variants that are no longer used or have been previously improved.
Hot off the heels of the [2.4.10 release](/updates/2021-03-29-component-updates/) we have updated some components, and updated the some pages on the documentation site. There are also a couple of `alpha` and `beta` releases of components making use of our layout components rather than component specific CSS as well as deprecating variants that are no longer used or have been previously improved.
Hot off the heels of the [2.4.11 release](/updates/2021-04-01-component-updates/), we're issuing a minor release that fixes a number of technical fixes and optimsations that will reduce the number of errors when building Sass and using the VF's JavaScript modules.
As a reminder, the rollup CSS and JS are compilations of many independently versioned components and is likely to contain changes that may disrupt the look of your site. We advise testing. Even better is to build your own CSS rollup from the npm sources, [you can find a guide here]({{ '/building' | url }}).
{#- don't forget to add the latest version to /tools/vf-component-library/src/site/_data/siteConfig.js -#}
Sometimes when a component has JavaScript, its module requires another components' JavaScript (example: embl-notifications JS requires vf-banner JS). To do this we use JS module imports. We've adapted that import approach slightly to use relative paths. The vf-core JavaScript build is "intelligent" and will attempt to resolve paths, but for non-clever importers the relative path will resolve many issues.
