Download the PHP package ikkez/f3-assets-sass without Composer
On this page you can find all versions of the php package ikkez/f3-assets-sass. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package f3-assets-sass
SASS addon for F3 Sugar Assets
This is an extention to add a SASS/SCSS compiler to the existing Assets Management plugin for the PHP Fat-Free Framework.
Install
When you have F3-Assets already up and running, just run composer require ikkez/f3-assets-sass.
In case you do not use composer, copy the assets/ folder into your AUTOLOAD path, install scssphp/scssphp separately and you should be ready to go.
Usage
To register the sass compiler, just add this line to your view controller, or where ever you have put the initialisation of the main assets plugin.
Within your templates you can then easily use .scss files directly, as it would be normal css files.
That's it. Compilation, minification and concatenation with other files is now handled by the assets plugin.
The base directory of the sass file can also be used as import path,
so using @import within your sass file can be used to load other relative sass files. So recompiling a whole bootstrap frontend is not problem:
The only drawback with @include files is, that changes to those files are currently not detected automatically,
so the whole main sass file does not update on the fly. However, you can add the watch attribute and define
one or multiple paths to scan for file changes - wildcards are possible:
NB: The watch-attribute should only be considered while working on the files, because scanning for file modification times isn't necessary for production-ready styles and would, depending on the amount of files to scan, slow things down.
If you need to refresh files on a production environment, it's recommended to clear the temp files with \Assets::instance()->clear();, instead of proactive looking for changes.
If you like to add sass files programmatically, you should simply treat them like normal css files:
``
License
GPLv3
