Bump @pandacss/dev from 0.23.0 to 0.28.0

Bumps @pandacss/dev from 0.23.0 to 0.28.0.

Release notes

Sourced from @pandacss/dev's releases.

@pandacss/dev@0.28.0

Minor Changes
f58f6df2: Refactor config.hooks to be much more powerful, you can now:

Tweak the config after it has been resolved (after presets are loaded and merged), this could be used to dynamically load all recipes from a folder

Transform a source file's content before parsing it, this could be used to transform the file content to a tsx-friendly syntax so that Panda's parser can parse it.

Implement your own parser logic and add the extracted results to the classic Panda pipeline, this could be used to parse style usage from any template language

Tweak the CSS content for any @layer or even right before it's written to disk (if using the CLI) or injected through the postcss plugin, allowing all kinds of customizations like removing the unused CSS variables, etc.

React to any config change or after the codegen step (your outdir, the styled-system folder) have been generated

See the list of available config.hooks here:
export interface PandaHooks {
  /**
   * Called when the config is resolved, after all the presets are loaded and merged.
   * This is the first hook called, you can use it to tweak the config before the context is created.
   */
  'config:resolved': (args: { conf: LoadConfigResult }) => MaybeAsyncReturn
  /**
   * Called when the Panda context has been created and the API is ready to be used.
   */
  'context:created': (args: { ctx: ApiInterface; logger: LoggerInterface }) => void
  /**
   * Called when the config file or one of its dependencies (imports) has changed.
   */
  'config:change': (args: { config: UserConfig }) => MaybeAsyncReturn
  /**
   * Called after reading the file content but before parsing it.
   * You can use this hook to transform the file content to a tsx-friendly syntax so that Panda's parser can parse it.
   * You can also use this hook to parse the file's content on your side using a custom parser, in this case you don't have to return anything.
   */
  'parser:before': (args: { filePath: string; content: string }) => string | void
  /**
   * Called after the file styles are extracted and processed into the resulting ParserResult object.
   * You can also use this hook to add your own extraction results from your custom parser to the ParserResult object.
   */
  'parser:after': (args: { filePath: string; result: ParserResultInterface | undefined }) => void
  /**
   * Called after the codegen is completed
   */
  'codegen:done': () => MaybeAsyncReturn
  /**
   * Called right before adding the design-system CSS (global, static, preflight, tokens, keyframes) to the final CSS
   * Called right before writing/injecting the final CSS (styles.css) that contains the design-system CSS and the parser CSS

... (truncated)

Changelog

Sourced from @pandacss/dev's changelog.

0.28.0

Minor Changes
f58f6df2: Refactor config.hooks to be much more powerful, you can now:

Tweak the config after it has been resolved (after presets are loaded and merged), this could be used to dynamically load all recipes from a folder

Transform a source file's content before parsing it, this could be used to transform the file content to a tsx-friendly syntax so that Panda's parser can parse it.

Implement your own parser logic and add the extracted results to the classic Panda pipeline, this could be used to parse style usage from any template language

Tweak the CSS content for any @layer or even right before it's written to disk (if using the CLI) or injected through the postcss plugin, allowing all kinds of customizations like removing the unused CSS variables, etc.

React to any config change or after the codegen step (your outdir, the styled-system folder) have been generated

See the list of available config.hooks here:
export interface PandaHooks {
  /**
   * Called when the config is resolved, after all the presets are loaded and merged.
   * This is the first hook called, you can use it to tweak the config before the context is created.
   */
  'config:resolved': (args: { conf: LoadConfigResult }) => MaybeAsyncReturn
  /**
   * Called when the Panda context has been created and the API is ready to be used.
   */
  'context:created': (args: { ctx: ApiInterface; logger: LoggerInterface }) => void
  /**
   * Called when the config file or one of its dependencies (imports) has changed.
   */
  'config:change': (args: { config: UserConfig }) => MaybeAsyncReturn
  /**
   * Called after reading the file content but before parsing it.
   * You can use this hook to transform the file content to a tsx-friendly syntax so that Panda's parser can parse it.
   * You can also use this hook to parse the file's content on your side using a custom parser, in this case you don't have to return anything.
   */
  'parser:before': (args: { filePath: string; content: string }) => string | void
  /**
   * Called after the file styles are extracted and processed into the resulting ParserResult object.
   * You can also use this hook to add your own extraction results from your custom parser to the ParserResult object.
   */
  'parser:after': (args: { filePath: string; result: ParserResultInterface | undefined }) => void
  /**
   * Called after the codegen is completed
   */
  'codegen:done': () => MaybeAsyncReturn
  /**
   * Called right before adding the design-system CSS (global, static, preflight, tokens, keyframes) to the final CSS

... (truncated)

Commits

02b0c48 Version Packages (#2037)
f58f6df refactor(hooks): rm hookable, use raw object + callbacks (#1969)
9ea9e92 docs: update component library to use importMap (#2052)
f255342 feat(cli): add --cpu-prof flag (#2046)
e54028c Version Packages (#2023)
13eb351 Version Packages (#2015)
bfa8b1e refactor: replace pathe with node:path (#2012)
fcca63d Version Packages (#2009)
fee015f chore(deps): update dependency pathe to v1.1.2 (#2004)
2e09e19 Version Packages (#1993)
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

jiftechnify / nostatus

Bump @pandacss/dev from 0.23.0 to 0.28.0 #103

`@pandacss/dev@0`.28.0

Minor Changes

0.28.0

Minor Changes

jiftechnify / nostatus

Bump @pandacss/dev from 0.23.0 to 0.28.0 #103

@​pandacss/dev@​0.28.0

Minor Changes

0.28.0

Minor Changes

`@pandacss/dev@0`.28.0