@rindo/core 1.8.12 → 2.5.2

package/dist/declarations/config.d.ts

@@ -1,409 +0,0 @@
-import { CopyTask } from './assets';
-import { DevServerConfig, RindoDevServerConfig } from './dev-server';
-import { Logger } from './logger';
-import { OutputTarget } from './output-targets';
-import { RindoSystem } from './system';
-import { TestingConfig } from './testing';
-/**
- * https://rindojs.web.app/docs/config/
- */
-export interface RindoConfig {
-    /**
-     * By default, Rindo will use the appropriate config to automatically prefix css. For example,
-     * developers can write modern and standard css properties, such as "transform", and Rindo
-     * will automatically add in the prefixed version, such as "-webkit-transform". To disable
-     * autoprefixing css, set this value to `false`.
-     */
-    autoprefixCss?: boolean | any;
-    /**
-     * By default, Rindo will statically analyze the application and generate a component graph of
-     * how all the components are interconnected.
-     *
-     * From the component graph it is able to best decide how components should be grouped
-     * depending on their usage with one another within the app.
-     * By doing so it's able to bundle components together in order to reduce network requests.
-     * However, bundles can be manually generated using the bundles config.
-     *
-     * The bundles config is an array of objects that represent how components are grouped together
-     * in lazy-loaded bundles.
-     * This config is rarely needed as Rindo handles this automatically behind the scenes.
-     */
-    bundles?: ConfigBundle[];
-    /**
-     * The copy config is an array of objects that defines any files or folders that should
-     * be copied over to the build directory.
-     *
-     * Each object in the array must include a src property which can be either an absolute path,
-     * a relative path or a glob pattern. The config can also provide an optional dest property
-     * which can be either an absolute path or a path relative to the build directory.
-     * Also note that any files within src/assets are automatically copied to www/assets for convenience.
-     *
-     * In the copy config below, it will copy the entire directory from src/docs-content over to www/docs-content.
-     *
-     * @deprecated
-     */
-    copy?: CopyTask[];
-    /**
-     * Rindo will cache build results in order to speed up rebuilds.
-     * To disable this feature, set enableCache to false.
-     */
-    enableCache?: boolean;
-    /**
-     * The excludeSrc config setting specifies a set of regular expressions that should be excluded
-     * from the build process.
-     *
-     * The defaults are meant to exclude possible test files that you would not want to include in your final build.
-     */
-    excludeSrc?: string[];
-    /**
-     * Rindo is traditionally used to compile many components into an app,
-     * and each component comes with its own compartmentalized styles.
-     * However, it's still common to have styles which should be "global" across all components and the website.
-     * A global CSS file is often useful to set CSS Variables.
-     *
-     * Additonally, the globalStyle config is can be used to precompile styles with Sass, PostCss, etc.
-     * Below is an example folder structure containing a webapp's global sass file, named app.css.
-     */
-    globalStyle?: string;
-    /**
-     * When the hashFileNames config is set to true, and it is a production build,
-     * the hashedFileNameLength config is used to determine how many characters the file name's hash should be.
-     */
-    hashedFileNameLength?: number;
-    /**
-     * During production builds, the content of each generated file is hashed to represent the content,
-     * and the hashed value is used as the filename. If the content isn't updated between builds,
-     * then it receives the same filename. When the content is updated, then the filename is different.
-     *
-     * By doing this, deployed apps can "forever-cache" the build directory and take full advantage of
-     * content delivery networks (CDNs) and heavily caching files for faster apps.
-     */
-    hashFileNames?: boolean;
-    /**
-     * The namespace config is a string representing a namespace for the app.
-     * For apps that are not meant to be a library of reusable components,
-     * the default of App is just fine. However, if the app is meant to be consumed
-     * as a third-party library, such as Navify, a unique namespace is required.
-     */
-    namespace?: string;
-    /**
-     * Rindo is able to take an app's source and compile it to numerous targets,
-     * such as an app to be deployed on an http server, or as a third-party library
-     * to be distributed on npm. By default, Rindo apps have an output target type of www.
-     *
-     * The outputTargets config is an array of objects, with types of www and dist.
-     */
-    outputTargets?: OutputTarget[];
-    /**
-     * The plugins config can be used to add your own rollup plugins.
-     * By default, Rindo does not come with Sass or PostCss support.
-     * However, either can be added using the plugin array.
-     */
-    plugins?: any[];
-    /**
-     * The srcDir config specifies the directory which should contain the source typescript files
-     * for each component. The standard for Rindo apps is to use src, which is the default.
-     */
-    srcDir?: string;
-    /**
-     * Passes custom configuration down to the "rollup-plugin-commonjs" that Rindo uses under the hood.
-     * For further information: https://rindojs.web.app/docs/module-bundling
-     */
-    commonjs?: BundlingConfig;
-    /**
-     * Passes custom configuration down to the "rollup-plugin-node-resolve" that Rindo uses under the hood.
-     * For further information: https://rindojs.web.app/docs/module-bundling
-     */
-    nodeResolve?: NodeResolveConfig;
-    /**
-     * Passes custom configuration down to rollup itself, not all rollup options can be overriden.
-     */
-    rollupConfig?: RollupConfig;
-    /**
-     * Sets if the ES5 build must be generated or not. It defaults to `false` in dev mode, and `true` in production mode.
-     * Notice that Rindo always generates a modern build too, this setting will just disable the additional `es5` build.
-     */
-    buildEs5?: boolean;
-    /**
-     * Sets if the JS browser files are minified or not. Rindo uses `terser` under the hood.
-     * Defaults to `false` in dev mode and `true` in production mode.
-     */
-    minifyJs?: boolean;
-    /**
-     * Sets if the CSS is minified or not. Rindo uses `cssnano` under the hood.
-     * Defaults to `false` in dev mode and `true` in production mode.
-     */
-    minifyCss?: boolean;
-    /**
-     * Forces Rindo to run in `dev` mode if the value is `true` and `production` mode
-     * if it's `false`.
-     *
-     * Defaults to `false` (ie. production) unless the `--dev` flag is used in the CLI.
-     */
-    devMode?: boolean;
-    /**
-     * Object to provide a custom logger. By default a `logger` is already provided for the
-     * platform the compiler is running on, such as NodeJS or a browser.
-     */
-    logger?: Logger;
-    /**
-     * Config to add extra runtime for DOM features that require more polyfills. Note
-     * that not all DOM APIs are fully polyfilled when using the slot polyfill. These
-     * are opt-in since not all users will require the additional runtime.
-     */
-    extras?: ConfigExtras;
-    /**
-     * The hydrated flag identifies if a component and all of its child components
-     * have finished hydrating. This helps prevent any flash of unstyled content (FOUC)
-     * as various components are asynchronously downloaded and rendered. By default it
-     * will add the `hydrated` CSS class to the element. The `hydratedFlag` confg can be used
-     * to change the name of the CSS class, change it to an attribute, or change which
-     * type of CSS properties and values are assigned before and after hydrating. This config
-     * can also be used to not include the hydrated flag at all by setting it to `null`.
-     */
-    hydratedFlag?: HydratedFlag;
-    globalScript?: string;
-    srcIndexHtml?: string;
-    watch?: boolean;
-    testing?: TestingConfig;
-    maxConcurrentWorkers?: number;
-    maxConcurrentTasksPerWorker?: number;
-    preamble?: string;
-    includeSrc?: string[];
-    entryComponentsHint?: string[];
-    buildDist?: boolean;
-    buildLogFilePath?: string;
-    cacheDir?: string;
-    devInspector?: boolean;
-    devServer?: RindoDevServerConfig;
-    enableCacheStats?: boolean;
-    sys?: RindoSystem;
-    tsconfig?: string;
-    validateTypes?: boolean;
-    watchIgnoredRegex?: RegExp;
-    excludeUnusedDependencies?: boolean;
-    rindoCoreResolvedId?: string;
-}
-export interface ConfigExtras {
-    /**
-     * By default, the slot polyfill does not update `appendChild()` so that it appends
-     * new child nodes into the correct child slot like how shadow dom works. This is an opt-in
-     * polyfill for those who need it. Defaults to `false`.
-     */
-    appendChildSlotFix?: boolean;
-    /**
-     * By default, the runtime does not polyfill `cloneNode()` when cloning a component
-     * that uses the slot polyfill. This is an opt-in polyfill for those who need it.
-     * Defaults to `false`.
-     */
-    cloneNodeFix?: boolean;
-    /**
-     * Include the CSS Custom Property polyfill/shim for legacy browsers. Defaults to `true`
-     * for legacy builds only. ESM builds will not include the css vars shim.
-     */
-    cssVarsShim?: boolean;
-    /**
-     * Dynamic `import()` shim. This is only needed for Edge 18 and below, and Firefox 67 and below.
-     * Defaults to `true`.
-     */
-    dynamicImportShim?: boolean;
-    /**
-     * Dispatches component lifecycle events. Mainly used for testing. Defaults to `false`.
-     */
-    lifecycleDOMEvents?: boolean;
-    /**
-     * Safari 10 supports ES modules with `<script type="module">`, however, it did not implement
-     * `<script nomodule>`. When set to `false`, the runtime will not patch support for Safari 10.
-     * Defaults to `true`.
-     */
-    safari10?: boolean;
-    /**
-     * It is possible to assign data to the actual `<script>` element's `data-opts` property,
-     * which then gets passed to Rindo's initial bootstrap. This feature is only required
-     * for very special cases and rarely needed. When set to `false` it will not read
-     * this data. Defaults to `true`.
-     */
-    scriptDataOpts?: boolean;
-    /**
-     * If enabled `true`, the runtime will check if the shadow dom shim is required. However,
-     * if it's determined that shadow dom is already natively supported by the browser then
-     * it does not request the shim. Setting to `false` will avoid all shadow dom tests.
-     * Defaults to `true`.
-     */
-    shadowDomShim?: boolean;
-}
-export interface Config extends RindoConfig {
-    buildAppCore?: boolean;
-    buildDocs?: boolean;
-    configPath?: string;
-    cwd?: string;
-    writeLog?: boolean;
-    rollupPlugins?: any[];
-    devServer?: DevServerConfig;
-    flags?: ConfigFlags;
-    fsNamespace?: string;
-    logLevel?: 'error' | 'warn' | 'info' | 'debug' | string;
-    rootDir?: string;
-    suppressLogs?: boolean;
-    profile?: boolean;
-    _isValidated?: boolean;
-    _isTesting?: boolean;
-}
-export interface HydratedFlag {
-    /**
-     * Defaults to `hydrated`.
-     */
-    name?: string;
-    /**
-     * Can be either `class` or `attribute`. Defaults to `class`.
-     */
-    selector?: 'class' | 'attribute';
-    /**
-     * Defaults to use CSS `visibility` property.
-     */
-    property?: string;
-    /**
-     * This is the CSS value to give all components before it has been hydrated.
-     * Defaults to `hidden`.
-     */
-    initialValue?: string;
-    /**
-     * This is the CSS value to assign once a component has finished hydrating.
-     * Defaults to `inherit`.
-     */
-    hydratedValue?: string;
-}
-export interface BrowserConfig extends RindoConfig {
-    win?: Window;
-}
-export interface RollupConfig {
-    inputOptions?: RollupInputOptions;
-    outputOptions?: RollupOutputOptions;
-}
-export interface RollupInputOptions {
-    context?: string;
-    moduleContext?: ((id: string) => string) | {
-        [id: string]: string;
-    };
-    treeshake?: boolean;
-}
-export interface RollupOutputOptions {
-    globals?: {
-        [name: string]: string;
-    } | ((name: string) => string);
-}
-export interface BundlingConfig {
-    namedExports?: {
-        [key: string]: string[];
-    };
-}
-export interface NodeResolveConfig {
-    module?: boolean;
-    jsnext?: boolean;
-    main?: boolean;
-    browser?: boolean;
-    extensions?: string[];
-    preferBuiltins?: boolean;
-    jail?: string;
-    only?: Array<string | RegExp>;
-    modulesOnly?: boolean;
-    /**
-     * @see https://github.com/browserify/resolve#resolveid-opts-cb
-     */
-    customResolveOptions?: {
-        basedir?: string;
-        package?: string;
-        extensions?: string[];
-        readFile?: Function;
-        isFile?: Function;
-        isDirectory?: Function;
-        packageFilter?: Function;
-        pathFilter?: Function;
-        paths?: Function | string[];
-        moduleDirectory?: string | string[];
-        preserveSymlinks?: boolean;
-    };
-}
-export interface ConfigFlags {
-    task?: 'build' | 'docs' | 'help' | 'serve' | 'test' | 'g' | 'generate';
-    args?: string[];
-    knownArgs?: string[];
-    unknownArgs?: string[];
-    address?: string;
-    build?: boolean;
-    cache?: boolean;
-    checkVersion?: boolean;
-    ci?: boolean;
-    compare?: boolean;
-    config?: string;
-    debug?: boolean;
-    dev?: boolean;
-    docs?: boolean;
-    docsApi?: string;
-    docsJson?: string;
-    e2e?: boolean;
-    emulate?: string;
-    es5?: boolean;
-    esm?: boolean;
-    headless?: boolean;
-    help?: boolean;
-    log?: boolean;
-    logLevel?: string;
-    verbose?: boolean;
-    maxWorkers?: number;
-    open?: boolean;
-    port?: number;
-    prerender?: boolean;
-    prod?: boolean;
-    profile?: boolean;
-    root?: string;
-    screenshot?: boolean;
-    screenshotConnector?: string;
-    serve?: boolean;
-    serviceWorker?: boolean;
-    spec?: boolean;
-    stats?: boolean;
-    updateScreenshot?: boolean;
-    version?: boolean;
-    watch?: boolean;
-    devtools?: boolean;
-}
-export interface ConfigBundle {
-    components: string[];
-}
-export interface ServiceWorkerConfig {
-    unregister?: boolean;
-    swDest?: string;
-    swSrc?: string;
-    globPatterns?: string[];
-    globDirectory?: string | string[];
-    globIgnores?: string | string[];
-    templatedUrls?: any;
-    maximumFileSizeToCacheInBytes?: number;
-    manifestTransforms?: any;
-    modifyUrlPrefix?: any;
-    dontCacheBustURLsMatching?: RegExp;
-    navigateFallback?: string;
-    navigateFallbackWhitelist?: RegExp[];
-    navigateFallbackBlacklist?: RegExp[];
-    cacheId?: string;
-    skipWaiting?: boolean;
-    clientsClaim?: boolean;
-    directoryIndex?: string;
-    runtimeCaching?: any[];
-    ignoreUrlParametersMatching?: any[];
-    handleFetch?: boolean;
-}
-export interface HostConfig {
-    hosting?: {
-        rules?: HostRule[];
-    };
-}
-export interface HostRule {
-    include: string;
-    headers: HostRuleHeader[];
-}
-export interface HostRuleHeader {
-    name?: string;
-    value?: string;
-}

