From 730f0f591491e99ccb3e8bb5558842d6488341f0 Mon Sep 17 00:00:00 2001 From: suu3 Date: Tue, 4 Jun 2024 17:28:26 +0900 Subject: [PATCH] docs: fix a incorrect link --- website/pages/docs/guides/component-library.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/pages/docs/guides/component-library.md b/website/pages/docs/guides/component-library.md index 2e69cd79b..b27e8f22c 100644 --- a/website/pages/docs/guides/component-library.md +++ b/website/pages/docs/guides/component-library.md @@ -133,7 +133,7 @@ This approach comes with a few downsides: ### Summary -- create a Panda [preset](docs/customization/presets) so that you (and your users) can share the same design system tokens +- create a Panda [preset](/docs/customization/presets) so that you (and your users) can share the same design system tokens - create a workspace package for your outdir (`@acme-org/styled-system`) and use that package name as the `importMap` in your app code - have your component library (`@acme-org/components`) use the `@acme-org/styled-system` package as external @@ -144,7 +144,7 @@ Let's make a dedicated workspace package for your `outdir`: 1. Create a new directory `packages/styled-system` (or any other name) 2. Install `@pandacss/dev` as a dev dependency 3. Run the `panda init` command in there to generate a `panda.config.ts` file, don't forget to set the `jsxFramework` if needed -4. [optional] you might want to install and import your [preset](docs/customization/presets) in this `panda.config.ts` file as well +4. [optional] you might want to install and import your [preset](/docs/customization/presets) in this `panda.config.ts` file as well 5. Run the [`panda emit-pkg`](/docs/references/cli#emit-pkg) command to set the entrypoints in [`exports`](https://nodejs.org/api/packages.html#exports) This should look similar to this: