Serving static files without processing

[shalvah]

I have an openapi.json file in my static directory, but whenever I link to it in Markdown like this:

[download the OpenAPI spec](/openapi.json)

I get a Webpack error.

./static/openapi.json (./node_modules/file-loader/dist/cjs.js?name=assets/files/[name]-[hash].[ext]!./static/openapi.json)
Module parse failed: Unexpected token e in JSON at position 0 while parsing near 'export default __web...'
File was processed with these loaders:
 * ./node_modules/file-loader/dist/cjs.js
You may need an additional loader to handle the result of these loaders.
SyntaxError: Unexpected token e in JSON at position 0 while parsing near 'export default __web...'
    at JSON.parse (<anonymous>)

Apparently, Webpack is trying to load it as a JS module, for some reason.

If I change the file extension to '.txt', it works, but the rendered URL includes a version hash.

I understand the rationale, but it's still confusing to me (and I can't see an easy way to override it). My workaround was to hardcode the link using an <a> tag. Is there a way to specify what static assets should be served as-is? If not, could we add this feature?

[slorber]

Hi,

It make sense to load that JSON file both as a webpack asset and a json module, and it seems it's trying to do both at the same time.

We have webpack loader for code (including json), and webpack loader for assets enabling convenient linking https://v2.docusaurus.io/docs/next/markdown-features/assets/#files

We should probably make exceptions for markdown links linking to .js, .jsx, .ts, .ts, .json files as in such case we definitively want to link to the file instead of loading that file as a module.

In the meantime you can use this pathname:// escape hatch:
https://codesandbox.io/s/mystifying-tdd-k58mi?file=/docs/doc1.md

[Link to OpenAPI.json](pathname:///openapi.json)

[shalvah]

I see. Thanks!