@pandacss/types - npm Package Compare versions

dist/config.d.ts

		@@ -315,7 +315,2 @@ import type { TSConfig } from 'pkg-types'
		/**
		* Whether to optimize the generated css.
		* @default true
		*/
		optimize?: boolean
		/**
		* Whether to minify the generated css.
		@@ -360,18 +355,2 @@ * @default false
		/**
		* Whether to emit the artifacts to `node_modules` as a package.
		* @default false
		* @deprecated `emitPackage` is deprecated, it's known for causing several issues:
		* - bundlers sometimes eagerly cache the `node_modules`, leading to `panda codegen` updates to the `styled-system` not visible in the browser
		* - auto-imports are not suggested in your IDE.
		* - in some IDE the typings are not always reflected properly
		*
		* As alternatives, you can use:
		* - relative paths instead of absolute paths (e.g. `../styled-system/css` instead of `styled-system/css`)
		* - use package.json #imports and/or tsconfig path aliases (prefer package.json#imports when possible, TS 5.4 supports them by default) like `#styled-system/css` instead of `styled-system/css`
		* @see https://nodejs.org/api/packages.html#subpath-imports
		* - for a component library, use a dedicated workspace package (e.g. `@acme/styled-system`) and use `importMap: "@acme/styled-system"` so that Panda knows which entrypoint to extract, e.g. `import { css } from '@acme/styled-system/css'`
		* @see https://panda-css.com/docs/guides/component-library
		*/
		emitPackage?: boolean
		/**
		* Whether to only emit the `tokens` directory
		@@ -378,0 +357,0 @@ * @default false

package.json

		{
		"name": "@pandacss/types",
		"version": "0.0.0-dev-20240624212930",
		"version": "0.0.0-dev-20240627180503",
		"description": "The types for css panda",
		@@ -34,3 +34,3 @@ "main": "dist/index.d.ts",
		"ts-morph": "21.0.1",
		"@pandacss/extractor": "0.0.0-dev-20240624212930"
		"@pandacss/extractor": "0.0.0-dev-20240627180503"
		},
		@@ -37,0 +37,0 @@ "scripts": {

Worsened metrics