Santhosh Janardhanan
de2d83092e
- Delete old Vite+Svelte frontend - Initialize new SvelteKit project with TypeScript - Configure Tailwind CSS v4 + DaisyUI - Implement JWT authentication with auto-refresh - Create login page with form validation (Zod) - Add protected route guards - Update Docker configuration for single-stage build - Add E2E tests with Playwright (6/11 passing) - Fix Svelte 5 reactivity with $state() runes Known issues: - 5 E2E tests failing (timing/async issues) - Token refresh implementation needs debugging - Validation error display timing
27 lines
1.3 KiB
TypeScript
27 lines
1.3 KiB
TypeScript
import type * as Compiler from "./svelte-ast-types-for-v5.js";
|
|
import type * as SvAST from "./svelte-ast-types.js";
|
|
import type { NormalizedParserOptions } from "./parser-options.js";
|
|
import type { SvelteConfig } from "../svelte-config/index.js";
|
|
import type { ESLintProgram } from "./index.js";
|
|
/** The context for parsing. */
|
|
export type SvelteParseContext = {
|
|
/**
|
|
* Determines if the file is in Runes mode.
|
|
*
|
|
* - Svelte 3/4 does not support Runes mode.
|
|
* - Checks if `runes` configuration exists in:
|
|
* - `parserOptions`
|
|
* - `svelte.config.js`
|
|
* - `<svelte:options>` in the Svelte file.
|
|
* - Returns `true` if the `runes` symbol is present in the Svelte file.
|
|
*/
|
|
runes?: boolean;
|
|
/** The version of "svelte/compiler". */
|
|
compilerVersion: string;
|
|
/** The result of static analysis of `svelte.config.js`. */
|
|
svelteConfig: SvelteConfig | null;
|
|
};
|
|
export declare function resolveSvelteParseContextForSvelte(svelteConfig: SvelteConfig | null, parserOptions: NormalizedParserOptions, svelteAst: Compiler.Root | SvAST.AstLegacy): SvelteParseContext;
|
|
export declare function resolveSvelteParseContextForSvelteScript(svelteConfig: SvelteConfig | null): SvelteParseContext;
|
|
export declare function hasRunesSymbol(ast: ESLintProgram): boolean;
|