package/dist/declarations/css-var-shim.d.ts

@@ -1,9 +0,0 @@
-export interface CssVarShim {
-    i(): Promise<any>;
-    addLink(linkEl: HTMLLinkElement): Promise<any>;
-    addGlobalStyle(styleEl: HTMLStyleElement): void;
-    createHostStyle(hostEl: HTMLElement, templateName: string, cssText: string, isScoped: boolean): HTMLStyleElement;
-    removeHost(hostEl: HTMLElement): void;
-    updateHost(hostEl: HTMLElement): void;
-    updateGlobal(): void;
-}

package/dist/declarations/decorators.d.ts

@@ -1,150 +0,0 @@
-import { ModeStyles } from './style';
-declare type CustomMethodDecorator<T> = (target: Object, propertyKey: string | symbol, descriptor: TypedPropertyDescriptor<T>) => TypedPropertyDescriptor<T> | void;
-export interface ComponentDecorator {
-    (opts?: ComponentOptions): ClassDecorator;
-}
-export interface ComponentOptions {
-    /**
-     * Tag name of the web component. Ideally, the tag name must be globally unique,
-     * so it's recommended to choose an unique prefix for all your components within the same collection.
-     *
-     * In addition, tag name must contain a '-'
-     */
-    tag: string;
-    /**
-     * If `true`, the component will use scoped stylesheets. Similar to shadow-dom,
-     * but without native isolation. Defaults to `false`.
-     */
-    scoped?: boolean;
-    /**
-     * If `true`, the component will use native shadow-dom encapsulation, it will fallback to
-     * `scoped` if the browser does not support shadow-dom nativelly. Defaults to `false`.
-     * Additionally, `shadow` can also be given options when attaching the shadow root.
-     */
-    shadow?: boolean | ShadowRootOptions;
-    /**
-     * Relative URL to some external stylesheet file. It should be a `.css` file unless some
-     * external plugin is installed like `@rindo/sass`.
-     */
-    styleUrl?: string;
-    /**
-     * Similar as `styleUrl` but allows to specify different stylesheets for different modes.
-     */
-    styleUrls?: string[] | ModeStyles;
-    /**
-     * String that contains inlined CSS instead of using an external stylesheet.
-     * The performance characteristics of this feature are the same as using an external stylesheet.
-     *
-     * Notice, you can't use sass, or less, only `css` is allowed using `styles`, use `styleUrl` is you need more advanced features.
-     */
-    styles?: string;
-    /**
-     * Array of relative links to folders of assets required by the component.
-     */
-    assetsDirs?: string[];
-    /**
-     * @deprecated Use `assetsDirs` instead
-     */
-    assetsDir?: string;
-}
-export interface ShadowRootOptions {
-    /**
-     * When set to `true`, specifies behavior that mitigates custom element issues
-     * around focusability. When a non-focusable part of the shadow DOM is clicked, the first
-     * focusable part is given focus, and the shadow host is given any available `:focus` styling.
-     */
-    delegatesFocus?: boolean;
-}
-export interface PropDecorator {
-    (opts?: PropOptions): PropertyDecorator;
-}
-export interface PropOptions {
-    /**
-     * The name of the associated DOM attribute.
-     * Rindo uses different heuristics to determine the default name of the attribute,
-     * but using this property, you can override the default behaviour.
-     */
-    attribute?: string | null;
-    /**
-     * A Prop is _by default_ immutable from inside the component logic.
-     * Once a value is set by a user, the component cannot update it internally.
-     * However, it's possible to explicitly allow a Prop to be mutated from inside the component,
-     * by setting this `mutable` option to `true`.
-     */
-    mutable?: boolean;
-    /**
-     * In some cases it may be useful to keep a Prop in sync with an attribute.
-     * In this case you can set the `reflect` option to `true`, since it defaults to `false`:
-     */
-    reflect?: boolean;
-    /** @deprecated: "attr" has been deprecated, please use "attribute" instead. */
-    attr?: string;
-    /** @deprecated "context" has been deprecated. */
-    context?: string;
-    /** @deprecated "connect" has been deprecated, please use ES modules and/or dynamic imports instead. */
-    connect?: string;
-    /** @deprecated "reflectToAttr" has been deprecated, please use "reflect" instead. */
-    reflectToAttr?: boolean;
-}
-export interface MethodDecorator {
-    (opts?: MethodOptions): CustomMethodDecorator<any>;
-}
-export interface MethodOptions {
-}
-export interface ElementDecorator {
-    (): PropertyDecorator;
-}
-export interface EventDecorator {
-    (opts?: EventOptions): PropertyDecorator;
-}
-export interface EventOptions {
-    /**
-     * A string custom event name to override the default.
-     */
-    eventName?: string;
-    /**
-     * A Boolean indicating whether the event bubbles up through the DOM or not.
-     */
-    bubbles?: boolean;
-    /**
-     * A Boolean indicating whether the event is cancelable.
-     */
-    cancelable?: boolean;
-    /**
-     * A Boolean value indicating whether or not the event can bubble across the boundary between the shadow DOM and the regular DOM.
-     */
-    composed?: boolean;
-}
-export interface ListenDecorator {
-    (eventName: string, opts?: ListenOptions): CustomMethodDecorator<any>;
-}
-export interface ListenOptions {
-    /**
-     * Handlers can also be registered for an event other than the host itself.
-     * The `target` option can be used to change where the event listener is attached,
-     * this is useful for listening to application-wide events.
-     */
-    target?: ListenTargetOptions;
-    /**
-     * Event listener attached with `@Listen` does not "capture" by default,
-     * When a event listener is set to "capture", means the event will be dispatched
-     * during the "capture phase", check out https://www.quirksmode.org/js/events_order.html for further information.
-     */
-    capture?: boolean;
-    /**
-     * By default, Rindo uses several heuristics to determine if
-     * it must attach a `passive` event listener or not.
-     *
-     * Using the `passive` option can be used to change the default behaviour.
-     * Please check out https://developers.google.com/web/updates/2016/06/passive-event-listeners for further information.
-     */
-    passive?: boolean;
-}
-export declare type ListenTargetOptions = 'parent' | 'body' | 'document' | 'window';
-export interface StateDecorator {
-    (): PropertyDecorator;
-}
-export interface WatchDecorator {
-    (propName: string): CustomMethodDecorator<any>;
-}
-export {};

