@bsmldrs If they get used _anywhere_ they end up in the same bundle. Thinking we need to mess with next's defaults for #splitchunksplugin" target="_blank" rel="nofollow noopener">webpack.js.org/guides/code-sp….
Also don't want other teams needing to remember to write dynamic imports when consuming our core library :(
Webpack/NextJS experts. I have a tree shakeable npm lib used across our app. Some large components only get used on a few pages. Next still bundles them with the lib bundle. Since most pages don't them, they hurt perf. What's the magic to keep them out, only load on needed pages?
Spending some time today polishing up our example Next.js frontend and Laravel Sanctum authenticated API backend. Upgrading the frontend to Next.js 12.
Going to continue showing these some love this week and put some better documentation around them. ❤️
github.com/taylorotwell/n…
@brendt_gd@laravelphp@phpunit Hey Brent, did you manage to find a solution/workaround? Also running in to this with @laravelphp 7, @phpunit 8 and php 7.4. I know there are open issues. Just wondering if processIsolation and increasing memory limit are the only options.
Ready for another AirPods Pro giveaway? Got five pairs this time. Just RT and you're in! Giveaway open worldwide, winners will be picked on Monday. Good luck!
@themsaid A little late but still: out of the box support for creating GraphQL endpoints. Packages do exist, but still an integrated approach would be nice.