snaplet-sass alternatives and similar packages
Based on the "snaplet" category.
Alternatively, view snaplet-sass alternatives based on common mentions on social networks and blogs.
-
snaplet-postgresql-simple
postgresql-simple snaplet for the Snap Framework -
snaplet-persistent
Snaplet for using Persistent in snap applications -
snaplet-actionlog
Create a change log/history for records in your snap application -
snaplet-sqlite-simple
sqlite-simple snaplet for the Snap Framework -
snaplet-mysql-simple
A haskell snaplet for using MariaDB and MySQL database with a Snap Framework application via mysql-simple -
snaplet-auth-acid
An AcidState backend for Snap's Auth Snaplet -
snaplet-postmark
Haskell Snap Framework support for Postmark email system. -
snaplet-coffee
A Haskell Snaplet based off of snaplet-fay, but for coffeescript -
snaplet-haxl
Snaplet for Haxl: https://github.com/facebook/Haxl
Learn any GitHub repo in 59 seconds
Do you think we are missing an alternative of snaplet-sass or a related project?
README
snaplet-sass
[Changelog](CHANGELOG.md)
snaplet-sass integrates Snap with Sass.
Features
- Compile and serve sass files on request, no need to restart the snap server.
- Production mode to pre-compile all sass files.
- Outputs sourcemaps to make debugging generated CSS easier.
- Writes CSS to disk to allow reading the generated source.
Example Usage
Site.hs:
import Snap.Snaplet.Sass
routes = [..., ("/sass", with sass sassServe)]
app :: SnapletInit App App
app = makeSnaplet "app" "A snaplet example application." Nothing $ do
s <- nestSnaplet "sass" sass initSass
return $ App { _sass = s }
Application.hs:
import Snap.Snaplet.Sass
data App = App { _sass :: Snaplet Sass }
makeLens ''App
Now run your application and try requesting a Sass file.
A snaplet config file will be generated at snaplets/sass/devel.cfg the first time your application initializes the snaplet. The defaults are the recommended ones for development.
Place your .sass or .scss files in snaplets/sass/src. Note that a default devel.cfg will not be created if you have already created the sass directory. If this happens to you, move snaplets/sass, start your application, and then move the files back into snaplets/sass.
Any requests to the specified directory (in this case /sass/) will compile the appropriate Sass file and serve it.
Thanks
This borrows hugely from snaplet-fay.