Crawling wrong urls and generating unnesecary folders
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 175
- Forks
- 17
- Avg merge
- 5h 26m
- Merged PRs (30d)
- 5
Description
Suppose we are embedding multiple markdown files with links using -- $!{readmeContent}.
These readme files which have been taken from github generally contain links in the form of /something instead of https://github.com/something so, the crawler thinks that /something is a route of my website and generates a folder like /something/index.html which is the main issue. There should be a way to control this, like an option in vite.config.js to for example add only the urls that I want to generate or disable the crawler altogether for specific routes.
Contributor guide
No contributing guide indexed for this repository
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 by tracing the crawler behavior for relative links found in embedded Markdown and inspect how vite.config.js could expose crawler controls. Define whether the change should allow selected URLs, exclude routes, or disable crawling, then verify that unwanted folders such as /something/index.html are no longer generated while intended routes still are.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vite
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100