Notable Pseudocode Mashups

    svelte-check

    2.7.1 • Public • Published

    Check your code with svelte-check

    Provides CLI diagnostics checks for:

    • Unused CSS
    • Svelte A11y hints
    • JavaScript/TypeScript compiler errors

    Requires Node 12 or later.

    Usage:

    Local / in your project

    Installation:

    npm i svelte-check --save-dev

    Package.json:

    {
        // ...
        "scripts": {
            "svelte-check": "svelte-check"
            // ...
        },
        // ...
        "devDependencies": {
            "svelte-check": "..."
            // ...
        }
    }

    Usage:

    npm run svelte-check

    Global (not recommended)

    Installation:

    npm i svelte-check svelte -g

    Usage:

    1. Go to folder where to start checking
    2. svelte-check

    Args:

    Flag Description
    --workspace <path> Path to your workspace. All subdirectories except node_modules and those listed in --ignore are checked
    --output <human|human-verbose|machine>
    --watch Will not exit after one pass but keep watching files for changes and rerun diagnostics
    --tsconfig <path> Pass a path to a tsconfig or jsconfig file. The path can be relative to the workspace path or absolute. Doing this means that only files matched by the files/include/exclude pattern of the config file are diagnosed. It also means that errors from TypeScript and JavaScript files are reported.
    --ignore <path1,path2> Files/folders to ignore - relative to workspace root, comma-separated, inside quotes. Example: --ignore "dist,build". When used in conjunction with --tsconfig, this will only have effect on the files watched, not on the files that are diagnosed, which is then determined by the tsconfig.json
    --fail-on-warnings Will also exit with error code when there are warnings
    --fail-on-hints Will also exit with error code when there are hints
    --compiler-warnings <code1:error|ignore,code2:error|ignore> A list of Svelte compiler warning codes. Each entry defines whether that warning should be ignored or treated as an error. Warnings are comma-separated, between warning code and error level is a colon; all inside quotes. Example: --compiler-warnings "css-unused-selector:ignore,unused-export-let:error"
    --diagnostic-sources <js,svelte,css> A list of diagnostic sources which should run diagnostics on your code. Possible values are js (includes TS), svelte, css. Comma-separated, inside quotes. By default all are active. Example: --diagnostic-sources "js,svelte"
    --threshold <error|warning> Filters the diagnostics to display. error will output only errors while warning will output warnings and errors.
    --use-new-transformation <true|false> Svelte files need to be transformed to something that TypeScript understands for intellisense. Version 2.0 of this transformation can be enabled with this setting. It will be the default, soon. Please try it out and provide feedback

    FAQ

    Why is there no option to only check specific files (for example only staged files)?

    svelte-check needs to know the whole project to do valid checks. Imagine you alter a component property export let foo to export let bar, but you don't update any of the component usages. They all have errors now but you would not catch them if you only run checks on changed files.

    More docs, preprocessor setup and troubleshooting

    See here.

    Machine-Readable Output

    Setting the --output to machine will format output in a way that is easier to read by machines, e.g. inside CI pipelines, for code quality checks, etc.

    Each row corresponds to a new record. Rows are made up of columns that are separated by a single space character. The first column of every row contains a timestamp in milliseconds which can be used for monitoring purposes. The second column gives us the "row type", based on which the number and types of subsequent columns may differ.

    The first row is of type START and contains the workspace folder (wrapped in quotes).

    Example:
    1590680325583 START "/home/user/language-tools/packages/language-server/test/plugins/typescript/testfiles"
    

    Any number of ERROR or WARNING records may follow. Their structure is identical and tells us the filename, the line and column numbers, and the error message. The filename is relative to the workspace directory. The filename and the message are both wrapped in quotes.

    Example:
    1590680326283 ERROR "codeactions.svelte" 1:16 "Cannot find module 'blubb' or its corresponding type declarations."
    1590680326778 WARNING "imported-file.svelte" 0:37 "Component has unused export property 'prop'. If it is for external reference only, please consider using `export const prop`"
    

    The output concludes with a COMPLETED message that summarizes total numbers of files, errors, warnings and hints that were encountered during the check.

    Example:
    1590680326807 COMPLETED 20 FILES 21 ERRORS 1 WARNINGS 0 HINTS
    

    If the application experiences a runtime error, this error will appear as a FAILURE record.

    Example:
    1590680328921 FAILURE "Connection closed"
    

    Credits

    • Vue's VTI which lays the foundation for svelte-check

    Keywords

    Install

    npm i svelte-check

    DownloadsWeekly Downloads

    93,587

    Version

    2.7.1

    License

    MIT

    Unpacked Size

    4.22 MB

    Total Files

    8

    Last publish

    Collaborators

    • dummdidumm
    • svelte-language-tools-deploy
    • orta