css, integration: Replace outdent dependency with dedent

[askoufis]

Really the only reason to move is that dedent seems much more actively maintained than outdent.

[changeset-bot]

🦋 Changeset detected

Latest commit: 456545b

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 19 packages

Name	Type
@vanilla-extract/integration	Patch
@vanilla-extract/css	Patch
@vanilla-extract-private/tests	Patch
@fixtures/features	Patch
@fixtures/layers	Patch
@fixtures/low-level	Patch
@fixtures/next-app-router	Patch
@fixtures/next-pages-router	Patch
@fixtures/recipes	Patch
@fixtures/sprinkles	Patch
@fixtures/template-string-paths	Patch
@fixtures/themed	Patch
@fixtures/thirdparty	Patch
@fixtures/unused-modules	Patch
@fixtures/thirdparty-dep	Patch
@fixtures/thirdparty-dep-dep	Patch
vanilla-extract-example-remix	Patch
vanilla-extract-example-webpack-react	Patch
@vanilla-extract-private/test-helpers	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[SimenB]

I think this change broke something in how dedenting works when passing a multiline string in @vanilla-extract/css.

import { createGlobalTheme } from "@vanilla-extract/css";

const vars = createGlobalTheme(":root", {
  focusWithin: {
    highlightBoxShadow: `
      0px 0px 0px 4px #DEEFFF
    `,
  },
});

This works fine in 1.15.0, but with 1.15.1 the backticks are turned into ", which is a syntax error.

It might not be the change in this PR, but it who knows 🙂 It broke in the patch release this PR was included in at least

[askoufis]

I think this change broke something in how dedenting works when passing a multiline string in @vanilla-extract/css.

import { createGlobalTheme } from "@vanilla-extract/css";

const vars = createGlobalTheme(":root", {
  focusWithin: {
    highlightBoxShadow: `
      0px 0px 0px 4px #DEEFFF
    `,
  },
});

This works fine in 1.15.0, but with 1.15.1 the backticks are turned into ", which is a syntax error.

It might not be the change in this PR, but it who knows 🙂 It broke in the patch release this PR was included in at least

I can't seem to reproduce this. This is the CSS that I'm seeing generated. It looks a bit weird, but is otherwise completely functional:

If you find a minimal reproduction, please raise a separate issue.

[SimenB]

Fair enough 😀

#1405