npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@visual-framework/vf-core

v2.2.47

Published

Common dependencies for the Visual Framework.

Downloads

2,063

Readme

npm version This project is using Percy.io for visual regression testing.

👋 Downloading or cloning this repo? 🛑

Most won't need to clone this repo. Do so if you only wish to develop the architecture of the Visual Framework core or contribute a global component, otherwise use one of the boilerplates or install a component directly.


The Visual Framework Core (vf-core)

npm version Chat for support on Slack This project is using Percy.io for visual regression testing.

If you’re new to the Visual Framework system for life science websites: think of it as a Bootstrap but made for flexibility. The Visual Framework is highly modular for compatibility allowing for non-breaking use alongside other frameworks, like Bootstrap. So you can use components made elsewhere without breaking your site. Learn more about the Visual Framework system here.

This repo, for the "VF Core", is one part of that effort and — as the name suggests — is at the heart of all Visual Framework-based tools. The VF Core allows for extendable components and builds CSS, JS and other image-style assets.

Much like an arch-based design of a cistern, the vf-core supports complex systems with a flexible space inside. (For those that didn’t guess it, this is a photo of the Basilica Cistern; Image by Clint on Flickr)

In short: The VF Core is a base to build systems.

Here’s that column metaphor translates as a schematic of relationships for VF Core.

The vf-core is built with:

  • Fractal for component structure
  • Node and Gulp; to:
    • rollup JavaScript and handle assets
    • allow custom Sass/CSS components to be added to local projects
  • Dart Sass
  • Yeoman to make custom components interactively
  • Yarn to install components
  • Nunjucks for component templates
  • Lerna to publish components to npm as a mono-repo
  • Name-spacing for JavaScript and CSS; more on that in the coding standards

Making use of the VF Core

Here's a guide with the most common approaches.

FAQ

Here's a guide to the most common questions.

Have a problem?

See the troubleshooting guide.

Want to help develop?

Great. See the development guide.


Have opinions, ideas, concerns or want to get involved?

There are a few ways that we discuss and track ideas:

  • ⁉ General: Chat us for general ideas and discussion
  • ⚙️ Technical: GitHub issues here for implementing deeply technical and specific issues, like the Sass build process, browser bugs
  • 🏢 E-mail: if you have a sweeping Big Idea™️, e-mail Ken Hawkins [email protected]