Bump @remix-run/dev from 1.11.1 to 1.16.0

[dependabot]

Bumps @remix-run/dev from 1.11.1 to 1.16.0.

Release notes

Sourced from @​remix-run/dev's releases.

v1.16.0

Remix is full speed ahead preparing for our upcoming v2 release! 1.16.0 stabilizes a handful of CSS features, contains a major overhaul to the internals of the new remix dev server. and fixes a bunch of bugs.

Stabilized CSS Features

CSS Modules/Vanilla Extract/CSS Side-Effect Imports

Version 1.16.0 stabilizes built-in support for CSS Modules, Vanilla Extract and CSS side-effect imports, which were previously only available via future flags (future.unstable_cssModules, future.unstable_vanillaExtract, future.unstable_cssSideEffectImports). In order to use these features, check out our guide to CSS bundling in your project.

PostCSS

Version 1.16.0 stabilizes built-in PostCSS support via the new postcss option in remix.config.js. As a result, the future.unstable_postcss option has also been deprecated. The postcss option is false by default, but when set to true will enable processing of all CSS files using PostCSS if postcss.config.js is present. For more information on PostCSS support, check out the docs.

If you followed the original PostCSS setup guide for Remix, you may have a folder structure that looks like this, separating your source files from its processed output:

.
├── app
│   └── styles (processed files)
│       ├── app.css
│       └── routes
│           └── index.css
└── styles (source files)
    ├── app.css
    └── routes
        └── index.css

After you've enabled the new postcss option, you can delete the processed files from app/styles folder and move your source files from styles to app/styles:

.
├── app
│   └── styles (source files)
│       ├── app.css
│       └── routes
│           └── index.css

You should then remove app/styles from your .gitignore file since it now contains source files rather than processed output.

You can then update your package.json scripts to remove any usage of postcss since Remix handles this automatically. For example, if you had followed the original setup guide:

{
  "scripts": {
-    "dev:css": "postcss styles --base styles --dir app/styles -w",
-    "build:css": "postcss styles --base styles --dir app/styles --env production",
-    "dev": "concurrently \"npm run dev:css\" \"remix dev\""
+    "dev": "remix dev"
</tr></table> 

... (truncated)

Changelog

Sourced from @​remix-run/dev's changelog.

1.16.0

Minor Changes

• Enable support for CSS Modules, Vanilla Extract and CSS side-effect imports (#6046)

  These CSS bundling features were previously only available via future.unstable_cssModules, future.unstable_vanillaExtract and future.unstable_cssSideEffectImports options in remix.config.js, but they have now been stabilized.

  In order to use these features, check out our guide to CSS bundling in your project.

• Stabilize built-in PostCSS support via the new postcss option in remix.config.js. As a result, the future.unstable_postcss option has also been deprecated. (#5960)

  The postcss option is false by default, but when set to true will enable processing of all CSS files using PostCSS if postcss.config.js is present.

  If you followed the original PostCSS setup guide for Remix, you may have a folder structure that looks like this, separating your source files from its processed output:

  .
  ├── app
  │   └── styles (processed files)
  │       ├── app.css
  │       └── routes
  │           └── index.css
  └── styles (source files)
      ├── app.css
      └── routes
          └── index.css
  

  After you've enabled the new postcss option, you can delete the processed files from app/styles folder and move your source files from styles to app/styles:

  .
  ├── app
  │   └── styles (source files)
  │       ├── app.css
  │       └── routes
  │           └── index.css
  

  You should then remove app/styles from your .gitignore file since it now contains source files rather than processed output.

  You can then update your package.json scripts to remove any usage of postcss since Remix handles this automatically. For example, if you had followed the original setup guide:

  {
    "scripts": {
  -    "dev:css": "postcss styles --base styles --dir app/styles -w",
  -    "build:css": "postcss styles --base styles --dir app/styles --env production",
  -    "dev": "concurrently \"npm run dev:css\" \"remix dev\""
  +    "dev": "remix dev"
    }
  }

... (truncated)

Commits

• 6b9deca chore: Update version for release (#6264)
• 9ac1255 chore: Update version for release (pre) (#6263)
• 37bb7a7 fix: css bundling failing on non-node platforms (#6238)
• 0e39e9b chore: Update version for release (pre) (#6235)
• 37aa765 chore: Update version for release (pre) (#6226)
• 665be90 fix: look for @​remix-run/serve in devDependencies (#6228)
• 39f6405 chore: write mjs server output files (#6225)
• 22280ee chore: Update version for release (pre) (#6224)
• 06c81e3 Revert "Fix splat route index matching (#6222)
• 65b61d3 chore: Update version for release (pre) (#6216)
• 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 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)