app/components/enhance.tsx

Functions

Imports

It imports no other module of this repo. Imported by app/components/ask-panel.tsx, app/components/dictionary-entry.tsx, app/components/home-podcast.tsx, app/components/phage-tool.tsx, app/components/procedure.tsx, app/components/search-trigger.tsx, app/components/site-header.tsx, app/components/theme-toggle.tsx, app/routes/blog.$slug.tsx, app/routes/cv.tsx, app/routes/home.tsx, app/routes/kb-library.tsx, app/routes/lab.kind.tsx, app/routes/lab.tsx, app/routes/phages.tsx, app/routes/procedure.tsx, app/routes/procedure.version.tsx, app/routes/protocols.tsx, app/routes/publications.tsx, app/routes/search.tsx, app/routes/systems.tsx.

Source

1import { ENHANCE_URLS } from "virtual:enhance";
2
3/*
4 * How a public piece becomes interactive today, while public pages do not hydrate:
5 * <Enhance module="plate" /> where the markup it enhances is rendered. The URLs come from the app
6 * build, which bundles each `app/enhance/*.ts` in isolation and emits it as a self-contained asset
7 * (scripts/lib/enhance-bundle.mjs).
8 */
9export { ENHANCE_URLS };
10
11export type EnhanceModule = keyof typeof ENHANCE_URLS;
12
13// A marker, not a script: a `<template>` is never fetched or run. The loader app/root.tsx renders
14// at the end of <body> (app/lib/enhance-loader.mjs) inserts one module script per URL, which the
15// policy allows as same-origin ('self'), so a cached page needs no nonce.
16export function Enhance({ module }: { module: EnhanceModule }) {
17  return <template data-enhance={ENHANCE_URLS[module]} />;
18}