Add support for using SCSS style files with wp_enqueue_style.
| Author: | Juan Sebastián Echeverry (profile at wordpress.org) |
| WordPress version required: | 6.0 |
| WordPress version tested: | 6.1.1 |
| Plugin version: | 0.4.1 |
| Added to WordPress repository: | 29-08-2019 |
| Last updated: | 24-01-2023 |
| Rating, %: | 100 |
| Rated by: | 5 |
| Plugin URI: | |
| Total downloads: | 8 318 |
| Active installs: | 1 000+ |
Click to start download
|
This plugin allows you to use SCSS files directly in wp_enqueue_style. Just add the file to the list of styles and the plugin will compile it when necessary.
The base of this plugin is strongly influenced by the WP-SCSS code and extracts some ideas from Sassify. The goal is to keep the plugin updated with the latest version of scssphp, remove configuration options from the graphical interface, and use the scssphp capabilities to create debug files.
This plugin is not intended to be installed by a conventional user, but to be required by templates or plugins that wish to include SCSS style files and therefore the configuration is expected to be done in the code.
FAQ
Performance
This plugin adds many extra steps for something as simple as printing a style link tag inside a site:
- Check the creation time of the compiled file.
- Interacts with the database.
- Converts a SCSS file into a style file.
Obviously it will add a few millisecond to the loading time of the site.
How much will performance be affected?
It depends on how many SCSS files you add to the list of styles and how complex they are.
So I shouldn’t use it in production?
Of course you can use it. If you are looking for a fast site then you should also add a cache or optimization plugin to your production environment, although it is very likely that you have already done so. Personally I have worked with Comet Cache and Autoptimize without any inconvenience. Any problems you encounter with another cache plugin don’t hesitate to write down the details to replicate the error. Remember that the more information you include in the report the easier it will be to fix it.
Then what are you looking for with this plugin?
What I want is to emulate for the style files the ease of development offered by Timber. Let SCSS-Library be to SCSS what Timber is to Twig.
My goal with this plugin is to be able to change the SCSS file directly and see the result immediately. No previous compilations or commands in a terminal. It is intended for development teams that include graphic designers who understand CSS and HTML but prefer not to have to open a terminal; and to support lazy programmers who like me prefer to leave repetitive tasks to the machines.
Is this plugin bug free?
I don’t think so. Feedbacks would be appreciated.
ChangeLog
0.4.1
0.4.0
- Refactoring to have a code easier to test.
0.3.2
- By default the plugin creates minified code.
- Maps and extended code are created when in dev mode.
- Refactoring the code to simplify the compilation manager and the error viewer.
0.3.1
- Added german translation
- Translation of comments in code to english.
0.3.0
- Update scssphp to 1.11.0.
- Code refactoring to simplify code testing and maintenance.
0.2.7
0.2.6
0.2
- Feature: develop environment options.
0.1.6
0.1.5
0.1.4
- Testing: Test environment added.
0.1.3
- Bug fixed: Autoptimize does not aggregate compiled files.
0.1.2
- Create compiled file if the file does not exist.
- Bug fixed: new version number in the wp_enqueue_style declaration recreates build file with a new name.
0.1.1
- Bug fixed: multisite pages lost the path to the compiled files.
0.1
