Skip to content

Latest commit

 

History

History
855 lines (580 loc) · 15.7 KB

CHANGELOG.md

File metadata and controls

855 lines (580 loc) · 15.7 KB
Raw

@pandacss/extractor

0.46.1

Patch Changes

0.46.0

Patch Changes

0.45.2

Patch Changes

0.45.1

Patch Changes

0.45.0

Patch Changes

0.44.0

Patch Changes

0.43.0

Patch Changes

0.42.0

Patch Changes

  • 19c3a2c: Minor changes to the format of the panda analyze --output coverage.json file

0.41.0

Patch Changes

  • 2750261: Fix an issue where spreading an identifier in a sva slots array would prevent expected CSS from being generated

    import { sva } from 'styled-system/css'
const parts = ['positioner', 'content']

const card = sva({
  slots: [...parts], // <- spreading here was causing the below CSS not to be generated, it's now fixed ✅
  base: {
    root: {
      p: '6',
    },
  },
})

0.40.1

Patch Changes

0.40.0

Patch Changes

0.39.2

Patch Changes

0.39.1

Patch Changes

0.39.0

Patch Changes

0.38.0

Patch Changes

0.37.2

Patch Changes

0.37.1

Patch Changes

0.37.0

Patch Changes

0.36.1

Patch Changes

0.36.0

Patch Changes

0.35.0

Patch Changes

0.34.3

Patch Changes

0.34.2

Patch Changes

  • 0bf09f2: Allow using namespaced imports

    import * as p from 'styled-system/patterns'
import * as recipes from 'styled-system/recipes'
import * as panda from 'styled-system/css'

// this will now be extracted
p.stack({ mt: '40px' })

recipes.cardStyle({ rounded: true })

panda.css({ color: 'red' })
panda.cva({ base: { color: 'blue' } })
panda.sva({ base: { root: { color: 'green' } } })

0.34.1

Patch Changes

0.34.0

Patch Changes

0.33.0

Patch Changes

0.32.1

Patch Changes

0.32.0

Patch Changes

  • 7e70b6b: Fix issue where 0 values doesn't get extracted when used in a condition
  • Updated dependencies [8cd8c19]

0.31.0

Patch Changes

0.30.2

Patch Changes

0.30.1

Patch Changes

0.30.0

Patch Changes

  • Updated dependencies [ab32d1d7]
  • Updated dependencies [49c760cd]

0.29.1

Patch Changes

0.29.0

Patch Changes

0.28.0

0.27.3

0.27.2

0.27.1

0.27.0

Minor Changes

  • 84304901: Improve performance, mostly for the CSS generation by removing a lot of postcss usage (and plugins).

    Public changes:

    • Introduce a new config.lightningcss option to use lightningcss (currently disabled by default) instead of postcss.
    • Add a new config.browserslist option to configure the browserslist used by lightningcss.
    • Add a --lightningcss flag to the panda and panda cssgen command to use lightningcss instead of postcss for this run.

    Internal changes:

    • markImportant fn from JS instead of walking through postcss AST nodes
    • use a fork of stitches stringify function instead of postcss-css-in-js to write the CSS string from a JS object
    • only compute once TokenDictionary properties
    • refactor serializeStyle to use the same code path as the rest of the pipeline with StyleEncoder / StyleDecoder and rename it to transformStyles to better convey what it does

0.26.2

0.26.1

0.26.0

0.25.0

0.24.2

0.24.1

0.24.0

0.23.0

0.22.1

0.22.0

0.21.0

Patch Changes

  • 1464460f: Fix static extraction issue when using JSX attributes (props) that are other JSX nodes

    While parsing over the AST Nodes, due to an optimization where we skipped retrieving the current JSX element and instead kept track of the latest one, the logic was flawed and did not extract other properties after encountering a JSX attribute that was another JSX node.

    const Component = () => {
  return (
    <>
      {/* ❌ this wasn't extracting ml="2" */}
      <Flex icon={<svg className="icon" />} ml="2" />

      {/* ✅ this was fine */}
      <Stack ml="4" icon={<div className="icon" />} />
    </>
  )
}

    Now both will be fine again.

0.20.1

0.20.0

0.19.0

0.18.3

0.18.2

0.18.1

0.18.0

Patch Changes

  • 336fd0b0: Perf: use raw if instead of ts-pattern in the extractor (hot path)

0.17.5

0.17.4

0.17.3

0.17.2

0.17.1

Patch Changes

  • a76b279e: Extract identifier values coming from an EnumDeclaration member

    Example:

    enum Color {
  Red = 'red.400',
  Blue = 'blue.400',
}

const className = css({ color: Color.Red, backgroundColor: Color['Blue'] })

0.17.0

