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

Bump nextjs-routes from 2.2.1 to 2.2.2 #491

Merged

Conversation

dependabot[bot]
Copy link
Contributor

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

Bumps nextjs-routes from 2.2.1 to 2.2.2.

Release notes

Sourced from nextjs-routes's releases.

v2.2.2

2.2.2

  • Adds support for Next.js's app directory. Link accepts either static routes (no url parameters) or a RouteLiteral string, which can be generated by the route helper from this library:

    import { route } from "nextjs-routes";
    <Link
    href={route({
    pathname: "/foos/[foo]",
    query: { foo: "bar" },
    })}
    >
    Baz
    </Link>;

  • Add RouteLiteral type. This type represents a string that has been confirmed to be a validated application route and can be passed to Link or useRouter. This is a TypeScript branded type.

    import { RouteLiteral } from "nextjs-routes";

    route returns a RouteLiteral. If you construct a route string you can cast it to a RouteLiteral so that Link and useRouter will accept it:

    const myRoute = `/foos/${foo}` as RouteLiteral
    

    In general, prefer using the route helper to generate routes.

  • Refine types for usePathname, useRouter and useParams from "next/navigation" to use nextjs-routes generated types.

  • Fix generated routes when using parallel-routes and intercepting-routes.

  • Fix ref type for Link. Previously ref was missing, now it's correctly typed.

Full Changelog: tatethurston/nextjs-routes@v2.2.1...v2.2.2

v2.2.2-rc.4

2.2.2

  • Adds support for Next.js's app directory. Link accepts either static routes (no url parameters) or a RouteLiteral string, which can be generated by the route helper from this library:

    import { route } from "nextjs-routes";
    <Link
    href={route({
    pathname: "/foos/[foo]",

... (truncated)

Changelog

Sourced from nextjs-routes's changelog.

2.2.2

  • Adds support for Next.js's app directory. Link accepts either static routes (no url parameters) or a RouteLiteral string, which can be generated by the route helper from this library:

    import { route } from "nextjs-routes";
    <Link
    href={route({
    pathname: "/foos/[foo]",
    query: { foo: "bar" },
    })}
    >
    Baz
    </Link>;

  • Add RouteLiteral type. This type represents a string that has been confirmed to be a validated application route and can be passed to Link or useRouter. This is a TypeScript branded type.

    import { RouteLiteral } from "nextjs-routes";

    route returns a RouteLiteral. If you construct a route string you can cast it to a RouteLiteral so that Link and useRouter will accept it:

    const myRoute = `/foos/${foo}` as RouteLiteral
    

    In general, prefer using the route helper to generate routes.

  • Refine types for usePathname, useRouter and useParams from "next/navigation" to use nextjs-routes generated types.

  • Fix generated routes when using parallel-routes and intercepting-routes.

  • Fix ref type for Link. Previously ref was missing, now it's correctly typed.

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 [nextjs-routes](https://github.com/tatethurston/nextjs-routes) from 2.2.1 to 2.2.2.
- [Release notes](https://github.com/tatethurston/nextjs-routes/releases)
- [Changelog](https://github.com/tatethurston/nextjs-routes/blob/main/CHANGELOG.md)
- [Commits](tatethurston/nextjs-routes@v2.2.1...v2.2.2)

---
updated-dependencies:
- dependency-name: nextjs-routes
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Oct 1, 2024
@informatyzacja-ci informatyzacja-ci bot added this pull request to the merge queue Oct 1, 2024
Merged via the queue into main with commit cc0ee7c Oct 1, 2024
5 checks passed
@informatyzacja-ci informatyzacja-ci bot deleted the dependabot/npm_and_yarn/nextjs-routes-2.2.2 branch October 1, 2024 16:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants