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

@flosportsinc/flo-scss

v0.11.0

Published

Based on The most popular front-end framework for developing responsive, mobile first projects on the web.

Downloads

13

Readme

Table of contents

Quick start

Node 14 required

Install Flo-SCSS

Several quick start options are available:

Running documentation locally

  1. cd flo-scss
  2. Run through the tooling setup to install Jekyll (the site builder) and other Ruby dependencies with bundle install. WARNING - read installing ruby instructions for mac OS
  3. Run npm install to install Node.js dependencies.
  4. Run npm run release && npm start to compile CSS and JavaScript files, generate our docs, and watch for changes.
  5. Open http://localhost:9001 in your browser, and voilà.

Learn more about using Jekyll by reading its documentation.

Install Ruby on macOS

WARNING

Make sure you follow these instructions for installing Ruby on macOS. Mistakes made in the process of installing
Ruby on macOS can result in the operating system failing to boot.
  1. Install gpg and curl

    • brew install gpg curl
  2. Install RVM by following the instructions here

    • If you have an issue installing the GPG keys, contact your sysadmin
      • @Sysadmins, this could be a DNS issue. Try switching to 8.8.8.8 temporarily.
    • Avoid doing a multi-user install. You should not have to sudo
    • Install the stable version with \curl -sSL https://get.rvm.io | bash -s stable
  3. Run the RVM startup script and restart your terminals

    • Run source ~/.rvm/scripts/rvm
  4. Install the correct version of ruby for the project

    • The version can be found in the Gemfile
    • Run rvm install x.x.x replacing Xs with the correct version
  5. Run rvm use x.x.x to set your ruby version, and you're ready to go!

Troubleshooting

If you get the following error: Error: Node Sass does not yet support your current environment, your node-sass is not compatible with node version. Run the following command:

npm rebuild node-sass

//or

sudo npm rebuild node-sass

If you get the following error: gyp: No Xcode or CLT version detected! when attempting to update node-sass, run the following command:

sudo xcode-select --reset

Documentation

Flo-SCSS's documentation is built off of bootstrap's and can be found: https://flo-scss.flo.center/.

Read the Getting started page for information on the framework contents, templates and examples, and more.

Documentation search is powered by Algolia's DocSearch. Working on our search? Be sure to set debug: true in site/docs/assets/js/src/search.js file.

Contributing

Commit messages should follow semantic versioning.

build: (no change - e.g. build script changes that do not affect the final output for the user)
docs: (no change - e.g. changes to the documentation)
fix: (patch change - bug fix for the user, not a fix to a build script)
feat: (minor change - e.g. new feature for the user, not a new feature for build script)
breaking: (major breaking change - e.g. changing or removing class names or functionality. Changes that break parity with mainline bootstrap documentation.

Using docs will not update the npm version.

Releasing

Versioning

For transparency into our release cycle and in striving to maintain backward compatibility, Bootstrap is maintained under the Semantic Versioning guidelines. Sometimes we screw up, but we adhere to those rules whenever possible.

Copyright and license

Code and documentation copyright 2011-2020 the Bootstrap Authors and Twitter, Inc. Code released under the MIT License. Docs released under Creative Commons.