What is not built yet, in the order I would build it, with enough design recorded that starting is execution rather than rediscovery. Nothing here is scheduled.
Vitest or Jest against a .tsx. JsxCore cannot provide this without Node, so the honest answer may
be "render through WebApplicationFactory and assert on the markup", which Testing
already covers, but that is not said anywhere a frontend developer will look. Deciding the
recommendation and writing it down is most of this item.
process.env.API_URL, or import.meta.env.MODE. Today process exists only inside the CommonJS
wrapper, so a view referencing it breaks in the browser. That is the exact bug class that broke
React before the wrapper supplied one.
The shape that seems right is an explicit allow-list injected into the import map, rather than ambient access to the server's environment. Leaking configuration into the browser by accident is the risk worth designing against.
Recorded so they are not rediscovered as gaps:
- Vite's
?urland?rawsuffixes.?rawreads a file's contents into a module, which is a different feature from naming a URL. - Content hashing for imported assets. They are served by
UseStaticFilesat their own URL, cached however that middleware is configured rather than immutably like a compiled view. ASP.NET Core's static web assets already fingerprint. - Images beside a component. An image in the views directory is not served and cannot be
imported. Views are a source tree;
wwwrootis what the application serves. Stylesheets are the exception, because those are processed rather than served as they are found. - npm
.binlinking. The native client does not createnode_modules/.bin, because linking executables is a lifecycle-script job it deliberately does not run. Any npm tool with a CLI must be invoked by path, as Styling documents. - Top-level
awaitin a view. It works: an already-resolved promise awaits and the view renders. Anything needing a timer fails withsetTimeout is not defined, because the engine has no event loop, which is a clear enough failure to leave alone. - Client-side routing. React Router works but competes with ASP.NET routing. Which one owns the URL is a question for whoever is building the application.
WebAssembly interop, compiling the exported .NET surface so client-rendered views could call it directly, is not on this list. The design notes are in git history if it ever comes back.
Both are writing and choosing a shape rather than building. Item 1 is a decision to record; item 2 is a decision to design.