Joshua Fredrickson
Joshua Fredrickson
I've been thinking on this for a minute, and you're right. Probably the best path forward is to take a serious look into updating the v1 sites at some point....
I'm running into this when using a callback with `themeJson`: `bud.config.js`: ```js .themeJson((theme) => { theme.set("typography.customFontSize", true); return theme; }) ``` This nests a duplicate `settings` object inside `settings >...
I've added this into a new site build and in my limited time with it so far, I agree this is in a place where it's working as expected. 👍
It looks like this is caused by `postcss-loader@^4.0.4`. The quick fix is to downgrade `autoprefixer` and `postcss-loader` like so: ```bash yarn add autoprefixer@^9.8.6 -D yarn add postcss-loader@~3.0.0 -D ```
This is fixed in 0.7.
This is fixed in 0.7.
#186 fixes this issue if you're in a pinch.
@chasecee is correct. JSX doesn't work out of the box. I was able to get it working by using the `block-params` filter like so: ```php add_filter('micropackage/block-loader/block-params', function ($params) { if...
This is also applies to Laravel 11. Are there plans to update this package to a supported version of Laravel now that 9 is officially EOL?
We have an L9 project in the same boat... looking to step it up to L11 in the coming year, still in the planning stages. If the timing works out...