FLUID-5918: Provide source maps for CSS generated from Stylus

Metadata

Source
FLUID-5918
Type
Improvement
Priority
Major
Status
Closed
Resolution
Won't Fix
Assignee
N/A
Reporter
Justin Obara
Created
2016-06-16T14:15:27.334-0400
Updated
2021-03-23T12:49:51.220-0400
Versions
N/A
Fixed Versions
  1. 3.0
Component
  1. Build Scripts

Description

Some of our CSS, in particular the styles for the preferences framework, are generated using Stylus. These files are compiled into proper CSS files which are used by preference editors. However, there is no mapping between the two when debugging the styles in the browser. We should look into providing source maps for the stylus files.

see: http://stylus-lang.com/docs/sourcemaps.html

Comments

  • Justin Obara commented 2016-06-16T14:17:43.591-0400

    We are currently using the "grunt-contrib-stylus" grunt plugin for compiling Styl files to css. However, this plugin does not explicitly support source maps. It is possible to get it to generate inline source maps, but this causes the css file size to double. A more appropriate method would be to create distinct map files.

    https://github.com/gruntjs/grunt-contrib-stylus/issues/118#issuecomment-98195500

  • Justin Obara commented 2021-03-23T12:49:51.214-0400

    As part of the work on FLUID-6496 the CSS Preprocessing in Infusion was migrated to Sass