Weave Code
Bootstrap Sass Laravel Package
twbs/bootstrap-sass
bootstrap-sass is the official Sass port of Bootstrap 3, packaging Bootstrap’s CSS, JavaScript, and fonts for Rails, Sprockets, Compass, and LibSass projects. It exposes variables, mixins, and helpers for customizable, maintainable styles.
bootstrap-sass is a Sass-powered version of Bootstrap 3, ready to drop right into your Sass powered applications.
Frequently asked questions about Bootstrap Sass
- Is twbs/bootstrap-sass a Composer package I can install in Laravel?
- No. bootstrap-sass is an npm/frontend Sass distribution, not a PHP or Composer package, so it should not be added to composer.json. In Laravel it can only be used in the frontend asset layer, typically through npm and Laravel Mix for legacy projects.
- How do I install bootstrap-sass in a Laravel Mix project?
- Install it as a frontend dev dependency with npm, then import the Bootstrap Sass entry point from resources/sass/app.scss before your custom styles. Compile through the existing Laravel Mix pipeline and keep Bootstrap JavaScript separate from the Sass package. Document any jQuery requirement for Bootstrap 3 plugins.
- Does bootstrap-sass work with Laravel Vite and Dart Sass?
- Treat Vite or Dart Sass integration as a compatibility spike rather than a default choice. Bootstrap 3-era Sass patterns, deprecated @import usage, and modern Sass compilers can produce warnings or build failures. For new Laravel Vite projects, prefer a maintained Bootstrap release instead.
- Which Bootstrap versions does bootstrap-sass support?
- It ships Sass source for Bootstrap 2 and Bootstrap 3-era releases, with the last release around 2019. Bootstrap 2 and Bootstrap 3 differ significantly in markup and plugin behavior, so pin the exact version you need. Do not assume compatibility across major Bootstrap versions.
- How do I customize Bootstrap variables with bootstrap-sass?
- Override Sass variables before importing the Bootstrap entry point, using a dedicated overrides layer rather than editing vendor files. This lets you theme variables, mixins, and components at compile time. Keep imports and overrides isolated so a future migration is easier to audit.
- Do I need jQuery for bootstrap-sass JavaScript?
- The Sass package itself provides styles, but Bootstrap 3 JavaScript components are separate and many require jQuery. If you need those components, load the matching JavaScript deliberately and document the jQuery coupling. Modern Bootstrap 5 removes the jQuery requirement, which is one reason to migrate.
- Is bootstrap-sass maintained and safe for production?
- It is effectively unmaintained and end-of-life, with no ongoing security or browser-compatibility updates. The MIT license is acceptable, but there is no upstream support to rely on. Freeze and vendor the dependency if retained, track vulnerabilities, and fund a migration path.
- What Laravel or PHP version does bootstrap-sass require?
- PHP and Laravel versions are largely irrelevant because the real compatibility surface is Node, the Sass compiler, the bundler, browser targets, and Bootstrap JavaScript. Expect friction with modern Dart Sass and Vite pipelines. Audit your asset toolchain before adopting it in any Laravel app.
- What should I use instead of bootstrap-sass in Laravel?
- For greenfield or actively developed Laravel applications, use a maintained frontend stack such as Bootstrap 5 via npm and Vite, Tailwind, or another supported design system. If migrating, inventory Bootstrap 2/3 components, replace glyphicons with an icon library, remove jQuery-dependent plugins, and update markup incrementally.
- How should I test a legacy bootstrap-sass integration in CI?
- Pin an exact version, commit the lockfile or vendor the assets, and compile the stylesheet in CI to catch Sass and bundler failures. Add visual regression coverage for key Blade templates and record any compiler warnings. Also document the deprecation decision and the planned migration path.
Weaver
How can I help you explore Laravel packages today?