0.16.0

0.15.5

0.15.4

Patch Changes

  • 3a04a927: Fix static extraction of the Array Syntax when used with runtime conditions

    Given a component like this:

    function App() {
  return <Box py={[2, verticallyCondensed ? 2 : 3, 4]} />
}

    the py value was incorrectly extracted like this:

     {
    "py": {
        "1": 2,
    },
},
{
    "py": {
        "1": 3,
    },
},

    which would then generate invalid CSS like:

    .paddingBlock\\\\:1_2 {
  1: 2px;
}

.paddingBlock\\\\:1_3 {
  1: 3px;
}

    it's now correctly transformed back to an array:

    {
  "py": {
-    "1": 2,
+   [
+       undefined,
+       2,
+   ]
  },
},
{
  "py": {
-    "1": 3,
+   [
+       undefined,
+       3,
+   ]
  },
},

    which will generate the correct CSS

    @media screen and (min-width: 40em) {
  .sm\\\\:py_2 {
    padding-block: var(--spacing-2);
  }

  .sm\\\\:py_3 {
    padding-block: var(--spacing-3);
  }
}

0.15.3

0.15.2

0.15.1

Patch Changes

  • c40ae1b9: feat(parser): extract {fn}.raw as an identity fn

    so this will now work:

    import { css } from 'styled-system/css'

const paragraphSpacingStyle = css.raw({
  '&:not(:first-child)': { marginBlockEnd: '1em' },
})

export const proseCss = css.raw({
  maxWidth: '800px',
  '& p': {
    '&:not(:first-child)': { marginBlockStart: '1em' },
  },
  '& h1': paragraphSpacingStyle,
  '& h2': paragraphSpacingStyle,
})

    & use ECMA preset for ts-evaluator: This means that no other globals than those that are defined in the ECMAScript spec such as Math, Promise, Object, etc, are available but it allows for some basic evaluation of expressions like this:

    import { cva } from '.panda/css'

const variants = () => {
  const spacingTokens = Object.entries({
    s: 'token(spacing.1)',
    m: 'token(spacing.2)',
    l: 'token(spacing.3)',
  })

  const spacingProps = {
    px: 'paddingX',
    py: 'paddingY',
  }

  // Generate variants programmatically
  return Object.entries(spacingProps)
    .map(([name, styleProp]) => {
      const variants = spacingTokens
        .map(([variant, token]) => ({ [variant]: { [styleProp]: token } }))
        .reduce((_agg, kv) => ({ ..._agg, ...kv }))

      return { [name]: variants }
    })
    .reduce((_agg, kv) => ({ ..._agg, ...kv }))
}

const baseStyle = cva({
  variants: variants(),
})

0.15.0

