Materialize Bridge Docs
v1
v1
  • Intro
  • 1. About this application
    • 1.1 Introduction
    • 1.2 Navigation guide
    • 1.3 Components catalog
    • 1.4 Internal Structure
    • 1.5 Installation
    • 1.6 Project status
    • 1.7 Color switcher
  • 2. Installation
    • Webpack, Aurelia-CLI (Webpack)
    • JSPM
    • Aurelia-CLI (require)
    • Fuse-box 2.x
  • 3. App developers tutorial
    • 3.1 Introduction
    • 3.2 Setup
    • 3.3 Select component
    • 3.4 Button component
    • 3.5 Slider component
    • 3.6 Collapsible component
    • 3.7 What you need to know
  • 4. App developers notes
    • 4.1 On bundling
    • 4.2 Using your own SASS with JSPM
  • 5. Contributing (bridge developers notes)
    • Cloning and running the code
    • Creating samples
  • 6. About Aurelia
    • 5.1 Key Features
  • 7. About Materialize
    • 7.1 Integrated with Aurelia
    • 7.2 Why choose Materialize
Powered by GitBook
On this page
  1. 4. App developers notes

4.2 Using your own SASS with JSPM

A lot of people change Materialize sass files to match their own preferences. If you're doing that, you'll have to make sure that your changed styles are loaded instead of the original ones.

When using JSPM you can make use of a feature names overrides to do this:

System.config({
...
  packages: {
    "materialize-css": {
      main: "dist/js/materialize.js",
      map: {
        '../css/materialize.css': 'my path'
      }
    }
  }
...
});
Previous4.1 On bundlingNext5. Contributing (bridge developers notes)

Last updated 7 years ago