This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

[email protected]

Patch Changes

• d81f4ff: add a readme to the npm package

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

[email protected]

Patch Changes

• 477976c: Add repository to package.json

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

[email protected]

Patch Changes

• 238a159: Allow TypedLink to receive children in the types

This PR sort generated routes. I run the build command and test it with the example app.

Notice:

I could extract a function that creates the routes map so I won't have to use the sortedRoutes variable and I could just call it routes, but I'm not sure what is the code style in this repo - so feel free to comment and I will fix it as you want :)

Closes #11

I add as a pre-commit hook to files in pages the next-static-paths script to generate the static-paths.d.ts. I notice that sometimes it creates useless git diff in static-paths.d.ts that is the same as before but with a different paths order.

Diggin into the code I found it uses globby inside. As referenced here https://github.com/sindresorhus/globby/issues/131#issuecomment-513565156 the globby results are not deterministic. I think this causes the git diff.

Can we sort the results to avoid this useless diff?

We can use globbySync and run manual sort after it instead of globbyStream https://github.com/Schniz/next-static-paths/blob/main/packages/next-static-paths/cli/command-generate.ts#L105 here but it can hurt performance a bit

Thanks!

Hi Thank you for creating this package!

I have an issue that react warns me about props passing into the DOM elements when I have the newNextLinkBehavior and the children are DOM elements, and the route requires param.

How to reproduce

• Go to the example app
• Upgrade deps
• Replace the link in index.tsx to be

<TypedLink as={"/dynamic/[userId]"} userId={"myUserId"}>
        Test
      </TypedLink>

• Upgrading to the new route behavior in next.config.js

module.exports = {
  reactStrictMode: true,
  experimental: {
    newNextLinkBehavior: true,
  },
};

• Run pnpm dev
• Navigate to the index page in app

Expected behavior

TypedLink works without warning and the props do not pass to the Link component. The library omits dynamically the props passed to TypedLink like the as prop

Actual behavior

We get a warning

Warning: React does not recognize the `userId` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `userid` instead. If you accidentally passed it from a parent component, remove it from the DOM element.

Workaround

We can still use the pathFor that returns a string and use the regular Link from next/link