-
-
Notifications
You must be signed in to change notification settings - Fork 220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: use nextjs experimental externalDir #265
Conversation
🦋 Changeset detectedLatest commit: e321b8c The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This pull request is being automatically deployed with Vercel (learn more). nextjs-monorepo-example-blog-app – ./apps/blog-app🔍 Inspect: https://vercel.com/belgattitude/nextjs-monorepo-example-blog-app/35gv5tEMWW2ZxsEN2KD8JrhDUqK8 nextjs-monorepo-example-web-app – ./apps/web-app🔍 Inspect: https://vercel.com/belgattitude/nextjs-monorepo-example-web-app/8ctNB46bupJfQxz5ZoWR8Dgt4zRo |
Code Climate has analyzed commit e321b8c and detected 0 issues on this pull request. View more on Code Climate. |
Purpose
Trying out recent externalDir offered by NextJs: vercel/next.js#22867. It works perfect even supporting svg and offer comparable speed.
Benchmarks
With experimental/externalDirs
**FIRST BUILD: 22 seconds **:
(mean ± σ): 9 seconds:
With previous implementation (webpack)
Example of next.config.js overrides
**FIRST BUILD: 22 seconds **:
(mean ± σ): 9 seconds: