| 1 |
Source: libplack-middleware-file-sass-perl |
| 2 |
Section: perl |
| 3 |
Priority: optional |
| 4 |
Build-Depends: |
| 5 |
debhelper-compat (= 13), |
| 6 |
libmodule-package-perl, |
| 7 |
libplack-perl, |
| 8 |
libtest-requires-perl, |
| 9 |
libtext-sass-perl |
| 10 |
Maintainer: Debian Perl Group <[email protected]> |
| 11 |
Uploaders: Jonas Smedegaard <[email protected]> |
| 12 |
Standards-Version: 4.7.2 |
| 13 |
Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libplack-middleware-file-sass-perl.git |
| 14 |
Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libplack-middleware-file-sass-perl |
| 15 |
Homepage: https://metacpan.org/release/Plack-Middleware-File-Sass |
| 16 |
Testsuite: autopkgtest-pkg-perl |
| 17 |
|
| 18 |
Package: libplack-middleware-file-sass-perl |
| 19 |
Architecture: all |
| 20 |
Depends: |
| 21 |
libplack-perl, |
| 22 |
ruby-sass | libhaml-ruby (<< 3.1) | libtext-sass-perl, |
| 23 |
${perl:Depends}, |
| 24 |
${misc:Depends}, |
| 25 |
Recommends: |
| 26 |
ruby-sass | libhaml-ruby (<< 3.1), |
| 27 |
Description: Sass and SCSS support for all Plack-based PSGI frameworks |
| 28 |
PSGI is a specification to decouple web server environments from web |
| 29 |
application framework code. Plack is an implementation of PSGI. |
| 30 |
. |
| 31 |
Plack::Middleware::File::Sass is a Plack middleware component that |
| 32 |
works with Plack::App::File or Plack::Middleware::Static to compile |
| 33 |
Sass templates into CSS stylesheet in every request. |
| 34 |
. |
| 35 |
When a request comes in for *.css* file, this middleware changes the |
| 36 |
internal path to *.sass* or *.scss*, depending on the configuration, in |
| 37 |
the same directory. If the Sass template is found, a new CSS stylesheet |
| 38 |
is built on memory and served to the browsers. Otherwise, it falls back |
| 39 |
to the original *.css* file in the directory. |
| 40 |
. |
| 41 |
This middleware should be very handy for the development. While Sass to |
| 42 |
CSS rendering is reasonably fast, for the production environment you |
| 43 |
might want to precompile Sass templates to CSS files on disk and serves |
| 44 |
them with a real web server like nginx or lighttpd. |
| 45 |
. |
| 46 |
Text::Sass provides only a limited Sass implementation, so the Ruby |
| 47 |
implementation is recommended even when Text::Sass is available. |