Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps-dev): bump @remix-run/dev from 2.3.1 to 2.4.1 #50

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 1, 2024

Bumps @remix-run/dev from 2.3.1 to 2.4.1.

Release notes

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

v2.4.1

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v241

v2.4.0

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v240

Changelog

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

2.4.1

Patch Changes

  • Vite: Error messages when .server files are referenced by client (#8267)

    • Previously, referencing a .server module from client code resulted in an error message like:
      • The requested module '/app/models/answer.server.ts' does not provide an export named 'isDateType'
    • This was confusing because answer.server.ts does provide the isDateType export, but Remix was replacing .server modules with empty modules (export {}) for the client build
    • Now, Remix explicitly fails at compile time when a .server module is referenced from client code and includes dedicated error messages depending on whether the import occurs in a route or a non-route module
    • The error messages also include links to relevant documentation
  • Remove unstable_viteServerBuildModuleId in favor of manually referencing virtual module name "virtual:remix/server-build". (#8264)

    This is a breaking change for projects using the unstable Vite plugin with a custom server.

    This change was made to avoid issues where @remix-run/dev could be inadvertently required in your server's production dependencies.

    Instead, you should manually write the virtual module name "virtual:remix/server-build" when calling ssrLoadModule in development.

    -import { unstable_viteServerBuildModuleId } from "@remix-run/dev";
    // ...
    app.all(
    "*",
    createRequestHandler({
    build: vite
    
    
     ? () => vite.ssrLoadModule(unstable_viteServerBuildModuleId)
    
    
    
    
    
     ? () => vite.ssrLoadModule("virtual:remix/server-build")
    : await import("./build/server/index.js"),
    
    })
    );
  • Vite: Fix errors for non-existent index.html importer (#8353)

  • Add vite:dev and vite:build commands to the Remix CLI. (#8211)

    In order to handle upcoming Remix features where your plugin options can impact the number of Vite builds required, you should now run your Vite dev and build processes via the Remix CLI.

    {
      "scripts": {
    -    "dev": "vite dev",
    -    "build": "vite build && vite build --ssr"
    +    "dev": "remix vite:dev",
    +    "build": "remix vite:build"
      }
  • ... (truncated)

    Commits

    Dependabot compatibility score

    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 <dependency name> 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)

    Bumps [@remix-run/dev](https://github.com/remix-run/remix/tree/HEAD/packages/remix-dev) from 2.3.1 to 2.4.1.
    - [Release notes](https://github.com/remix-run/remix/releases)
    - [Changelog](https://github.com/remix-run/remix/blob/main/packages/remix-dev/CHANGELOG.md)
    - [Commits](https://github.com/remix-run/remix/commits/@remix-run/[email protected]/packages/remix-dev)
    
    ---
    updated-dependencies:
    - dependency-name: "@remix-run/dev"
      dependency-type: direct:development
      update-type: version-update:semver-minor
    ...
    
    Signed-off-by: dependabot[bot] <[email protected]>
    Copy link
    Contributor Author

    dependabot bot commented on behalf of github Jan 1, 2024

    The following labels could not be found: npm dependencies.

    Copy link

    vercel bot commented Jan 1, 2024

    The latest updates on your projects. Learn more about Vercel for Git ↗︎

    Name Status Preview Comments Updated (UTC)
    remix-ecommerce ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 1, 2024 1:35pm

    Copy link
    Contributor Author

    dependabot bot commented on behalf of github Feb 1, 2024

    Superseded by #63.

    @dependabot dependabot bot closed this Feb 1, 2024
    @dependabot dependabot bot deleted the dependabot/npm_and_yarn/remix-run/dev-2.4.1 branch February 1, 2024 13:51
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    None yet
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    0 participants