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

vueboot

v0.4.5

Published

A collection of Vuejs components that wrap Bootstrap components

Downloads

415

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

morgulmorgul

Keywords

vuebootstrap

Readme

VueBoot

VueJS components and directives written using Bootstrap v4, leveraging the official Bootstrap JS.

Note: This should be considered pre-release software. There will be bugs! (Many of them from Bootstrap v4, in fact)

Project Focus

This project is focused on providing useful/convenient VueJS wrappers around existing Bootstrap components. It does not wrap all of them (because that seems unnecessary), and really only wraps the ones I find the need for. I'm open to adding new components, but see the Contributing section for what I'll accept.

Why?

For two reasons, mostly. First is, I want to use Bootstrap v4 and VueJS v1.0. While VueStrap is a very nice looking project, it has not been updated for either VueJS v1.0 or Bootstrap v4. I'm crazy, I want to start working on the bleeding edge.

The second reason is a bit more personal, and born out of experience with UIBootstrap. The Bootstrap developers put a lot of work into their javascript code, and implementations that replace it with 'native' framework code, while neat, tend to have many more bugs, especially with regards to positioning. Bootstrap's code get more attention by having a larger user base, and therefore I trust it more. And any issue I do have, should be resolved faster, all things being equal. So, personally, I'd rather wrap Bootstrap's javascript, as opposed to replacing it.

Usage

VueBoot is available on both npm and bower. For complete usage instructions, please see the Usage page on the main site.

Contributing

Contributions are welcome! I accept pull requests, feature requests (through the issues), and all that. Primarily, I'm interested in bug fixes or additional features to current components. If you want to add a component, you'll have to follow my guideline below.

Adding components

Guideline: Is this component new, does it add functionality, or does it significantly improve the syntax for using an existing Bootstrap component?

While I'm ok with adding components, the focus of the goal is using Bootstrap JS. If using the Bootstrap component is straightforward, I see no reason to wrap it up in VueJS 'just because'. There needs to be some value added. I'm open to being convinced so don't feel discouraged. If there's any doubt, make an issue requesting it as a feature first, before putting the work into a pull request.