@dtwo/schema 3.0.0-rc.14 → 3.1.0-0

package/schema/config.d.ts

@@ -17,1231 +17,1387 @@ import type { Options } from 'webpack-dev-middleware'
 import type { IncomingMessage, ServerResponse } from 'http'
 import type { MiddlewareOptions, ClientOptions } from 'webpack-hot-middleware'
 export interface ConfigSchema {
-   /**
-   * Configure Dtwo component auto-registration.
-   * Any components in the directories configured here can be used throughout your pages, layouts (and other components) without needing to explicitly import them.
+ /**
+  * Configure Dtwo component auto-registration.
+  * 
+  * Any components in the directories configured here can be used throughout your pages, layouts (and other components) without needing to explicitly import them.
+  * 
+  * 
+  * @see https://dtwojs.web.app/docs/guide/directory-structure/components
+ */
+ components: boolean | ComponentsOptions | ComponentsOptions['dirs'],
+
+ /**
+  * Configure how Dtwo auto-imports composables into your application.
+  * 
+  * 
+  * @see [Dtwo 3 documentation](https://dtwojs.web.app/docs/guide/directory-structure/composables)
+ */
+ imports: ImportsOptions,
+
+ /**
+  * Whether to use the kdu-router integration in Dtwo 3. If you do not provide a value it will be enabled if you have a `pages/` directory in your source folder.
+  * 
+ */
+ pages: boolean,
+
+ /**
+  * Manually disable dtwo telemetry.
+  * 
+ */
+ telemetry: boolean,
+
+ /**
+  * Kdu.js config
+  * 
+ */
+ kdu: {
+  /**
+   * Options for the Kdu compiler that will be passed at build time.
+   * 
    * 
-   * @default {{ dirs: [`~/components`] }}
+   * @see [documentation](https://kdu-js.web.app/api/application.html#app-config-compileroptions)
   */
-  components: boolean | ComponentsOptions | ComponentsOptions['dirs'],
-
-  /** Configure how Dtwo auto-imports composables into your application. */
-  imports: ImportsOptions,
-
-  /** Whether to use the kdu-router integration in Dtwo 3. If you do not provide a value it will be enabled if you have a `pages/` directory in your source folder. */
-  pages: boolean,
-
-  /** Manually disable dtwo telemetry. */
-  telemetry: boolean,
-
-  /** Kdu.js config */
-  kdu: {
-    /**
-     * Options for the Kdu compiler that will be passed at build time.
-     * 
-     * @see [documentation](https://kdu-js.web.app/api/application.html#app-config-compileroptions)
-    */
-    compilerOptions: CompilerOptions,
-  },
+  compilerOptions: CompilerOptions,
+ },
+
+ /**
+  * Dtwo App configuration.
+  * 
+ */
+ app: {
+  /**
+   * The base path of your Dtwo application.
+   * 
+   * This can be set at runtime by setting the DTWO_APP_BASE_URL environment variable.
+   * 
+   * @default "/"
+   * 
+   * @example
+   * ```bash
+   * DTWO_APP_BASE_URL=/prefix/ node .output/server/index.mjs
+   * ```
+  */
+  baseURL: string,
 
-  /** Dtwo App configuration. */
-  app: {
-    /**
-     * The base path of your Dtwo application.
-     * This can be set at runtime by setting the DTWO_APP_BASE_URL environment variable.
-     * @default "/"
-     * 
-     * @example
-     * ```bash
-     * DTWO_APP_BASE_URL=/prefix/ node .output/server/index.mjs
-     * ```
-    */
-    baseURL: string,
-
-    /**
-     * The folder name for the built site assets, relative to `baseURL` (or `cdnURL` if set). This is set at build time and should not be customized at runtime.
-     * @default "/_dtwo/"
-    */
-    buildAssetsDir: string,
-
-    /**
-     * An absolute URL to serve the public folder from (production-only).
-     * This can be set to a different value at runtime by setting the `DTWO_APP_CDN_URL` environment variable.
-     * @default ""
-     * 
-     * @example
-     * ```bash
-     * DTWO_APP_CDN_URL=https://mycdn.org/ node .output/server/index.mjs
-     * ```
-    */
-    cdnURL: string,
-
-    /**
-     * Set default configuration for `<head>` on every page.
-     * 
-     * @example
-     * ```js
-     * app: {
-     *   head: {
-     *     meta: [
-     *       // <meta name="viewport" content="width=device-width, initial-scale=1">
-     *       { name: 'viewport', content: 'width=device-width, initial-scale=1' }
-     *     ],
-     *     script: [
-     *       // <script src="https://myawesome-lib.js"></script>
-     *       { src: 'https://awesome-lib.js' }
-     *     ],
-     *     link: [
-     *       // <link rel="stylesheet" href="https://myawesome-lib.css">
-     *       { rel: 'stylesheet', href: 'https://awesome-lib.css' }
-     *     ],
-     *     // please note that this is an area that is likely to change
-     *     style: [
-     *       // <style type="text/css">:root { color: red }</style>
-     *       { children: ':root { color: red }', type: 'text/css' }
-     *     ],
-     *     noscript: [
-     *       // <noscript>Javascript is required</noscript>
-     *       { children: 'Javascript is required' }
-     *     ]
-     *   }
-     * }
-     * ```
-    */
-    head: DtwoAppConfig['head'],
-
-    /**
-     * Default values for layout transitions.
-     * This can be overridden with `definePageMeta` on an individual page. Only JSON-serializable values are allowed.
-     * @default false
-     * 
-     * @see https://kdu-js.web.app/api/built-in-components.html#transition
-    */
-    layoutTransition: DtwoAppConfig['layoutTransition'],
-
-    /**
-     * Default values for page transitions.
-     * This can be overridden with `definePageMeta` on an individual page. Only JSON-serializable values are allowed.
-     * @default false
-     * 
-     * @see https://kdu-js.web.app/api/built-in-components.html#transition
-    */
-    pageTransition: DtwoAppConfig['pageTransition'],
-
-    /**
-     * Default values for KeepAlive configuration between pages.
-     * This can be overridden with `definePageMeta` on an individual page. Only JSON-serializable values are allowed.
-     * @default false
-     * 
-     * @see https://kdu-js.web.app/api/built-in-components.html#keepalive
-    */
-    keepalive: DtwoAppConfig['keepalive'],
-
-    /**
-     * Customize Dtwo root element id.
-     * @default "__dtwo"
-    */
-    rootId: string,
-
-    /**
-     * Customize Dtwo root element tag.
-     * @default "div"
-    */
-    rootTag: string,
-  },
+  /**
+   * The folder name for the built site assets, relative to `baseURL` (or `cdnURL` if set). This is set at build time and should not be customized at runtime.
+   * 
+   * @default "/_dtwo/"
+  */
+  buildAssetsDir: string,
 
   /**
-   * An array of dtwo app plugins.
-   * Each plugin can be a string (which can be an absolute or relative path to a file). If it ends with `.client` or `.server` then it will be automatically loaded only in the appropriate context.
-   * It can also be an object with `src` and `mode` keys.
+   * An absolute URL to serve the public folder from (production-only).
+   * 
+   * This can be set to a different value at runtime by setting the `DTWO_APP_CDN_URL` environment variable.
+   * 
+   * @default ""
    * 
    * @example
-   * ```js
-   * plugins: [
-   *   '~/plugins/foo.client.js', // only in client side
-   *   '~/plugins/bar.server.js', // only in server side
-   *   '~/plugins/baz.js', // both client & server
-   *   { src: '~/plugins/both-sides.js' },
-   *   { src: '~/plugins/client-only.js', mode: 'client' }, // only on client side
-   *   { src: '~/plugins/server-only.js', mode: 'server' } // only on server side
-   * ]
+   * ```bash
+   * DTWO_APP_CDN_URL=https://mycdn.org/ node .output/server/index.mjs
    * ```
   */
-  plugins: (DtwoPlugin | string)[],
+  cdnURL: string,
 
   /**
-   * You can define the CSS files/modules/libraries you want to set globally (included in every page).
-   * Dtwo will automatically guess the file type by its extension and use the appropriate pre-processor. You will still need to install the required loader if you need to use them.
+   * Set default configuration for `<head>` on every page.
+   * 
    * 
    * @example
    * ```js
-   * css: [
-   *   // Load a Node.js module directly (here it's a Sass file).
-   *   'bulma',
-   *   // CSS file in the project
-   *   '@/assets/css/main.css',
-   *   // SCSS file in the project
-   *   '@/assets/css/main.scss'
-   * ]
+   * app: {
+   *   head: {
+   *     meta: [
+   *       // <meta name="viewport" content="width=device-width, initial-scale=1">
+   *       { name: 'viewport', content: 'width=device-width, initial-scale=1' }
+   *     ],
+   *     script: [
+   *       // <script src="https://myawesome-lib.js"></script>
+   *       { src: 'https://awesome-lib.js' }
+   *     ],
+   *     link: [
+   *       // <link rel="stylesheet" href="https://myawesome-lib.css">
+   *       { rel: 'stylesheet', href: 'https://awesome-lib.css' }
+   *     ],
+   *     // please note that this is an area that is likely to change
+   *     style: [
+   *       // <style type="text/css">:root { color: red }</style>
+   *       { children: ':root { color: red }', type: 'text/css' }
+   *     ],
+   *     noscript: [
+   *       // <noscript>JavaScript is required</noscript>
+   *       { children: 'JavaScript is required' }
+   *     ]
+   *   }
+   * }
    * ```
   */
-  css: string[],
-
-  /**
-   * The builder to use for bundling the Kdu part of your application.
-   * @default "@dtwo/wite-builder"
-  */
-  builder: 'wite' | 'webpack' | { bundle: (dtwo: Dtwo) => Promise<void> },
-
-  /** Whether to generate sourcemaps. */
-  sourcemap: boolean | { server?: boolean, client?: boolean },
-
-  /** Shared build configuration. */
-  build: {
-    /**
-     * If you want to transpile specific dependencies with Babel, you can add them here. Each item in transpile can be a package name, a function, a string or regex object matching the dependency's file name.
-     * You can also use a function to conditionally transpile. The function will receive an object ({ isDev, isServer, isClient, isModern, isLegacy }).
-     * 
-     * @example
-     * ```js
-     *       transpile: [({ isLegacy }) => isLegacy && 'ky']
-     * ```
-    */
-    transpile: Array<string | RegExp | Function>,
-
-    /**
-     * You can provide your own templates which will be rendered based on Dtwo configuration. This feature is specially useful for using with modules.
-     * Templates are rendered using [`lodash.template`](https://lodash.com/docs/4.17.15#template).
-     * 
-     * @example
-     * ```js
-     * templates: [
-     *   {
-     *     src: '~/modules/support/plugin.js', // `src` can be absolute or relative
-     *     dst: 'support.js', // `dst` is relative to project `.dtwo` dir
-     *     options: {
-     *       // Options are provided to template as `options` key
-     *       live_chat: false
-     *     }
-     *   }
-     * ]
-     * ```
-    */
-    templates: Array<any>,
-
-    /**
-     * Dtwo uses `webpack-bundle-analyzer` to visualize your bundles and how to optimize them.
-     * Set to `true` to enable bundle analysis, or pass an object with options: [for webpack](https://github.com/webpack-contrib/webpack-bundle-analyzer#options-for-plugin) or [for wite](https://github.com/btd/rollup-plugin-visualizer#options).
-     * @default false
-     * 
-     * @example
-     * ```js
-     * analyze: {
-     *   analyzerMode: 'static'
-     * }
-     * ```
-    */
-    analyze: boolean | BundleAnalyzerPlugin.Options | PluginVisualizerOptions,
-  },
+  head: DtwoAppConfig['head'],
 
   /**
-   * Extend project from multiple local or remote sources.
-   * Value should be either a string or array of strings pointing to source directories or config path relative to current config.
-   * You can use `github:`, `gitlab:`, `bitbucket:` or `https://` to extend from a remote git repository.
+   * Default values for layout transitions.
+   * 
+   * This can be overridden with `definePageMeta` on an individual page. Only JSON-serializable values are allowed.
+   * 
+   * @default false
+   * 
+   * @see https://kdu-js.web.app/api/built-in-components.html#transition
   */
-  extends: string|string[],
+  layoutTransition: DtwoAppConfig['layoutTransition'],
 
   /**
-   * Extend project from a local or remote source.
-   * Value should be a string pointing to source directory or config path relative to current config.
-   * You can use `github:`, `gitlab:`, `bitbucket:` or `https://` to extend from a remote git repository.
-   * @default null
+   * Default values for page transitions.
+   * 
+   * This can be overridden with `definePageMeta` on an individual page. Only JSON-serializable values are allowed.
+   * 
+   * @default false
+   * 
+   * @see https://kdu-js.web.app/api/built-in-components.html#transition
   */
-  theme: string,
+  pageTransition: DtwoAppConfig['pageTransition'],
 
   /**
-   * Define the root directory of your application.
-   * This property can be overwritten (for example, running `dtwo ./my-app/` will set the `rootDir` to the absolute path of `./my-app/` from the current/working directory.
-   * It is normally not needed to configure this option.
-   * @default "/<rootDir>"
+   * Default values for KeepAlive configuration between pages.
+   * 
+   * This can be overridden with `definePageMeta` on an individual page. Only JSON-serializable values are allowed.
+   * 
+   * @default false
+   * 
+   * @see https://kdu-js.web.app/api/built-in-components.html#keepalive
   */
-  rootDir: string,
+  keepalive: DtwoAppConfig['keepalive'],
 
   /**
-   * Define the workspace directory of your application.
-   * Often this is used when in a monorepo setup. Dtwo will attempt to detect your workspace directory automatically, but you can override it here.
-   * It is normally not needed to configure this option.
-   * @default "/<rootDir>"
+   * Customize Dtwo root element id.
+   * 
+   * @default "__dtwo"
   */
-  workspaceDir: string,
+  rootId: string,
 
   /**
-   * Define the source directory of your Dtwo application.
-   * If a relative path is specified, it will be relative to the `rootDir`.
-   * @default "/<rootDir>"
+   * Customize Dtwo root element tag.
+   * 
+   * @default "div"
+  */
+  rootTag: string,
+ },
+
+ /**
+  * An array of dtwo app plugins.
+  * 
+  * Each plugin can be a string (which can be an absolute or relative path to a file). If it ends with `.client` or `.server` then it will be automatically loaded only in the appropriate context.
+  * It can also be an object with `src` and `mode` keys.
+  * 
+  * 
+  * @note Plugins are also auto-registered from the `~/plugins` directory
+  * and these plugins do not need to be listed in `dtwo.config` unless you
+  * need to customize their order. All plugins are deduplicated by their src path.
+  * 
+  * @see https://dtwojs.web.app/docs/guide/directory-structure/plugins
+  * 
+  * @example
+  * ```js
+  * plugins: [
+  *   '~/plugins/foo.client.js', // only in client side
+  *   '~/plugins/bar.server.js', // only in server side
+  *   '~/plugins/baz.js', // both client & server
+  *   { src: '~/plugins/both-sides.js' },
+  *   { src: '~/plugins/client-only.js', mode: 'client' }, // only on client side
+  *   { src: '~/plugins/server-only.js', mode: 'server' } // only on server side
+  * ]
+  * ```
+ */
+ plugins: (DtwoPlugin | string)[],
+
+ /**
+  * You can define the CSS files/modules/libraries you want to set globally (included in every page).
+  * 
+  * Dtwo will automatically guess the file type by its extension and use the appropriate pre-processor. You will still need to install the required loader if you need to use them.
+  * 
+  * 
+  * @example
+  * ```js
+  * css: [
+  *   // Load a Node.js module directly (here it's a Sass file).
+  *   'bulma',
+  *   // CSS file in the project
+  *   '@/assets/css/main.css',
+  *   // SCSS file in the project
+  *   '@/assets/css/main.scss'
+  * ]
+  * ```
+ */
+ css: string[],
+
+ /**
+  * The builder to use for bundling the Kdu part of your application.
+  * 
+  * @default "@dtwo/wite-builder"
+ */
+ builder: 'wite' | 'webpack' | { bundle: (dtwo: Dtwo) => Promise<void> },
+
+ /**
+  * Whether to generate sourcemaps.
+  * 
+ */
+ sourcemap: boolean | { server?: boolean, client?: boolean },
+
+ /**
+  * Shared build configuration.
+  * 
+ */
+ build: {
+  /**
+   * If you want to transpile specific dependencies with Babel, you can add them here. Each item in transpile can be a package name, a function, a string or regex object matching the dependency's file name.
+   * 
+   * You can also use a function to conditionally transpile. The function will receive an object ({ isDev, isServer, isClient, isModern, isLegacy }).
+   * 
    * 
    * @example
    * ```js
-   * export default {
-   *   srcDir: 'src/'
-   * }
-   * ```
-   * This would work with the following folder structure:
-   * ```bash
-   * -| app/
-   * ---| node_modules/
-   * ---| dtwo.config.js
-   * ---| package.json
-   * ---| src/
-   * ------| assets/
-   * ------| components/
-   * ------| layouts/
-   * ------| middleware/
-   * ------| pages/
-   * ------| plugins/
-   * ------| static/
-   * ------| store/
-   * ------| server/
+   *       transpile: [({ isLegacy }) => isLegacy && 'ky']
    * ```
   */
-  srcDir: string,
+  transpile: Array<string | RegExp | ((ctx: { isClient?: boolean; isServer?: boolean; isDev: boolean }) => string | RegExp | false)>,
 
   /**
-   * Define the server directory of your Dtwo application, where Hole routes, middleware and plugins are kept.
-   * If a relative path is specified, it will be relative to your `rootDir`.
-   * @default "/<rootDir>/server"
-  */
-  serverDir: string,
-
-  /**
-   * Define the directory where your built Dtwo files will be placed.
-   * Many tools assume that `.dtwo` is a hidden directory (because it starts with a `.`). If that is a problem, you can use this option to prevent that.
-   * @default "/<rootDir>/.dtwo"
+   * You can provide your own templates which will be rendered based on Dtwo configuration. This feature is specially useful for using with modules.
+   * 
+   * Templates are rendered using [`lodash.template`](https://lodash.com/docs/4.17.15#template).
+   * 
    * 
    * @example
    * ```js
-   * export default {
-   *   buildDir: 'dtwo-build'
-   * }
+   * templates: [
+   *   {
+   *     src: '~/modules/support/plugin.js', // `src` can be absolute or relative
+   *     dst: 'support.js', // `dst` is relative to project `.dtwo` dir
+   *     options: {
+   *       // Options are provided to template as `options` key
+   *       live_chat: false
+   *     }
+   *   }
+   * ]
    * ```
   */
-  buildDir: string,
+  templates: Array<any>,
 
   /**
-   * Used to set the modules directories for path resolving (for example, webpack's `resolveLoading`, `nodeExternals` and `postcss`).
-   * The configuration path is relative to `options.rootDir` (default is current working directory).
-   * Setting this field may be necessary if your project is organized as a yarn workspace-styled mono-repository.
-   * @default ["/<rootDir>/node_modules","D:/Workspace/ORGs/d2js/dtwo/packages/schema/node_modules"]
+   * Dtwo uses `webpack-bundle-analyzer` to visualize your bundles and how to optimize them.
+   * 
+   * Set to `true` to enable bundle analysis, or pass an object with options: [for webpack](https://github.com/webpack-contrib/webpack-bundle-analyzer#options-for-plugin) or [for wite](https://github.com/btd/rollup-plugin-visualizer#options).
+   * 
+   * @default false
    * 
    * @example
    * ```js
-   * export default {
-   *   modulesDir: ['../../node_modules']
+   * analyze: {
+   *   analyzerMode: 'static'
    * }
    * ```
   */
-  modulesDir: Array<string>,
+  analyze: boolean | BundleAnalyzerPlugin.Options | PluginVisualizerOptions,
+ },
+
+ /**
+  * Extend project from multiple local or remote sources.
+  * 
+  * Value should be either a string or array of strings pointing to source directories or config path relative to current config.
+  * You can use `github:`, `gitlab:`, `bitbucket:` or `https://` to extend from a remote git repository.
+  * 
+ */
+ extends: string|string[],
+
+ /**
+  * Extend project from a local or remote source.
+  * 
+  * Value should be a string pointing to source directory or config path relative to current config.
+  * You can use `github:`, `gitlab:`, `bitbucket:` or `https://` to extend from a remote git repository.
+  * 
+  * @default null
+ */
+ theme: string,
+
+ /**
+  * Define the root directory of your application.
+  * 
+  * This property can be overwritten (for example, running `dtwo ./my-app/` will set the `rootDir` to the absolute path of `./my-app/` from the current/working directory.
+  * It is normally not needed to configure this option.
+  * 
+  * @default "/<rootDir>"
+ */
+ rootDir: string,
+
+ /**
+  * Define the workspace directory of your application.
+  * 
+  * Often this is used when in a monorepo setup. Dtwo will attempt to detect your workspace directory automatically, but you can override it here.
+  * It is normally not needed to configure this option.
+  * 
+  * @default "/<rootDir>"
+ */
+ workspaceDir: string,
+
+ /**
+  * Define the source directory of your Dtwo application.
+  * 
+  * If a relative path is specified, it will be relative to the `rootDir`.
+  * 
+  * @default "/<rootDir>"
+  * 
+  * @example
+  * ```js
+  * export default {
+  *   srcDir: 'src/'
+  * }
+  * ```
+  * This would work with the following folder structure:
+  * ```bash
+  * -| app/
+  * ---| node_modules/
+  * ---| dtwo.config.js
+  * ---| package.json
+  * ---| src/
+  * ------| assets/
+  * ------| components/
+  * ------| layouts/
+  * ------| middleware/
+  * ------| pages/
+  * ------| plugins/
+  * ------| static/
+  * ------| store/
+  * ------| server/
+  * ```
+ */
+ srcDir: string,
+
+ /**
+  * Define the server directory of your Dtwo application, where Hole routes, middleware and plugins are kept.
+  * 
+  * If a relative path is specified, it will be relative to your `rootDir`.
+  * 
+  * @default "/<rootDir>/server"
+ */
+ serverDir: string,
+
+ /**
+  * Define the directory where your built Dtwo files will be placed.
+  * 
+  * Many tools assume that `.dtwo` is a hidden directory (because it starts with a `.`). If that is a problem, you can use this option to prevent that.
+  * 
+  * @default "/<rootDir>/.dtwo"
+  * 
+  * @example
+  * ```js
+  * export default {
+  *   buildDir: 'dtwo-build'
+  * }
+  * ```
+ */
+ buildDir: string,
+
+ /**
+  * Used to set the modules directories for path resolving (for example, webpack's `resolveLoading`, `nodeExternals` and `postcss`).
+  * 
+  * The configuration path is relative to `options.rootDir` (default is current working directory).
+  * Setting this field may be necessary if your project is organized as a yarn workspace-styled mono-repository.
+  * 
+  * @default ["/<rootDir>/node_modules","D:/Workspace/ORGs/d2js/dtwo/packages/schema/node_modules"]
+  * 
+  * @example
+  * ```js
+  * export default {
+  *   modulesDir: ['../../node_modules']
+  * }
+  * ```
+ */
+ modulesDir: Array<string>,
+
+ /**
+  * Whether Dtwo is running in development mode.
+  * 
+  * Normally, you should not need to set this.
+  * 
+  * @default false
+ */
+ dev: boolean,
+
+ /**
+  * Whether your app is being unit tested.
+  * 
+  * @default false
+ */
+ test: boolean,
+
+ /**
+  * Set to `true` to enable debug mode.
+  * 
+  * At the moment, it prints out hook names and timings on the server, and logs hook arguments as well in the browser.
+  * 
+  * @default false
+ */
+ debug: boolean,
+
+ /**
+  * Whether to enable rendering of HTML - either dynamically (in server mode) or at generate time. If set to `false` and combined with `static` target, generated pages will simply display a loading screen with no content.
+  * 
+  * @default true
+ */
+ ssr: boolean,
+
+ /**
+  * Modules are Dtwo extensions which can extend its core functionality and add endless integrations.
+  * 
+  * Each module is either a string (which can refer to a package, or be a path to a file), a tuple with the module as first string and the options as a second object, or an inline module function.
+  * Dtwo tries to resolve each item in the modules array using node require path (in `node_modules`) and then will be resolved from project `srcDir` if `~` alias is used.
+  * 
+  * 
+  * @note Modules are executed sequentially so the order is important.
+  * 
+  * @example
+  * ```js
+  * modules: [
+  *   // Using package name
+  *   '@dtwojs/axios',
+  *   // Relative to your project srcDir
+  *   '~/modules/awesome.js',
+  *   // Providing options
+  *   ['@dtwojs/google-analytics', { ua: 'X1234567' }],
+  *   // Inline definition
+  *   function () {}
+  * ]
+  * ```
+ */
+ modules: (DtwoModule | string | [DtwoModule | string, Record<string, any>])[],
+
+ /**
+  * Customize default directory structure used by Dtwo.
+  * 
+  * It is better to stick with defaults unless needed.
+  * 
+ */
+ dir: {
+  /**
+   * The assets directory (aliased as `~assets` in your build).
+   * 
+   * @default "assets"
+  */
+  assets: string,
 
   /**
-   * Whether Dtwo is running in development mode.
-   * Normally, you should not need to set this.
-   * @default false
+   * The layouts directory, each file of which will be auto-registered as a Dtwo layout.
+   * 
+   * @default "layouts"
   */
-  dev: boolean,
+  layouts: string,
 
   /**
-   * Whether your app is being unit tested.
-   * @default false
+   * The middleware directory, each file of which will be auto-registered as a Dtwo middleware.
+   * 
+   * @default "middleware"
   */
-  test: boolean,
+  middleware: string,
 
   /**
-   * Set to `true` to enable debug mode.
-   * At the moment, it prints out hook names and timings on the server, and logs hook arguments as well in the browser.
-   * @default false
+   * The directory which will be processed to auto-generate your application page routes.
+   * 
+   * @default "pages"
   */
-  debug: boolean,
+  pages: string,
 
   /**
-   * Whether to enable rendering of HTML - either dynamically (in server mode) or at generate time. If set to `false` and combined with `static` target, generated pages will simply display a loading screen with no content.
-   * @default true
+   * The plugins directory, each file of which will be auto-registered as a Dtwo plugin.
+   * 
+   * @default "plugins"
   */
-  ssr: boolean,
+  plugins: string,
 
   /**
-   * Modules are Dtwo extensions which can extend its core functionality and add endless integrations.
-   * Each module is either a string (which can refer to a package, or be a path to a file), a tuple with the module as first string and the options as a second object, or an inline module function.
-   * Dtwo tries to resolve each item in the modules array using node require path (in `node_modules`) and then will be resolved from project `srcDir` if `~` alias is used.
+   * The directory containing your static files, which will be directly accessible via the Dtwo server and copied across into your `dist` folder when your app is generated.
    * 
-   * @note Modules are executed sequentially so the order is important.
+   * @default "public"
+  */
+  public: string,
+
+  /**
+   * @default "public"
    * 
-   * @example
-   * ```js
-   * modules: [
-   *   // Using package name
-   *   '@dtwojs/axios',
-   *   // Relative to your project srcDir
-   *   '~/modules/awesome.js',
-   *   // Providing options
-   *   ['@dtwojs/google-analytics', { ua: 'X1234567' }],
-   *   // Inline definition
-   *   function () {}
-   * ]
-   * ```
+   * @deprecated use `dir.public` option instead
   */
-  modules: (DtwoModule | string | [DtwoModule | string, Record<string, any>])[],
-
-  /**
-   * Customize default directory structure used by Dtwo.
-   * It is better to stick with defaults unless needed.
-  */
-  dir: {
-    /**
-     * The assets directory (aliased as `~assets` in your build).
-     * @default "assets"
-    */
-    assets: string,
-
-    /**
-     * The layouts directory, each file of which will be auto-registered as a Dtwo layout.
-     * @default "layouts"
-    */
-    layouts: string,
-
-    /**
-     * The middleware directory, each file of which will be auto-registered as a Dtwo middleware.
-     * @default "middleware"
-    */
-    middleware: string,
-
-    /**
-     * The directory which will be processed to auto-generate your application page routes.
-     * @default "pages"
-    */
-    pages: string,
-
-    /**
-     * The plugins directory, each file of which will be auto-registered as a Dtwo plugin.
-     * @default "plugins"
-    */
-    plugins: string,
-
-    /**
-     * The directory containing your static files, which will be directly accessible via the Dtwo server and copied across into your `dist` folder when your app is generated.
-     * @default "public"
-    */
-    public: string,
-
-    /**
-     * @default "public"
-     * 
-     * @deprecated use `dir.public` option instead
-    */
-    static: string,
-  },
+  static: string,
+ },
+
+ /**
+  * The extensions that should be resolved by the Dtwo resolver.
+  * 
+  * @default [".js",".jsx",".mjs",".ts",".tsx",".kdu"]
+ */
+ extensions: Array<string>,
+
+ /**
+  * You can improve your DX by defining additional aliases to access custom directories within your JavaScript and CSS.
+  * 
+  * 
+  * @note Within a webpack context (image sources, CSS - but not JavaScript) you _must_ access
+  * your alias by prefixing it with `~`.
+  * 
+  * @note These aliases will be automatically added to the generated `.dtwo/tsconfig.json` so you can get full
+  * type support and path auto-complete. In case you need to extend options provided by `./.dtwo/tsconfig.json`
+  * further, make sure to add them here or within the `typescript.tsConfig` property in `dtwo.config`.
+  * 
+  * @example
+  * ```js
+  * export default {
+  *   alias: {
+  *     'images': fileURLToPath(new URL('./assets/images', import.meta.url)),
+  *     'style': fileURLToPath(new URL('./assets/style', import.meta.url)),
+  *     'data': fileURLToPath(new URL('./assets/other/data', import.meta.url))
+  *   }
+  * }
+  * ```
+  * 
+  * ```html
+  * <template>
+  *   <img src="~images/main-bg.jpg">
+  * </template>
+  * 
+  * <script>
+  * import data from 'data/test.json'
+  * </script>
+  * 
+  * <style>
+  * // Uncomment the below
+  * //@import '~style/variables.scss';
+  * //@import '~style/utils.scss';
+  * //@import '~style/base.scss';
+  * body {
+  *   background-image: url('~images/main-bg.jpg');
+  * }
+  * </style>
+  * ```
+ */
+ alias: Record<string, string>,
+
+ /**
+  * Pass options directly to `node-ignore` (which is used by Dtwo to ignore files).
+  * 
+  * 
+  * @see [node-ignore](https://github.com/kaelzhang/node-ignore)
+  * 
+  * @example
+  * ```js
+  * ignoreOptions: {
+  *   ignorecase: false
+  * }
+  * ```
+ */
+ ignoreOptions: any,
+
+ /**
+  * Any file in `pages/`, `layouts/`, `middleware/` or `store/` will be ignored during building if its filename starts with the prefix specified by `ignorePrefix`.
+  * 
+  * @default "-"
+ */
+ ignorePrefix: string,
+
+ /**
+  * More customizable than `ignorePrefix`: all files matching glob patterns specified inside the `ignore` array will be ignored in building.
+  * 
+  * @default ["**\/*.stories.{js,ts,jsx,tsx}","**\/*.{spec,test}.{js,ts,jsx,tsx}","**\/*.d.ts",".output","**\/-*.*"]
+ */
+ ignore: Array<string>,
+
+ /**
+  * The watchers property lets you overwrite watchers configuration in your `dtwo.config`.
+  * 
+ */
+ watchers: {
+  /**
+   * An array of event types, which, when received, will cause the watcher to restart.
+   * 
+  */
+  rewatchOnRawEvents: any,
 
   /**
-   * The extensions that should be resolved by the Dtwo resolver.
-   * @default [".js",".jsx",".mjs",".ts",".tsx",".kdu"]
+   * `watchOptions` to pass directly to webpack.
+   * 
+   * 
+   * @see [webpack@4 watch options](https://v4.webpack.js.org/configuration/watch/#watchoptions).
   */
-  extensions: Array<string>,
+  webpack: {
+   /** @default 1000 */
+   aggregateTimeout: number,
+  },
 
   /**
-   * You can improve your DX by defining additional aliases to access custom directories within your JavaScript and CSS.
+   * Options to pass directly to `chokidar`.
+   * 
    * 
-   * @note Within a webpack context (image sources, CSS - but not JavaScript) you _must_ access
-   * your alias by prefixing it with `~`.
+   * @see [chokidar](https://github.com/paulmillr/chokidar#api)
+  */
+  chokidar: {
+   /** @default true */
+   ignoreInitial: boolean,
+  },
+ },
+
+ /**
+  * Hooks are listeners to Dtwo events that are typically used in modules, but are also available in `dtwo.config`.
+  * 
+  * Internally, hooks follow a naming pattern using colons (e.g., build:done).
+  * For ease of configuration, you can also structure them as an hierarchical object in `dtwo.config` (as below).
+  * 
+  * 
+  * @example
+  * ```js'node:fs'
+  * import fs from 'node:fs'
+  * import path from 'node:path'
+  * export default {
+  *   hooks: {
+  *     build: {
+  *       done(builder) {
+  *         const extraFilePath = path.join(
+  *           builder.dtwo.options.buildDir,
+  *           'extra-file'
+  *         )
+  *         fs.writeFileSync(extraFilePath, 'Something extra')
+  *       }
+  *     }
+  *   }
+  * }
+  * ```
+ */
+ hooks: DtwoHooks,
+
+ /**
+  * Runtime config allows passing dynamic config and environment variables to the Dtwo app context.
+  * 
+  * The value of this object is accessible from server only using `useRuntimeConfig`.
+  * It mainly should hold _private_ configuration which is not exposed on the frontend. This could include a reference to your API secret tokens.
+  * Anything under `public` and `app` will be exposed to the frontend as well.
+  * Values are automatically replaced by matching env variables at runtime, e.g. setting an environment variable `DTWO_API_KEY=my-api-key DTWO_PUBLIC_BASE_URL=/foo/` would overwrite the two values in the example below.
+  * 
+  * 
+  * @example
+  * ```js
+  * export default {
+  *  runtimeConfig: {
+  *     apiKey: '' // Default to an empty string, automatically set at runtime using process.env.DTWO_API_KEY
+  *     public: {
+  *        baseURL: '' // Exposed to the frontend as well.
+  *     }
+  *   }
+  * }
+  * ```
+ */
+ runtimeConfig: RuntimeConfig,
+
+ /**
+  * Additional app configuration
+  * 
+  * For programmatic usage and type support, you can directly provide app config with this option. It will be merged with `app.config` file as default value.
+  * 
+ */
+ appConfig: AppConfig,
+
+ devServer: {
+  /**
+   * Whether to enable HTTPS.
    * 
-   * @note These aliases will be automatically added to the generated `.dtwo/tsconfig.json` so you can get full
-   * type support and path auto-complete. In case you need to extend options provided by `./.dtwo/tsconfig.json`
-   * further, make sure to add them here or within the `typescript.tsConfig` property in `dtwo.config`.
+   * @default false
    * 
    * @example
-   * ```js
+   * ```
+   * import { fileURLToPath } from 'node:url'
    * export default {
-   *   alias: {
-   *     'images': fileURLToPath(new URL('./assets/images', import.meta.url)),
-   *     'style': fileURLToPath(new URL('./assets/style', import.meta.url)),
-   *     'data': fileURLToPath(new URL('./assets/other/data', import.meta.url))
+   *   server: {
+   *     https: {
+   *       key: fs.readFileSync(fileURLToPath(new URL('./server.key', import.meta.url))),
+   *       cert: fs.readFileSync(fileURLToPath(new URL('./server.crt', import.meta.url)))
+   *     }
    *   }
    * }
    * ```
-   * 
-   * ```html
-   * <template>
-   *   <img src="~images/main-bg.jpg">
-   * </template>
-   * 
-   * <script>
-   * import data from 'data/test.json'
-   * </script>
-   * 
-   * <style>
-   * // Uncomment the below
-   * //@import '~style/variables.scss';
-   * //@import '~style/utils.scss';
-   * //@import '~style/base.scss';
-   * body {
-   *   background-image: url('~images/main-bg.jpg');
-   * }
-   * </style>
-   * ```
   */
-  alias: Record<string, string>,
+  https: false | { key: string; cert: string },
 
   /**
-   * Pass options directly to `node-ignore` (which is used by Dtwo to ignore files).
+   * Dev server listening port
    * 
-   * @see [node-ignore](https://github.com/kaelzhang/node-ignore)
-   * 
-   * @example
-   * ```js
-   * ignoreOptions: {
-   *   ignorecase: false
-   * }
-   * ```
+   * @default 3000
   */
-  ignoreOptions: any,
+  port: number,
 
   /**
-   * Any file in `pages/`, `layouts/`, `middleware/` or `store/` will be ignored during building if its filename starts with the prefix specified by `ignorePrefix`.
-   * @default "-"
+   * Dev server listening host
+   * 
+   * @default "localhost"
   */
-  ignorePrefix: string,
+  host: string,
 
   /**
-   * More customizable than `ignorePrefix`: all files matching glob patterns specified inside the `ignore` array will be ignored in building.
-   * @default ["**\/*.stories.{js,ts,jsx,tsx}","**\/*.{spec,test}.{js,ts,jsx,tsx}","**\/*.d.ts",".output","**\/-*.*"]
+   * Listening dev server url
+   * 
+   * @default "http://localhost:3000"
   */
-  ignore: Array<string>,
-
-  /** The watchers property lets you overwrite watchers configuration in your `dtwo.config`. */
-  watchers: {
-    /** An array of event types, which, when received, will cause the watcher to restart. */
-    rewatchOnRawEvents: any,
-
-    /**
-     * `watchOptions` to pass directly to webpack.
-     * 
-     * @see [webpack@4 watch options](https://v4.webpack.js.org/configuration/watch/#watchoptions).
-    */
-    webpack: {
-       /** @default 1000 */
-       aggregateTimeout: number,
-    },
-
-    /**
-     * Options to pass directly to `chokidar`.
-     * 
-     * @see [chokidar](https://github.com/paulmillr/chokidar#api)
-    */
-    chokidar: {
-       /** @default true */
-       ignoreInitial: boolean,
-    },
-  },
+  url: string,
+ },
 
+ experimental: {
   /**
-   * Hooks are listeners to Dtwo events that are typically used in modules, but are also available in `dtwo.config`.
-   * Internally, hooks follow a naming pattern using colons (e.g., build:done).
-   * For ease of configuration, you can also structure them as an hierarchical object in `dtwo.config` (as below).
+   * Set to true to generate an async entry point for the Kdu bundle (for module federation support).
    * 
-   * @example
-   * ```js'node:fs'
-   * import fs from 'node:fs'
-   * import path from 'node:path'
-   * export default {
-   *   hooks: {
-   *     build: {
-   *       done(builder) {
-   *         const extraFilePath = path.join(
-   *           builder.dtwo.options.buildDir,
-   *           'extra-file'
-   *         )
-   *         fs.writeFileSync(extraFilePath, 'Something extra')
-   *       }
-   *     }
-   *   }
-   * }
-   * ```
+   * @default false
   */
-  hooks: DtwoHooks,
+  asyncEntry: boolean,
 
   /**
-   * Runtime config allows passing dynamic config and environment variables to the Dtwo app context.
-   * The value of this object is accessible from server only using `useRuntimeConfig`.
-   * It mainly should hold _private_ configuration which is not exposed on the frontend. This could include a reference to your API secret tokens.
-   * Anything under `public` and `app` will be exposed to the frontend as well.
-   * Values are automatically replaced by matching env variables at runtime, e.g. setting an environment variable `DTWO_API_KEY=my-api-key DTWO_PUBLIC_BASE_URL=/foo/` would overwrite the two values in the example below.
+   * Enable Kdu's reactivity transform
    * 
-   * @example
-   * ```js
-   * export default {
-   *  runtimeConfig: {
-   *     apiKey: '' // Default to an empty string, automatically set at runtime using process.env.DTWO_API_KEY
-   *     public: {
-   *        baseURL: '' // Exposed to the frontend as well.
-   *     }
-   *   }
-   * }
-   * ```
+   * @default false
+   * 
+   * @see https://kdu-js.web.app/guide/extras/reactivity-transform.html
   */
-  runtimeConfig: RuntimeConfig,
-
-  /**
-   * Additional app configuration
-   * For programmatic usage and type support, you can directly provide app config with this option. It will be merged with `app.config` file as default value.
-  */
-  appConfig: AppConfig,
-
-  devServer: {
-    /**
-     * Whether to enable HTTPS.
-     * @default false
-     * 
-     * @example
-     * ```
-     * import { fileURLToPath } from 'node:url'
-     * export default {
-     *   server: {
-     *     https: {
-     *       key: fs.readFileSync(fileURLToPath(new URL('./server.key', import.meta.url))),
-     *       cert: fs.readFileSync(fileURLToPath(new URL('./server.crt', import.meta.url)))
-     *     }
-     *   }
-     * }
-     * ```
-    */
-    https: false | { key: string; cert: string },
-
-    /**
-     * Dev server listening port
-     * @default 3000
-    */
-    port: number,
-
-    /**
-     * Dev server listening host
-     * @default "localhost"
-    */
-    host: string,
-
-    /**
-     * Listening dev server url
-     * @default "http://localhost:3000"
-    */
-    url: string,
-  },
+  reactivityTransform: boolean,
 
-  experimental: {
-    /**
-     * Set to true to generate an async entry point for the Kdu bundle (for module federation support).
-     * @default false
-    */
-    asyncEntry: boolean,
-
-    /**
-     * Enable Kdu's reactivity transform
-     * @default false
-     * 
-     * @see https://kdu-js.web.app/guide/extras/reactivity-transform.html
-    */
-    reactivityTransform: boolean,
-
-    /**
-     * Externalize `kdu`, `@kdujs/*` and `kdu-router` when building.
-     * @default true
-    */
-    externalKdu: boolean,
-
-    /**
-     * Tree shakes contents of client-only components from server bundle.
-     * @default true
-    */
-    treeshakeClientOnly: boolean,
-
-    /**
-     * Use wite-node for on-demand server chunk loading
-     * @default true
-     * 
-     * @deprecated use `wite.devBundler: 'wite-node'`
-    */
-    witeNode: boolean,
-
-    /**
-     * Split server bundle into multiple chunks and dynamically import them.
-     * @default true
-    */
-    witeServerDynamicImports: boolean,
-
-    /**
-     * Inline styles when rendering HTML (currently wite only).
-     * You can also pass a function that receives the path of a Kdu component and returns a boolean indicating whether to inline the styles for that component.
-     * @default true
-    */
-    inlineSSRStyles: boolean | ((id?: string) => boolean),
-
-    /**
-     * Turn off rendering of Dtwo scripts and JS resource hints.
-     * @default false
-    */
-    noScripts: boolean,
-
-    /**
-     * When this option is enabled (by default) payload of pages generated with `dtwo generate` are extracted
-     * @default false
-    */
-    payloadExtraction: boolean,
-
-    /**
-     * Enable cross-origin prefetch using the Speculation Rules API.
-     * @default false
-    */
-    crossOriginPrefetch: boolean,
-
-    /**
-     * Write early hints when using node server.
-     * @default false
-     * 
-     * @note nginx does not support 103 Early hints in the current version.
-    */
-    writeEarlyHints: boolean,
-  },
+  /**
+   * Externalize `kdu`, `@kdujs/*` and `kdu-router` when building.
+   * 
+   * @default true
+  */
+  externalKdu: boolean,
 
-  generate: {
-    /**
-     * The routes to generate.
-     * If you are using the crawler, this will be only the starting point for route generation. This is often necessary when using dynamic routes.
-     * It can be an array or a function.
-     * 
-     * @example
-     * ```js
-     * routes: ['/users/1', '/users/2', '/users/3']
-     * ```
-     * 
-     * You can pass a function that returns a promise or a function that takes a callback. It should
-     * return an array of strings or objects with `route` and (optional) `payload` keys.
-     * 
-     * @example
-     * ```js
-     * export default {
-     *   generate: {
-     *     async routes() {
-     *       const res = await axios.get('https://my-api/users')
-     *       return res.data.map(user => ({ route: '/users/' + user.id, payload: user }))
-     *     }
-     *   }
-     * }
-     * ```
-     * Or instead:
-     * ```js
-     * export default {
-     *   generate: {
-     *     routes(callback) {
-     *       axios
-     *         .get('https://my-api/users')
-     *         .then(res => {
-     *           const routes = res.data.map(user => '/users/' + user.id)
-     *           callback(null, routes)
-     *         })
-     *         .catch(callback)
-     *     }
-     *   }
-     * }
-     * ```
-     * 
-     * If `routes()` returns a payload, it can be accessed from the Dtwo context.
-     * 
-     * @example
-     * ```js
-     * export default {
-     *   async useAsyncData ({ params, error, payload }) {
-     *     if (payload) return { user: payload }
-     *     else return { user: await backend.fetchUser(params.id) }
-     *   }
-     * }
-     * ```
-    */
-    routes: Array<any>,
-
-    /** An array of string or regular expressions that will prevent generation of routes matching them. The routes will still be accessible when `fallback` is set. */
-    exclude: Array<any>,
-  },
+  /**
+   * Tree shakes contents of client-only components from server bundle.
+   * 
+   * @default true
+  */
+  treeshakeClientOnly: boolean,
 
   /**
-   * @default 3
+   * Use wite-node for on-demand server chunk loading
+   * 
+   * @default true
    * 
-   * @private
+   * @deprecated use `wite.devBundler: 'wite-node'`
   */
-  _majorVersion: number,
+  witeNode: boolean,
 
   /**
-   * @default false
+   * Split server bundle into multiple chunks and dynamically import them.
    * 
-   * @private
+   * @default true
   */
-  _legacyGenerate: boolean,
+  witeServerDynamicImports: boolean,
 
   /**
-   * @default false
+   * Inline styles when rendering HTML (currently wite only).
+   * 
+   * You can also pass a function that receives the path of a Kdu component and returns a boolean indicating whether to inline the styles for that component.
    * 
-   * @private
+   * @default true
   */
-  _start: boolean,
+  inlineSSRStyles: boolean | ((id?: string) => boolean),
 
   /**
-   * @default false
+   * Turn off rendering of Dtwo scripts and JS resource hints.
    * 
-   * @private
+   * @default false
   */
-  _build: boolean,
+  noScripts: boolean,
 
   /**
+   * When this option is enabled (by default) payload of pages generated with `dtwo generate` are extracted
+   * 
    * @default false
+  */
+  payloadExtraction: boolean,
+
+  /**
+   * Enable cross-origin prefetch using the Speculation Rules API.
    * 
-   * @private
+   * @default false
   */
-  _generate: boolean,
+  crossOriginPrefetch: boolean,
 
   /**
+   * Write early hints when using node server.
+   * 
    * @default false
    * 
-   * @private
+   * @note nginx does not support 103 Early hints in the current version.
   */
-  _prepare: boolean,
+  writeEarlyHints: boolean,
 
   /**
+   * Experimental component islands support with <DtwoIsland> and .island.kdu files.
+   * 
    * @default false
+  */
+  componentIslands: boolean,
+
+  /**
+   * Enable experimental config schema support
    * 
-   * @private
+   * @default false
   */
-  _cli: boolean,
+  configSchema: boolean,
+ },
 
+ generate: {
   /**
+   * The routes to generate.
+   * 
+   * If you are using the crawler, this will be only the starting point for route generation. This is often necessary when using dynamic routes.
+   * It is preferred to use `hole.prerender.routes`.
    * 
-   * @private
+   * 
+   * @example
+   * ```js
+   * routes: ['/users/1', '/users/2', '/users/3']
+   * ```
   */
-  _requiredModules: any,
+  routes: Array<any>,
 
   /**
+   * This option is no longer used. Instead, use `hole.prerender.ignore`.
+   * 
+  */
+  exclude: Array<any>,
+ },
+
+ /**
+  * @default 3
+  * 
+  * @private
+ */
+ _majorVersion: number,
+
+ /**
+  * @default false
+  * 
+  * @private
+ */
+ _legacyGenerate: boolean,
+
+ /**
+  * @default false
+  * 
+  * @private
+ */
+ _start: boolean,
+
+ /**
+  * @default false
+  * 
+  * @private
+ */
+ _build: boolean,
+
+ /**
+  * @default false
+  * 
+  * @private
+ */
+ _generate: boolean,
+
+ /**
+  * @default false
+  * 
+  * @private
+ */
+ _prepare: boolean,
+
+ /**
+  * @default false
+  * 
+  * @private
+ */
+ _cli: boolean,
+
+ /**
+  * 
+  * @private
+ */
+ _requiredModules: any,
+
+ /**
+  * 
+  * @private
+ */
+ _dtwoConfigFile: any,
+
+ /**
+  * 
+  * @private
+ */
+ _dtwoConfigFiles: Array<any>,
+
+ /**
+  * @default ""
+  * 
+  * @private
+ */
+ appDir: string,
+
+ /**
+  * 
+  * @private
+ */
+ _installedModules: Array<any>,
+
+ /**
+  * 
+  * @private
+ */
+ _modules: Array<any>,
+
+ /**
+  * Configuration for Hole.
+  * 
+  * 
+  * @see https://holepack.web.app/config/
+ */
+ hole: HoleConfig,
+
+ /**
+  * Global route options applied to matching server routes.
+  * 
+  * 
+  * @experimental This is an experimental feature and API may change in the future.
+  * 
+  * @see https://holepack.web.app/config/#routes
+ */
+ routeRules: HoleConfig['routeRules'],
+
+ /**
+  * Hole server handlers.
+  * 
+  * Each handler accepts the following options: - handler: The path to the file defining the handler. - route: The route under which the handler is available. This follows the conventions of https://github.com/unjs/radix3. - method: The HTTP method of requests that should be handled. - middleware: Specifies whether it is a middleware handler. - lazy: Specifies whether to use lazy loading to import the handler.
+  * 
+  * 
+  * @see https://dtwojs.web.app/docs/guide/directory-structure/server
+  * 
+  * @note Files from `server/api`, `server/middleware` and `server/routes` will be automatically registered by Dtwo.
+  * 
+  * @example
+  * ```js
+  * serverHandlers: [
+  *   { route: '/path/foo/**:name', handler: '~/server/foohandler.ts' }
+  * ]
+  * ```
+ */
+ serverHandlers: HoleEventHandler[],
+
+ /**
+  * Hole development-only server handlers.
+  * 
+  * 
+  * @see https://holepack.web.app/guide/introduction/routing
+ */
+ devServerHandlers: HoleDevEventHandler[],
+
+ postcss: {
+  /**
+   * Options for configuring PostCSS plugins.
+   * 
+   * https://postcss.org/
    * 
-   * @private
   */
-  _dtwoConfigFile: any,
+  plugins: Record<string, any>,
+ },
 
+ router: {
+  /**
+   * Additional options passed to `kdu-router`.
+   * 
+   * Note: Only JSON serializable options should be passed by dtwo config.
+   * For more control, you can use `app/router.options.ts` file.
+   * 
+   * 
+   * @see [documentation](https://kdujs-router.web.app/api/interfaces/routeroptions.html).
+  */
+  options: import('../src/types/router').RouterConfigSerializable,
+ },
+
+ /**
+  * Configuration for Dtwo's TypeScript integration.
+  * 
+ */
+ typescript: {
   /**
+   * TypeScript comes with certain checks to give you more safety and analysis of your program. Once you’ve converted your codebase to TypeScript, you can start enabling these checks for greater safety. [Read More](https://www.typescriptlang.org/docs/handbook/migrating-from-javascript.html#getting-stricter-checks)
    * 
-   * @private
+   * @default true
   */
-  _dtwoConfigFiles: Array<any>,
+  strict: boolean,
 
   /**
-   * @default ""
+   * Include parent workspace in the Dtwo project. Mostly useful for themes and module authors.
    * 
-   * @private
+   * @default false
   */
-  appDir: string,
+  includeWorkspace: boolean,
 
   /**
+   * Enable build-time type checking.
    * 
-   * @private
+   * If set to true, this will type check in development. You can restrict this to build-time type checking by setting it to `build`. Requires to install `typescript` and `kdu-tsc` as dev dependencies.
+   * 
+   * @default false
+   * 
+   * @see https://dtwojs.web.app/docs/guide/concepts/typescript
   */
-  _installedModules: Array<any>,
+  typeCheck: boolean | 'build',
 
   /**
+   * You can extend generated `.dtwo/tsconfig.json` using this option.
    * 
-   * @private
   */
-  _modules: Array<any>,
+  tsConfig: readPackageJSON,
 
   /**
-   * Configuration for Hole.
+   * Generate a `*.kdu` shim.
+   * 
+   * We recommend instead either enabling [**Take Over Mode**](https://kdu-js.web.app/guide/typescript/overview.html#kocan-takeover-mode) or adding TypeScript Kdu Plugin (Kocan)** 👉 [[Download](https://marketplace.visualstudio.com/items?itemName=Kdu-Code.vscode-typescript-kdu-plugin)].
+   * 
+   * @default true
+  */
+  shim: boolean,
+ },
+
+ /**
+  * Configuration that will be passed directly to Wite.
+  * 
+  * See https://witejs.web.app/config for more information. Please note that not all wite options are supported in Dtwo.
+  * 
+ */
+ wite: WiteConfig,
+
+ webpack: {
+  /**
+   * Dtwo uses `webpack-bundle-analyzer` to visualize your bundles and how to optimize them.
+   * 
+   * Set to `true` to enable bundle analysis, or pass an object with options: [for webpack](https://github.com/webpack-contrib/webpack-bundle-analyzer#options-for-plugin) or [for wite](https://github.com/btd/rollup-plugin-visualizer#options).
    * 
-   * @see https://holepack.web.app/config/
+   * @default false
+   * 
+   * @example
+   * ```js
+   * analyze: {
+   *   analyzerMode: 'static'
+   * }
+   * ```
   */
-  hole: HoleConfig,
+  analyze: boolean | BundleAnalyzerPlugin.Options,
 
   /**
-   * Global route options applied to matching server routes.
+   * Enable the profiler in webpackbar.
+   * 
+   * It is normally enabled by CLI argument `--profile`.
    * 
-   * @experimental This is an experimental feature and API may change in the future.
+   * @default false
    * 
-   * @see https://holepack.web.app/config/#routes
+   * @see [webpackbar](https://github.com/unjs/webpackbar#profile).
   */
-  routeRules: HoleConfig['routeRules'],
+  profile: boolean,
 
   /**
-   * Hole server handlers.
-   * Each handler accepts the following options: - handler: The path to the file defining the handler. - route: The route under which the handler is available. This follows the conventions of https://github.com/unjs/radix3. - method: The HTTP method of requests that should be handled. - middleware: Specifies whether it is a middleware handler. - lazy: Specifies whether to use lazy loading to import the handler.
+   * Enables Common CSS Extraction using [Kdu Server Renderer guidelines](https://kdujs-ssr.web.app/guide/css.html).
    * 
-   * @note Files from `server/api`, `server/middleware` and `server/routes` will be automatically registered by Dtwo.
+   * Using [extract-css-chunks-webpack-plugin](https://github.com/faceyspacey/extract-css-chunks-webpack-plugin/) under the hood, your CSS will be extracted into separate files, usually one per component. This allows caching your CSS and JavaScript separately and is worth trying if you have a lot of global or shared CSS.
+   * 
+   * @default true
    * 
    * @example
    * ```js
-   * serverHandlers: [
-   *   { route: '/path/foo/**:name', handler: '~/server/foohandler.ts' }
-   * ]
+   * export default {
+   *   webpack: {
+   *     extractCSS: true,
+   *     // or
+   *     extractCSS: {
+   *       ignoreOrder: true
+   *     }
+   *   }
+   * }
+   * ```
+   * 
+   * If you want to extract all your CSS to a single file, there is a workaround for this.
+   * However, note that it is not recommended to extract everything into a single file.
+   * Extracting into multiple CSS files is better for caching and preload isolation. It
+   * can also improve page performance by downloading and resolving only those resources
+   * that are needed.
+   * 
+   * @example
+   * ```js
+   * export default {
+   *   webpack: {
+   *     extractCSS: true,
+   *     optimization: {
+   *       splitChunks: {
+   *         cacheGroups: {
+   *           styles: {
+   *             name: 'styles',
+   *             test: /\.(css|kdu)$/,
+   *             chunks: 'all',
+   *             enforce: true
+   *           }
+   *         }
+   *       }
+   *     }
+   *   }
+   * }
    * ```
   */
-  serverHandlers: HoleEventHandler[],
+  extractCSS: boolean | PluginOptions,
 
   /**
-   * Hole development-only server handlers.
+   * Enables CSS source map support (defaults to `true` in development).
    * 
-   * @see https://holepack.web.app/guide/introduction/routing
+   * @default false
   */
-  devServerHandlers: HoleDevEventHandler[],
+  cssSourceMap: boolean,
 
-  postcss: {
-    /**
-     * Path to postcss config file.
-     * @default false
-    */
-    config: boolean,
-
-    /**
-     * Options for configuring PostCSS plugins.
-     * https://postcss.org/
-    */
-    plugins: Record<string, any>,
-  },
+  /**
+   * The polyfill library to load to provide URL and URLSearchParams.
+   * 
+   * Defaults to `'url'` ([see package](https://www.npmjs.com/package/url)).
+   * 
+   * @default "url"
+  */
+  serverURLPolyfill: string,
 
-  router: {
-    /**
-     * Additional options passed to `kdu-router`.
-     * Note: Only JSON serializable options should be passed by dtwo config.
-     * For more control, you can use `app/router.options.ts` file.
-     * 
-     * @see [documentation](https://kdujs-router.web.app/api/interfaces/routeroptions.html).
-    */
-    options: import('../src/types/router').RouterConfigSerializable,
-  },
+  /**
+   * Customize bundle filenames.
+   * 
+   * To understand a bit more about the use of manifests, take a look at [this webpack documentation](https://webpack.js.org/guides/code-splitting/).
+   * 
+   * 
+   * @note Be careful when using non-hashed based filenames in production
+   * as most browsers will cache the asset and not detect the changes on first load.
+   * 
+   * This example changes fancy chunk names to numerical ids:
+   * 
+   * @example
+   * ```js
+   * filenames: {
+   *   chunk: ({ isDev }) => (isDev ? '[name].js' : '[id].[contenthash].js')
+   * }
+   * ```
+  */
+  filenames: {
+   app: () => any,
+
+   chunk: () => any,
+
+   css: () => any,
+
+   img: () => any,
+
+   font: () => any,
 
-  /** Configuration for Dtwo's TypeScript integration. */
-  typescript: {
-    /**
-     * TypeScript comes with certain checks to give you more safety and analysis of your program. Once you’ve converted your codebase to TypeScript, you can start enabling these checks for greater safety. [Read More](https://www.typescriptlang.org/docs/handbook/migrating-from-javascript.html#getting-stricter-checks)
-     * @default true
-    */
-    strict: boolean,
-
-    /**
-     * Include parent workspace in the Dtwo project. Mostly useful for themes and module authors.
-     * @default false
-    */
-    includeWorkspace: boolean,
-
-    /**
-     * Enable build-time type checking.
-     * If set to true, this will type check in development. You can restrict this to build-time type checking by setting it to `build`. Requires to install `typescript` and `kdu-tsc` as dev dependencies.
-     * @default false
-    */
-    typeCheck: boolean | 'build',
-
-    /** You can extend generated `.dtwo/tsconfig.json` using this option. */
-    tsConfig: readPackageJSON,
-
-    /**
-     * Generate a `*.kdu` shim.
-     * We recommend instead either enabling [**Take Over Mode**](https://kdu-js.web.app/guide/typescript/overview.html#kocan-takeover-mode) or adding TypeScript Kdu Plugin (Kocan)** 👉 [[Download](https://marketplace.visualstudio.com/items?itemName=Kdu-Code.vscode-typescript-kdu-plugin)].
-     * @default true
-    */
-    shim: boolean,
+   video: () => any,
   },
 
   /**
-   * Configuration that will be passed directly to Wite.
-   * See https://witejs.web.app/config for more information. Please note that not all wite options are supported in Dtwo.
+   * Customize the options of Dtwo's integrated webpack loaders.
+   * 
   */
-  wite: WiteConfig,
+  loaders: {
+   file: {
+    /** @default false */
+    esModule: boolean,
+   },
 
-  webpack: {
-    /**
-     * Dtwo uses `webpack-bundle-analyzer` to visualize your bundles and how to optimize them.
-     * Set to `true` to enable bundle analysis, or pass an object with options: [for webpack](https://github.com/webpack-contrib/webpack-bundle-analyzer#options-for-plugin) or [for wite](https://github.com/btd/rollup-plugin-visualizer#options).
-     * @default false
-     * 
-     * @example
-     * ```js
-     * analyze: {
-     *   analyzerMode: 'static'
-     * }
-     * ```
-    */
-    analyze: boolean | BundleAnalyzerPlugin.Options,
-
-    /**
-     * Enable the profiler in webpackbar.
-     * It is normally enabled by CLI argument `--profile`.
-     * @default false
-     * 
-     * @see [webpackbar](https://github.com/unjs/webpackbar#profile).
-    */
-    profile: boolean,
-
-    /**
-     * Enables Common CSS Extraction using [Kdu Server Renderer guidelines](https://kdujs-ssr.web.app/guide/css.html).
-     * Using [extract-css-chunks-webpack-plugin](https://github.com/faceyspacey/extract-css-chunks-webpack-plugin/) under the hood, your CSS will be extracted into separate files, usually one per component. This allows caching your CSS and JavaScript separately and is worth trying if you have a lot of global or shared CSS.
-     * @default true
-     * 
-     * @example
-     * ```js
-     * export default {
-     *   webpack: {
-     *     extractCSS: true,
-     *     // or
-     *     extractCSS: {
-     *       ignoreOrder: true
-     *     }
-     *   }
-     * }
-     * ```
-     * 
-     * If you want to extract all your CSS to a single file, there is a workaround for this.
-     * However, note that it is not recommended to extract everything into a single file.
-     * Extracting into multiple CSS files is better for caching and preload isolation. It
-     * can also improve page performance by downloading and resolving only those resources
-     * that are needed.
-     * 
-     * @example
-     * ```js
-     * export default {
-     *   webpack: {
-     *     extractCSS: true,
-     *     optimization: {
-     *       splitChunks: {
-     *         cacheGroups: {
-     *           styles: {
-     *             name: 'styles',
-     *             test: /\.(css|kdu)$/,
-     *             chunks: 'all',
-     *             enforce: true
-     *           }
-     *         }
-     *       }
-     *     }
-     *   }
-     * }
-     * ```
-    */
-    extractCSS: boolean | PluginOptions,
-
-    /**
-     * Enables CSS source map support (defaults to `true` in development).
-     * @default false
-    */
-    cssSourceMap: boolean,
-
-    /**
-     * The polyfill library to load to provide URL and URLSearchParams.
-     * Defaults to `'url'` ([see package](https://www.npmjs.com/package/url)).
-     * @default "url"
-    */
-    serverURLPolyfill: string,
-
-    /**
-     * Customize bundle filenames.
-     * To understand a bit more about the use of manifests, take a look at [this webpack documentation](https://webpack.js.org/guides/code-splitting/).
-     * 
-     * @note Be careful when using non-hashed based filenames in production
-     * as most browsers will cache the asset and not detect the changes on first load.
-     * 
-     * This example changes fancy chunk names to numerical ids:
-     * 
-     * @example
-     * ```js
-     * filenames: {
-     *   chunk: ({ isDev }) => (isDev ? '[name].js' : '[id].[contenthash].js')
-     * }
-     * ```
-    */
-    filenames: {
-       app: () => any,
-
-       chunk: () => any,
-
-       css: () => any,
-
-       img: () => any,
-
-       font: () => any,
-
-       video: () => any,
-    },
+   fontUrl: {
+    /** @default false */
+    esModule: boolean,
 
-    /** Customize the options of Dtwo's integrated webpack loaders. */
-    loaders: {
-       file: {
-           /** @default false */
-           esModule: boolean,
-       },
+    /** @default 1000 */
+    limit: number,
+   },
 
-       fontUrl: {
-           /** @default false */
-           esModule: boolean,
+   imgUrl: {
+    /** @default false */
+    esModule: boolean,
 
-           /** @default 1000 */
-           limit: number,
-       },
+    /** @default 1000 */
+    limit: number,
+   },
 
-       imgUrl: {
-           /** @default false */
-           esModule: boolean,
+   pugPlain: any,
 
-           /** @default 1000 */
-           limit: number,
-       },
+   kdu: {
+    /** @default true */
+    productionMode: boolean,
 
-       pugPlain: any,
+    transformAssetUrls: {
+     /** @default "src" */
+     video: string,
 
-       kdu: {
-           /** @default true */
-           productionMode: boolean,
+     /** @default "src" */
+     source: string,
 
-           transformAssetUrls: {
-                /** @default "src" */
-                video: string,
+     /** @default "src" */
+     object: string,
 
-                /** @default "src" */
-                source: string,
+     /** @default "src" */
+     embed: string,
+    },
 
-                /** @default "src" */
-                object: string,
+    compilerOptions: {
+     [key: string]: any
+    },
+   },
 
-                /** @default "src" */
-                embed: string,
-           },
+   css: {
+    /** @default 0 */
+    importLoaders: number,
 
-           compilerOptions: {
-                [key: string]: any
-           },
-       },
+    url: {
+     filter: () => any,
+    },
 
-       css: {
-           /** @default 0 */
-           importLoaders: number,
+    /** @default false */
+    esModule: boolean,
+   },
 
-           url: {
-                filter: () => any,
-           },
+   cssModules: {
+    /** @default 0 */
+    importLoaders: number,
 
-           /** @default false */
-           esModule: boolean,
-       },
+    url: {
+     filter: () => any,
+    },
 
-       cssModules: {
-           /** @default 0 */
-           importLoaders: number,
+    /** @default false */
+    esModule: boolean,
 
-           url: {
-                filter: () => any,
-           },
+    modules: {
+     /** @default "[local]_[hash:base64:5]" */
+     localIdentName: string,
+    },
+   },
 
-           /** @default false */
-           esModule: boolean,
+   less: any,
 
-           modules: {
-                /** @default "[local]_[hash:base64:5]" */
-                localIdentName: string,
-           },
-       },
+   sass: {
+    sassOptions: {
+     /** @default true */
+     indentedSyntax: boolean,
+    },
+   },
 
-       less: any,
+   scss: any,
 
-       sass: {
-           sassOptions: {
-                /** @default true */
-                indentedSyntax: boolean,
-           },
-       },
+   stylus: any,
 
-       scss: any,
+   kduStyle: any,
+  },
 
-       stylus: any,
+  /**
+   * Add webpack plugins.
+   * 
+   * 
+   * @example
+   * ```js
+   * import webpack from 'webpack'
+   * import { version } from './package.json'
+   * // ...
+   * plugins: [
+   *   new webpack.DefinePlugin({
+   *     'process.VERSION': version
+   *   })
+   * ]
+   * ```
+  */
+  plugins: Array<any>,
 
-       kduStyle: any,
-    },
+  /**
+   * Terser plugin options.
+   * 
+   * Set to false to disable this plugin, or pass an object of options.
+   * 
+   * 
+   * @see [terser-webpack-plugin documentation](https://github.com/webpack-contrib/terser-webpack-plugin).
+   * 
+   * @note Enabling sourceMap will leave `//# sourceMappingURL` linking comment at
+   * the end of each output file if webpack `config.devtool` is set to `source-map`.
+  */
+  terser: false | BasePluginOptions & DefinedDefaultMinimizerAndOptions<any>,
 
-    /**
-     * Add webpack plugins.
-     * 
-     * @example
-     * ```js
-     * import webpack from 'webpack'
-     * import { version } from './package.json'
-     * // ...
-     * plugins: [
-     *   new webpack.DefinePlugin({
-     *     'process.VERSION': version
-     *   })
-     * ]
-     * ```
-    */
-    plugins: Array<any>,
-
-    /**
-     * Terser plugin options.
-     * Set to false to disable this plugin, or pass an object of options.
-     * 
-     * @see [terser-webpack-plugin documentation](https://github.com/webpack-contrib/terser-webpack-plugin).
-     * 
-     * @note Enabling sourceMap will leave `//# sourceMappingURL` linking comment at
-     * the end of each output file if webpack `config.devtool` is set to `source-map`.
-    */
-    terser: false | BasePluginOptions & DefinedDefaultMinimizerAndOptions<any>,
-
-    /**
-     * Hard-replaces `typeof process`, `typeof window` and `typeof document` to tree-shake bundle.
-     * @default false
-    */
-    aggressiveCodeRemoval: boolean,
-
-    /**
-     * OptimizeCSSAssets plugin options.
-     * Defaults to true when `extractCSS` is enabled.
-     * @default false
-     * 
-     * @see [css-minimizer-webpack-plugin documentation](https://github.com/webpack-contrib/css-minimizer-webpack-plugin).
-    */
-    optimizeCSS: false | BasePluginOptions0 & DefinedDefaultMinimizerAndOptions0<any>,
-
-    /** Configure [webpack optimization](https://webpack.js.org/configuration/optimization/). */
-    optimization: false | Configuration['optimization'],
-
-    /** Customize PostCSS Loader. Same options as https://github.com/webpack-contrib/postcss-loader#options */
-    postcss: {
-       execute: any,
-
-       postcssOptions: {
-           /** @default false */
-           config: boolean,
-
-           plugins: {
-                [key: string]: any
-           },
-       },
-
-       sourceMap: any,
-
-       implementation: any,
-
-       /** @default "" */
-       order: string,
-    },
+  /**
+   * Hard-replaces `typeof process`, `typeof window` and `typeof document` to tree-shake bundle.
+   * 
+   * @default false
+  */
+  aggressiveCodeRemoval: boolean,
+
+  /**
+   * OptimizeCSSAssets plugin options.
+   * 
+   * Defaults to true when `extractCSS` is enabled.
+   * 
+   * @default false
+   * 
+   * @see [css-minimizer-webpack-plugin documentation](https://github.com/webpack-contrib/css-minimizer-webpack-plugin).
+  */
+  optimizeCSS: false | BasePluginOptions0 & DefinedDefaultMinimizerAndOptions0<any>,
+
+  /**
+   * Configure [webpack optimization](https://webpack.js.org/configuration/optimization/).
+   * 
+  */
+  optimization: false | Configuration['optimization'],
+
+  /**
+   * Customize PostCSS Loader. Same options as https://github.com/webpack-contrib/postcss-loader#options
+   * 
+  */
+  postcss: {
+   execute: any,
 
-    /** See [webpack-dev-middleware](https://github.com/webpack/webpack-dev-middleware) for available options. */
-    devMiddleware: Options<IncomingMessage, ServerResponse>,
+   postcssOptions: {
+    config: any,
 
-    /** See [webpack-hot-middleware](https://github.com/webpack-contrib/webpack-hot-middleware) for available options. */
-    hotMiddleware: MiddlewareOptions & { client?: ClientOptions },
+    plugins: {
+     [key: string]: any
+    },
+   },
+
+   sourceMap: any,
 
-    /**
-     * Set to `false` to disable the overlay provided by [FriendlyErrorsWebpackPlugin](https://www.npmjs.com/package/@d2js/friendly-errors-webpack-plugin).
-     * @default true
-    */
-    friendlyErrors: boolean,
+   implementation: any,
 
-    /** Filters to hide build warnings. */
-    warningIgnoreFilters: Array<(warn: WebpackError) => boolean>,
+   /** @default "" */
+   order: string,
   },
+
+  /**
+   * See [webpack-dev-middleware](https://github.com/webpack/webpack-dev-middleware) for available options.
+   * 
+  */
+  devMiddleware: Options<IncomingMessage, ServerResponse>,
+
+  /**
+   * See [webpack-hot-middleware](https://github.com/webpack-contrib/webpack-hot-middleware) for available options.
+   * 
+  */
+  hotMiddleware: MiddlewareOptions & { client?: ClientOptions },
+
+  /**
+   * Set to `false` to disable the overlay provided by [FriendlyErrorsWebpackPlugin](https://www.npmjs.com/package/@d2js/friendly-errors-webpack-plugin).
+   * 
+   * @default true
+  */
+  friendlyErrors: boolean,
+
+  /**
+   * Filters to hide build warnings.
+   * 
+  */
+  warningIgnoreFilters: Array<(warn: WebpackError) => boolean>,
+ },
 }