mirror of
https://github.com/hanzoai/help-site.git
synced 2026-10-30 14:39:12 +00:00
zeekay
a31783cabd
@hanzo/event 0.3.61 runs its own stream whatever the visitor chose, and consent gates the third parties alone, so the provider is no longer switched off until Analytics is allowed: a pageview reaches /v1/event before any choice, and GA4 and the Pixel still wait for Accept all. @hanzo/ui 8.29.14 is the banner with the new copy and no Reject button. Its preferences sheet draws icons through react-native-svg, which picks its web build by the extension list alone; Turbopack applies that list only to transpiled packages, so react-native-svg is transpiled.
44 lines
1.8 KiB
TypeScript
44 lines
1.8 KiB
TypeScript
import type { NextConfig } from "next";
|
|
|
|
/**
|
|
* @hanzo/ui draws through @hanzo/gui, which is a react-native-web renderer on
|
|
* the browser. Two resolver facts follow, and both have to hold in dev AND in
|
|
* build or the two disagree:
|
|
*
|
|
* - `react-native` means `react-native-web` here. Without the alias the
|
|
* resolver reaches the real package, which ships untranspiled Flow and dies
|
|
* on `import typeof` before any of our code runs.
|
|
* - `.web.js` wins over `.js`. That is how react-native-svg (under the icon
|
|
* set) offers a browser implementation of the same module — it is picked by
|
|
* extension order, not by an export map, so the order is the whole mechanism.
|
|
*/
|
|
const alias = {
|
|
"react-native": "react-native-web",
|
|
// react-native-svg's web build asks React Native for the asset registry; on
|
|
// web that registry is react-native-web's.
|
|
"@react-native/assets-registry/registry": "react-native-web/dist/modules/AssetRegistry",
|
|
};
|
|
const extensions = [".web.tsx", ".web.ts", ".web.jsx", ".web.js"];
|
|
|
|
const nextConfig: NextConfig = {
|
|
output: "export",
|
|
reactStrictMode: true,
|
|
// Turbopack applies the extension list to the project and to transpiled
|
|
// packages, never to the rest of node_modules. react-native-svg (under the
|
|
// banner's icons) picks its web build by that list alone, so outside this it
|
|
// bundles the native one: Flow source and TurboModuleRegistry, which
|
|
// react-native-web does not export.
|
|
transpilePackages: ["react-native-svg"],
|
|
turbopack: {
|
|
resolveAlias: alias,
|
|
resolveExtensions: [...extensions, ".tsx", ".ts", ".jsx", ".js", ".mjs", ".json"],
|
|
},
|
|
webpack: (config) => {
|
|
config.resolve.alias = { ...config.resolve.alias, ...alias, "react-native$": "react-native-web" };
|
|
config.resolve.extensions = [...extensions, ...config.resolve.extensions];
|
|
return config;
|
|
},
|
|
};
|
|
|
|
export default nextConfig;
|