Releases: visual-framework/vf-core
v2.1.0
v2.1.0 brings minor dependency updates and modernises the Sass compilation to use Dart Sass #990 #1019.
For the compiled CSS, the change to Dart Sass currently brings zero changes, however:
- The vf-core install is now lighter as it no longer requires the node-sass binaries
- We no longer need the gulp-sass layer and directly utilise Dart Sass
- More flexibility for including components (
@import 'vf-sass-config/index.scss';or@import '../vf-sass-config/index.scss';depending on your needs) - Future-proofing support for Dart Sass exclusive features.
What is the Visual Framework?
The Visual Framework 2.0 is a modular, compatible framework for life science websites and services. Want to know more, or build something with the VF? Read the guide. This release for the vf-core is the engine of the system.
Then what is the VF Core?
The "VF Core" is at the heart of all Visual Framework-based tools. It is the recommended way to make use of the Visual Framework components, allowing for installation of components without worry if they're local or yarn-installed. It's also the tool that allows access to component documentation across node-based environments.
The VF Core allows for extendable components and builds CSS, JS and other image-style assets. The VF Core is a base to build systems.
For more background, see the project's Readme.
What should I do with this release?
You don't need to download this directly, the vf-core is a dependency that is best used by npm and is pre-included in Visual Framework projects; see a list of starter projects.
👋 How can you get involved?
v2.0.1
This is a maintenance release of vf-core that updates npm dependencies and has minor improvements for the component interface.
The Visual Framework 2.0 is a modular, compatible framework for life science websites and services. Want to know more, or build something with the VF? Read the guide
Does this mean the Visual Framework is "done"?
No. The vf-core is the modular build process that compiles the Sass, JS, Nunjucks templates and Fractal component documentation. The components and vf-core use independent semantic versioning and will be released independently of each other.
Then what is the VF Core?
The "VF Core" is at the heart of all Visual Framework-based tools. It is the recommended way to make use of the Visual Framework components, allowing for installation of components without worry if they're local or yarn-installed. It's also the tool that allows access to component documentation across node-based environments.
The VF Core allows for extendable components and builds CSS, JS and other image-style assets. The VF Core is a base to build systems.
For more background, see the project's Readme.
What should I do with this release?
You don't need to download this directly, the vf-core is a dependency that is best used by npm and is pre-included in Visual Framework projects; see a list of starter projects.
What's next?
We're already planning features for a v2.1 release that will focus on the component documentation experience. We hope to release it in summer 2020.
The stable release of vf-core will also allow us to focus on building components (like tabs, tables and text) that make use of the system.
👋 How can you get involved?
v2.0.0
After four release candidates we're ready for a stable release of the VF Core.
The Visual Framework 2.0 is a modular, compatible framework for life science websites and services. Want to know more, or build something with the VF? Read the guide
Does this mean the Visual Framework is "done"?
No. The vf-core is the modular build process that compiles the Sass, JS, Nunjucks templates and Fractal component documentation. The components and vf-core use independent semantic versioning and will be released independently of each other.
Then what is the VF Core?
The "VF Core" is at the heart of all Visual Framework-based tools. It is the recommended way to make use of the Visual Framework components, allowing for installation of components without worry if they're local or yarn-installed. It's also the tool that allows access to component documentation across node-based environments.
The VF Core allows for extendable components and builds CSS, JS and other image-style assets. The VF Core is a base to build systems.
For more background, see the project's Readme.
What should I do with this release?
You don't need to download this directly, the vf-core is a dependency that is best used by npm and is pre-included in Visual Framework projects; see a list of starter projects.
What's next?
We're already planning features for a v2.1 release that will focus on the component documentation experience. We hope to release it in summer 2020.
The stable release of vf-core will also allow us to focus on building components (like tabs, tables and text) that make use of the system.
👋 How can you get involved?
v2.0.0-rc.4
After rc.3 we're ready for our fourth and likely final RC before a stable release.
What's new in Release Candidate 4?
Small optimisations:
- The component generation tool (
gulp vf-component) has improved boilerplate content #787 - Updates npm dependencies
Does a RC mean the VF is "done"?
No. The release candidate of vf-core is for the portable build process that compiles the Sass, JS, Nunjucks templates and Fractal component documentation. We're still actively building components to be used by vf-core.
🔰 What is the VF 2.0?
A modular, compatible framework for life science websites and services.
Want to know more, or build something with the VF? Read the guide
👋 How can you get involved?
v2.0.0-rc.3
After rc.2 we're ready for our third and likely final RC before a stable release.
What's new in Release Candidate 2?
We've found a few small optimisations:
- Improved the testing prior to npm publishing #706
- Fixes Babel to correctly compile JS to ES2015 #723
- Documentation note on yaml component syntax #736
- Fix a sporadic issue when running
vf-clean#737
Does a RC mean the VF is "done"?
No. The release candidate of vf-core is for the portable build process that compiles the Sass, JS, Nunjucks templates and Fractal component documentation. We're still actively building components to be used by vf-core.
🔰 What is the VF 2.0?
A modular, compatible framework for life science websites and services.
Want to know more, or build something with the VF? Read the guide
👋 How can you get involved?
v2.0.0-rc.2
After rc.1 we're ready for our second release candidate.
What's new in Release Candidate 2?
Very little from rc.1, we've optimised the component publishing workflow and vf-core's dependencies but otherwise the last several weeks have shown the current approach to be quite stable and we're confident in moving towards a release. Hopefully later this month.
Does a RC mean the VF is "done"?
No. The release candidate of vf-core is for the portable build process that compiles the Sass, JS, Nunjucks templates and Fractal component documentation. We're still actively building components to be used by vf-core.
🔰 What is the VF 2.0?
A modular, compatible framework for life science websites and services.
Want to know more, or build something with the VF? Read the guide
👋 How can you get involved?
v2.0.0-rc.1: The one where it's all done, except the components
After beta.6 we're ready for our first release candidate 🎉. all differences between beta.6 and RC.1
What's new in RC.1?
Very little from beta.6, some logging was improve (#667) but otherwise the last several weeks have shown the current approach to be quite stable and we're confident in moving towards a release. Hopefully in the first week of 2020.
Does a RC mean the VF is "done"?
No. The release candidate of vf-core is for the portable build process that compiles the Sass, JS, Nunjucks templates and Fractal component documentation. We're still actively building components to be used by vf-core.
This is a bit like having your new website built, now we just need the content components.
🔰 What is the VF 2.0?
A modular, compatible framework for life science websites and services.
Want to know more, or build something with the VF? Read the guide
👋 How can you get involved?
v2.0.0-beta.6
After beta.5 we're ready for beta.6. We expect this to be the final release before our RC. See all differences between beta.5 and beta.6
Note: components are now published to npm independently and more frequently than vf-core releases.
What's in beta.6
- Enhancement: Separate out logic of vf-build task … 64aeafc
some vf-build tasks should only be done by vf-core, this moves those tasks out of the reach of therequire('../node_modules/@visual-framework/vf-core/tools/gulp-tasks/_gulp_rollup.js')( - Enhancement: capture component JS assets … d01bb5c
A new gulp task vf-component-assets:js to grab JS files from components and deploy them in the{build}/assetsurl - Chore: Removes unneeded/unused code from
vf-frctl-theme#631
🔰 What is the VF 2.0?
A modular, compatible framework for life science websites and services.
Want to know more, or build something with the VF? Read the guide
👋 How can you get involved?
v2.0.0-beta.5
- After
beta.4we're ready for beta.5. We expect this to be the final release before our RC. - Note: components are now published to npm independently and more frequently than
vf-corereleases. - all differences between
beta.4andbeta.5
What's in beta.5
- Feature: move config to reusable npm install #617
- Feature: add a more efficient fractalBuildMode for client projects #616
- Bug: fix nunjucks compilation loop #618
- Bug: fix Fractal config path #614
- Bug: watch should ignore precompiled templates #598
🔰 What is the VF 2.0?
A modular, compatible framework for life science websites and services.
Want to know more, or build something with the VF? Read the guide
👋 How can you get involved?
v2.0.0-beta.4
After beta.3 we're ready for beta.4. We expect to soon have a RC for vf-core.
🔰 What is the VF 2.0? A modular, compatible framework for life science websites and services.
Want to know more, or build something with the VF? Read the guide
👋 How can you get involved?
🔍 What’s new since the last release?
Breaking changes
- None expected