fix: correct outdated Next.js docs and example #293
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…n nextjs documentation and example
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
@TobyDS is attempting to deploy a commit to the t3-oss Team on Vercel. A member of the Team first needs to authorize it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
jiti no longer uses the default export or the
jiti()function. As such I have update the documentation to use the correct import:import { createJiti } from "jiti", and the suggested replacement for thejiti()function:await jiti.import().I also found that the documentation and example differed in the constuction of the path inside the
createJiti()function. As such I have edited the documentation and the example to match each other to avoid confusion. I oped to use the syntax from the example:const jiti = createJiti(new URL(import.meta.url).pathname)as it doesn't require importing a function from node:url, which is currently the method used in the docs.