Version Packages (next)

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

main is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on main.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

astro@0.19.0-next.3

Minor Changes

• 1971ab3: Adds support for client:only hydrator

  The new client:only hydrator allows you to define a component that should be skipped during the build and only hydrated in the browser.

  In most cases it is best to render placeholder content during the build, but that may not always be feasible if an NPM dependency attempts to use browser APIs as soon as is imported.

  Note If more than one renderer is included in your Astro config, you need to include a hint to determine which renderer to use. Renderers will be matched to the name provided in your Astro config, similar to <MyComponent client:only="@astrojs/renderer-react" />. Shorthand can be used for @astrojs renderers, i.e. <MyComponent client:only="react" /> will use @astrojs/renderer-react.

  An example usage:

  ---
  import BarChart from '../components/BarChart.jsx';
  ---
  
  <BarChart client:only />
  /**
   * If multiple renderers are included in the Astro config,
   * this will ensure that the component is hydrated with
   * the Preact renderer.
   */
  <BarChart client:only="preact" />
  /**
   * If a custom renderer is required, use the same name
   * provided in the Astro config.
   */
  <BarChart client:only="my-custom-renderer" />

  This allows you to import a chart component dependent on d3.js while making sure that the component isn't rendered at all at build time.

Patch Changes

• 1f13e40: Fix CSS scoping issue

• 78b5bde: Adds support for Astro.resolve

  Astro.resolve() helps with creating URLs relative to the current Astro file, allowing you to reference files within your src/ folder.

  Astro does not resolve relative links within HTML, such as images:

  <img src="../images/penguin.png" />

  The above will be sent to the browser as-is and the browser will resolve it relative to the current page. If you want it to be resolved relative to the .astro file you are working in, use Astro.resolve:

  <img src={Astro.resolve('../images/penguin.png')} />

docs@0.0.5-next.0

Patch Changes

• 78b5bde: Adds support for Astro.resolve

  Astro.resolve() helps with creating URLs relative to the current Astro file, allowing you to reference files within your src/ folder.

  Astro does not resolve relative links within HTML, such as images:

  <img src="../images/penguin.png" />

  The above will be sent to the browser as-is and the browser will resolve it relative to the current page. If you want it to be resolved relative to the .astro file you are working in, use Astro.resolve:

  <img src={Astro.resolve('../images/penguin.png')} />

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployments, click below or on the icon next to each commit.

astro-docs – ./docs

🔍 Inspect: https://vercel.com/pikapkg/astro-docs/JAv1P8BqrXrysYGWUnDc7YMok7XC
✅ Preview: https://astro-docs-git-changeset-release-main-pikapkg.vercel.app

astro-www – ./www

🔍 Inspect: https://vercel.com/pikapkg/astro-www/4Uf8FsBTccWRiVCaC9VfYfDynKsP
✅ Preview: Canceled

[Deployment for f7ec0c9 canceled]