package/dist/declarations/dev-server.d.ts

@@ -1,135 +0,0 @@
-import { BuildLog, BuildResults } from './build';
-import { FsStats } from './file-system';
-export interface DevServer {
-    browserUrl: string;
-    close(): Promise<void>;
-}
-export interface RindoDevServerConfig {
-    /**
-     * IP address used by the dev server. The default is `0.0.0.0`, which points to all IPv4 addresses on the local machine, such as `localhost`.
-     */
-    address?: string;
-    /**
-     * Base path to be used by the server. Defaults to the root pathname.
-     */
-    basePath?: string;
-    /**
-     * When set, the dev server will run via https using the SSL certificate and key you provide (use `fs` if you want to read them from files).
-     */
-    https?: Credentials;
-    /**
-     * The URL the dev server should first open to. Defaults to `/`.
-     */
-    initialLoadUrl?: string;
-    /**
-     * When `true`, every request to the server will be logged within the terminal. Defaults to `false`.
-     */
-    logRequests?: boolean;
-    /**
-     * By default, when dev server is started the local dev URL is opened in your default browser. However, to prevent this URL to be opened change this value to `false`. Defaults to `true`.
-     */
-    openBrowser?: boolean;
-    /**
-     * Sets the server's port. Defaults to `3333`.
-     */
-    port?: number;
-    /**
-     * When files are watched and udated, by default the dev server will use `hmr` (Hot Module Replacement) to update the page without a full page refresh. To have the page do a full refresh use `pageReload`. To disable any reloading, use `null`. Defaults to `hmr`.
-     */
-    reloadStrategy?: PageReloadStrategy;
-    root?: string;
-    websocket?: boolean;
-}
-export interface DevServerConfig extends RindoDevServerConfig {
-    browserUrl?: string;
-    contentTypes?: {
-        [ext: string]: string;
-    };
-    devServerDir?: string;
-    editors?: DevServerEditor[];
-    excludeHmr?: string[];
-    gzip?: boolean;
-    historyApiFallback?: HistoryApiFallback;
-    openBrowser?: boolean;
-    protocol?: 'http' | 'https';
-}
-export interface Credentials {
-    key: string;
-    cert: string;
-}
-export declare type PageReloadStrategy = 'hmr' | 'pageReload' | null;
-export interface DevServerStartResponse {
-    browserUrl?: string;
-    initialLoadUrl?: string;
-}
-export interface DevClientWindow extends Window {
-    ['s-dev-server']: boolean;
-    ['s-initial-load']: boolean;
-    WebSocket: new (socketUrl: string, protos: string[]) => WebSocket;
-}
-export interface DevClientConfig {
-    basePath: string;
-    editors: DevServerEditor[];
-    reloadStrategy: PageReloadStrategy;
-}
-export interface HistoryApiFallback {
-    index?: string;
-    disableDotRule?: boolean;
-}
-export interface HttpRequest {
-    method: 'GET' | 'POST' | 'PUT' | 'DELETE' | 'HEAD' | 'OPTIONS';
-    acceptHeader: string;
-    url: string;
-    pathname?: string;
-    filePath?: string;
-    stats?: FsStats;
-    headers?: {
-        [name: string]: string;
-    };
-    host?: string;
-}
-export interface DevServerMessage {
-    startServer?: DevServerConfig;
-    serverStated?: DevServerStartResponse;
-    buildLog?: BuildLog;
-    buildResults?: BuildResults;
-    requestBuildResults?: boolean;
-    error?: {
-        message?: string;
-        type?: string;
-        stack?: any;
-    };
-    isActivelyBuilding?: boolean;
-    requestLog?: {
-        method: string;
-        url: string;
-        status: number;
-    };
-}
-export declare type DevServerDestroy = () => void;
-export interface DevResponseHeaders {
-    'Cache-Control'?: string;
-    'Expires'?: string;
-    'Content-Type'?: string;
-    'Content-Length'?: number;
-    'Access-Control-Allow-Origin'?: string;
-    'Content-Encoding'?: 'gzip';
-    'Vary'?: 'Accept-Encoding';
-    'X-Powered-By'?: string;
-    'X-Directory-Index'?: string;
-}
-export interface DevServerEditor {
-    id: string;
-    name?: string;
-    supported?: boolean;
-    priority?: number;
-}
-export interface OpenInEditorData {
-    file?: string;
-    line?: number;
-    column?: number;
-    open?: string;
-    editor?: string;
-    exists?: boolean;
-    error?: string;
-}