Ignore assets in src/pages/ to suppress warning "unsupported file type"

[aymkx]

Changes

• Add assetExtensions: string[] to AstroSettings
  • The default value derives from VALID_INPUT_FORMATS.
• Add addAssetExtension to astro:config:setup hook for customizing (dynamically and silently in the same way as addPageExtension)
• Add a condition to suppress warning "unsupported file type" in src/pages/ while constructing static routes

Motivation

Astro regards .astro, .md, .mdx and etc. files in src/pages/ directory as pages and builds static routes to them.

By the way, image files to be optimized should be specified and inserted by relative path from the document: ![](./path/to/image) or import somethingImage from "./path/to/image"; <Image src={somethingImage} />. It seems to be recommended to locate such assets in src/assets/ directory, but I feel it irrational especially when there are many documents and assets in deep directory; tbh, we should locate referred assets in the same directory of the document.

In this way, the problem emerges: noisily warned that "unsupported file type" is found in src/pages/ directory for EACH asset file (by #9105).

The initial change which introduced this (#6851) looks good and I think, respecting the PR, we should not take a quick solution: removing the warning or degrading it to debug level.

In addition, configurable structured logging may solve this, but it seems to be a hard job. So, this is a kind of workarounds.

Testing

There is no unit tests because the changed behavior is only warning.
Locating png file in src/pages/ and inserting it in MDX, I tried building example/with-mdx and it ran as expected.

Docs

There is no change to be documented.

[changeset-bot]

🦋 Changeset detected

Latest commit: 4cb2076

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[codspeed-hq]

CodSpeed Performance Report

Merging #13319 will not alter performance

_{Comparing aymkx:ignore-assets-in-pages (4cb2076) with main (5f72a58)}

Summary

✅ 6 untouched benchmarks

[github-actions]

This PR is blocked because it contains a minor changeset. A reviewer will merge this at the next release if approved.

[ematipico]

pages/ is a known folder to Astro, and it assumes that all files in that folder are pages that can be parsed in a certain why, and emitted as .html/.js files at the build (static or SSR).

but I feel it irrational especially when there are many documents and assets in deep directory

You can use aliases

I suggest you to create a discussion first in https://github.com/withastro/roadmap, and see if the proposal gain traction

[aymkx]

I know about alias, but even if to be used, it is still irrational when there is a deep directory in src/assets/, and the same goes for arranging all assets flat.
Anyway, I'm not against the convention itself. I want to stop the annoying warning. It just means what is commented in #6851 actually happened.
Thanks for your response.