perf!: client / server subpaths

[harlan-zw]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

To ensure that client and server code is properly treeshaken, we now use subpath exports to differentiate the two ways of using Unhead.

import { createHead } from 'unhead/client'

// avoids bundling server plugins
createHead()

This is a breaking change if you were relying on any of the following:

• createServerHead() (is replaced by createHead() from unhead/server
• createHead() (imported from unhead), now imported from unhead/client

With this change we also soft deprecate @unhead/ssr and @unhead/dom as the same functionality is now exported by the associated subpath export.

⚠️ Updated import paths

🚦 Impact Level: Critical

The path where you import createHead from has been updated to be a subpath export. If you're not using Unhead through a framework (such as Nuxt), then this will be a breaking change.

📜 Migration Guide

ℹ️ Import your createHead's from unhead/legacy and you'll get the same v1 behavior.

Please follow the updated installation instructions or simply update the import to use the subpath.

Client bundle:

import { createHead } from 'unhead/client'

// avoids bundling server plugins
createHead()

Server bundle:

import { createHead } from 'unhead/server'

// avoids bundling server plugins
createHead()