automatic `external` attribute for links in `public/` folder
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.7k
- Forks
- 746
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 3
Description
Is your feature request related to a problem? Please describe
got a report from someone who understandably added a link to a pdf in a page - but it just led to a 404
Describe the solution you'd like
given that links in markdown are static, we can detect at build time if it is an actual asset in public/ (or any of the nitro public asset dirs) and automatically add an external prop to ProseA
Describe alternatives you've considered
in nuxt v5 we'll likely do a hard reload (ie make it an external link) if a route isn't resolvable by vue router, but this won't work if there's a root catch-all route.
Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the ProseA link handling and the build-time processing for Markdown links, then inspect how Nuxt and Nitro public asset directories are represented. Done means links targeting assets in public/ or the mentioned Nitro directories receive the external behavior and no longer produce a 404 through Vue Router.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown, nuxt, typescript
- Domain
- content, frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100