node: from the import as i reuse the code for a page and a worker, and worker only works when the node: is specified lol[I]t indicates that Cloudflare should strictly respect Cache-Control directives received from the origin server. Free, Pro and Business customers have this feature enabled by default.Means that a Cache-Control family header should always win over any default values, assuming you don't have a rule telling it otherwise?

Cloudflare-CDN-Cache-Control: public, max-age=3600, stale-while-revalidate=86400


.env file. How does yours look like?


CNAME records normally can not be on the zone apex. We use CNAME flattening to make it possible.
foliox.io NS @1.1.1.1 +noall +answer +shortdiggy diggy hole
•5/19/24, 6:29 PM
Begin DNS Transfer button. What does it show?page:build: ▲ Failed to compile.
page:build: ▲ node:async_hooks
page:build: ▲ Module build failed: UnhandledSchemeError: Reading from "node:async_hooks" is not handled by plugins (Unhandled scheme).
page:build: ▲ Webpack supports "data:" and "file:" URIs by default.
page:build: ▲ You may need an additional plugin to handle "node:" URIs.node:node:config.plugins.push(
new webpack.NormalModuleReplacementPlugin(/^node:.*$/, (resource) => {
resource.request = resource.request.replace("node:", "");
}),
);
config.resolve.fallback = {
...config.resolve.fallback,
async_hooks: false,
};