Patch Changes

  • be24d1a0: Fix issue (#1365) with the unbox fn that removed nullish values, which could be useful for the Array Syntax

    const className = css({
  color: ['black', undefined, 'orange', 'red'],
})

  • 7c1ab170: Fix issue where the satisfies would prevent an object from being extracted

0.14.0

0.13.1

0.13.0

0.12.2

0.12.1

0.12.0

0.11.1

0.11.0

0.10.0

0.9.0

Patch Changes

  • 3269b411: Fix extractor issue where we didn't explore both branches when using a default value as the condition expression

    In the example below, only the yellow color would be generated although the blue color should also be generated in case the disabled prop is true.

    const CompB = ({ disabled = false }: { disabled: boolean }) => {
  return <div className={css({ color: disabled ? 'blue' : 'yellow' })}>Component B is disabled</div>
}

0.8.0

Patch Changes

  • fb449016: Fix cases where Stitches styled.withConfig would be misinterpreted as a panda fn and lead to this error:

    TypeError: Cannot read properties of undefined (reading 'startsWith')
    at /panda/packages/shared/dist/index.js:433:16
    at get (/panda/packages/shared/dist/index.js:116:20)
    at Utility.setClassName (/panda/packages/core/dist/index.js:1682:66)
    at inner (/panda/packages/core/dist/index.js:1705:14)
    at Utility.getOrCreateClassName (/panda/packages/core/dist/index.js:1709:12)
    at AtomicRule.transform (/panda/packages/core/dist/index.js:1729:23)
    at /panda/packages/core/dist/index.js:323:32
    at inner (/panda/packages/shared/dist/index.js:219:12)
    at walkObject (/panda/packages/shared/dist/index.js:221:10)
    at AtomicRule.process (/panda/packages/core/dist/index.js:317:35)

  • 78612d7f: Fix node evaluation in extractor process (can happen when using a BinaryExpression, simple CallExpression or conditions)

0.7.0

Patch Changes

  • f2abf34d: Fix extractor behaviour when encoutering operation tokens, try to evaluate them instead of resolving them as string

    before:

    <AspectRatio ratio={1 / 2} asterisk={1 * 5} exp={1 ** 4} minus={5 - 1} />

    would be extracted to:

    {
  "asterisk": "1 *5",
  "exp": "1**4",
  "minus": "5 -1",
  "ratio": "1 / 2"
}

    now, it will be extracted to the actual values:

    {
  "asterisk": 5,
  "exp": 1,
  "minus": 4,
  "ratio": 0.5
}

  • 7bc69e4b: Fix issue where extraction does not work when the spread syntax is used or prop contains string that ends with ':'

0.6.0

Patch Changes

  • 21295f2e: Resolve identifier default value from parameter, code like position and inset here:

    export const Positioned: React.FC<PositionedProps> = ({ children, position = 'absolute', inset = 0, ...rest }) => (
  <styled.div position={position} inset={inset} {...rest}>
    {children}
  </styled.div>
)

0.5.1

Patch Changes

  • 6f03ead3: Fix issue where operation tokens did not get extracted.

    This means that values such as 1 / 2, 3*5, 2 **4, 8- 1 will now properly be extracted

  • e48b130a: - Remove stack from box.toJSON() so that generated JSON files have less noise, mostly useful to get make the panda debug command easier to read

    • Also use the ParserResult.toJSON() method on panda debug command for the same reason

    instead of:

    [
  {
    "type": "map",
    "value": {
      "padding": {
        "type": "literal",
        "value": "25px",
        "node": "StringLiteral",
        "stack": [
          "CallExpression",
          "ObjectLiteralExpression",
          "PropertyAssignment",
          "Identifier",
          "Identifier",
          "VariableDeclaration",
          "StringLiteral"
        ],
        "line": 10,
        "column": 20
      },
      "fontSize": {
        "type": "literal",
        "value": "2xl",
        "node": "StringLiteral",
        "stack": [
          "CallExpression",
          "ObjectLiteralExpression",
          "PropertyAssignment",
          "ConditionalExpression"
        ],
        "line": 11,
        "column": 67
      }
    },
    "node": "CallExpression",
    "stack": [
      "CallExpression",
      "ObjectLiteralExpression"
    ],
    "line": 11,
    "column": 21
  },

    we now have:

    {
  "css": [
    {
      "type": "object",
      "name": "css",
      "box": {
        "type": "map",
        "value": {},
        "node": "CallExpression",
        "line": 15,
        "column": 27
      },
      "data": [
        {
          "alignItems": "center",
          "backgroundColor": "white",
          "border": "1px solid black",
          "borderRadius": "8px",
          "display": "flex",
          "gap": "16px",
          "p": "8px",
          "pr": "16px"
        }
      ]
    }
  ],
  "cva": [],
  "recipe": {
    "checkboxRoot": [
      {
        "type": "recipe",
        "name": "checkboxRoot",
        "box": {
          "type": "map",
          "value": {},
          "node": "CallExpression",
          "line": 38,
          "column": 47
        },
        "data": [
          {}
        ]
      }
    ],

  • d9bc63e7: Fix ShorthandPropertyAssignment handling on root objects, it was only handled when accessing an object from a prop acces / element access

    this was fine:

    const aliased = 'green.600'
const colorMap = { aliased }
const className = css({ color: colorMap['aliased'] })

    this was not (weirdly):

    const color = 'green.600'
const className = css({ color })

  • Updated dependencies [f9247e52]

0.5.0

Minor Changes

  • ead9eaa3: Add support for tagged template literal version.

    This features is pure css approach to writing styles, and can be a great way to migrate from styled-components and emotion.

    Set the syntax option to template-literal in the panda config to enable this feature.

    // panda.config.ts
export default defineConfig({
  //...
  syntax: 'template-literal',
})

    For existing projects, you might need to run the panda codegen --clean

    You can also use the --syntax option to specify the syntax type when using the CLI.

    panda init -p --syntax template-literal

    To get autocomplete for token variables, consider using the CSS Var Autocomplete extension.

Patch Changes

0.4.0

Patch Changes

0.3.2

Patch Changes

0.3.1

Patch Changes

  • efd79d83: Baseline release for the launch
  • Updated dependencies [efd79d83]

0.3.0

Patch Changes

0.0.2

Patch Changes

  • fb40fff2: Initial release of all packages

    • Internal AST parser for TS and TSX
    • Support for defining presets in config
    • Support for design tokens (core and semantic)
    • Add outExtension key to config to allow file extension options for generated javascript. .js or .mjs
    • Add jsxElement option to patterns, to allow specifying the jsx element rendered by the patterns.

  • Updated dependencies [fb40fff2]