Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

image asset: ENOENT error for remote markdown files with relative paths #6635

Closed
1 task
mashehu opened this issue Mar 23, 2023 · 1 comment · Fixed by #7139
Closed
1 task

image asset: ENOENT error for remote markdown files with relative paths #6635

mashehu opened this issue Mar 23, 2023 · 1 comment · Fixed by #7139
Assignees
Labels
- P2: nice to have Not breaking anything but nice to have (priority) feat: assets Related to the Assets feature (scope)

Comments

@mashehu
Copy link

mashehu commented Mar 23, 2023

What version of astro are you using?

2.1.5

Are you using an SSR adapter? If so, which one?

None

What package manager are you using?

npm

What operating system are you using?

MacOS

What browser are you using?

Chrome

Describe the Bug

With the new image assets, relative links to images in a remote markdown are not resolved well and generate a ENOENT error which stops the server. See example below

Link to Minimal Reproducible Example

https://stackblitz.com/edit/github-mnzpmy-qdvhnk?file=astro/package.json

Participation

  • I am willing to submit a pull request for this issue.
@Princesseuh Princesseuh added the feat: assets Related to the Assets feature (scope) label Mar 23, 2023
@Princesseuh Princesseuh self-assigned this Mar 23, 2023
@Princesseuh Princesseuh added the - P3: minor bug An edge case that only affects very specific usage (priority) label Mar 24, 2023
@Princesseuh
Copy link
Member

It's unfortunately unlikely that we can support this. Importing files from outside the Astro project is not a supported use case we have at the moment, and is unfortunately unlikely to happen to be due to technical restrictions regarding where files can live.

@Princesseuh Princesseuh added - P2: nice to have Not breaking anything but nice to have (priority) and removed - P3: minor bug An edge case that only affects very specific usage (priority) labels May 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
- P2: nice to have Not breaking anything but nice to have (priority) feat: assets Related to the Assets feature (scope)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants