Been a while, sorry!

Is there a reason this hasn't been merged?

Ah, good to hear from you. I reverted this PR because:

• A user reported a fatal error
• Requires at least PHP 8.1, and I'm not sure if every user is up to that standard
• It's heavy and increases the zipped file size from current 1.0.1 MB to 1.6 MB

So, i think we should ship this with Bootstrap 6.

• A user reported a fatal error

I haven't had issues with it in production for months.

• Requires at least PHP 8.1, and I'm not sure if every user is up to that standard

PHP 8.0 is already end of life. So if they use a hosting which don't support it, they should definitely move. WordPress also adds a big alert if your PHP version is out of date.

• It's heavy and increases the zipped file size from current 1.0.1 MB to 1.6 MB

I don't think that matters all that much, it still is quite small.

Agree with that. But we should do a 6.3.1 release first, this is ready, just waiting for WC 10.4 which should be released yesterday. After that we can merge that PR immediately, release it in 6.4 and inform users.

Do you agree with that and do you want to do the 6.3.1 release?

@pro-wow you have reported an issue with that here. Can you please check if this issue still exists?

@justinkruit I have tested it on several sites and have no issues, please merge if you agree.

Ouch, I also got a white screen using Mamp and PHP 8.2. I do not feel good to merge this now, let's do that in v7. scssphp v1 still works...

Ouch, I also got a white screen using Mamp and PHP 8.2.

Do you have a PHP error?

It's about the memory limit:

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 290816 bytes) in /Applications/MAMP/htdocs/wordpress/wp-content/themes/bootscore/inc/scssphp/scssphp/scssphp/src/Serializer/Serializer.php on line 47

Increased it and works fine now:

define('WP_MEMORY_LIMIT', '256M');
define('WP_MAX_MEMORY_LIMIT', '256M');

But i'm a bit afraid of how many sites will be affected on this.