Add extension to import

[marcospassos]

Summary

Add extension to import for compatibility with ES modules.

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have checked my code and corrected any misspellings

[github-actions]

👋 @marcospassos
Thanks for your contribution!
The approval and merge process is almost fully automated 🧙
Here's how it works:

1. You open a new pull request
2. Automated tests check the code
3. Maintainers review the code
4. Once approved, the PR is ready to merge.

👉 Omit the extended description
Please remove the commit body before merging the pull request.
Instead, include the pull request number in the title to provide the full context
about the change.

☝️ Lastly, the title for the commit will come from the pull request title. So please provide a descriptive title that summarizes the changes in 50 characters or less using the imperative mood.
Happy coding! 🎉

[Copilot]

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (1)

src/next/TemplateCanvas/index.tsx:4

• Verify that appending the .js extension is required and that 'next/navigation.js' correctly resolves in your build environment, as Next.js conventionally supports import paths without an explicit extension.

import {usePathname, useSearchParams} from 'next/navigation.js';

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@croct/template-ui@19

commit: 8e315c6

[github-actions]

🔥 Here is the preview of the pull request:
https://preview.template-ui.croct.dev/pr-19