Nuclear Pumpkin Mocha


    1.7.0 • Public • Published


    Snipsync makes sure your documented code snippets are always in sync with your Github repo source files.


    This tool requires Node v15.0.0 or above (recommended 15.2.1) and Yarn.



    yarn add snipsync


    Create a file called "snipsync.config.yaml" in the project root. This file specifies the following:

    • origins: The Github repositories or local files where the tool will look for source code snippets.
    • targets: The local directories that contain the files to be spliced with the code snippets.

    The origins property is a list of objects that have one of the following 2 formats:

    1. owner, repo, and optionally ref: pull snippets from a GitHub repo
    2. files: array of strings containing relative paths to load snippets from. Supports glob syntax.

    If the ref key is left blank or not specified, then the most recent commit from the master branch will be used. If the enable_source_link key in features is not specified, then it will default to true. If the enable_code_block key in features is not specified, then it will default to true.

    The allowed_target_extensions key in features lets you set a list of extensions to scan. Specify extensions like [.md,.txt]. If the allowed_target_extensions key in features is not specified, then it defaults to an empty array ([]) and all files are scanned.

    Example of a complete snipsync.config.yaml:

      - owner: temporalio
        repo: go-samples
        ref: 6880b0d09ddb6edf150e3095c90522602022578f
      - owner: temporalio
        repo: java-samples
      - files:
        - ./src/**/*.ts
      - docs
      - blog
      enable_source_link: false
      enable_code_block: false
      allowed_target_extensions: [.md]

    Example of a bare minimum snipsync.config.yaml:

      - owner: temporalio
        repo: go-samples
      - docs

    Comment wrappers

    Use comments to identify code snippets and the locations where they should be merged.

    Source code

    In the source repo, wrap the code snippets in comments with a unique snippet identifier like this:

    // @@@SNIPSTART hellouniverse
    func HelloUniverse() {
    	fmt.Println("Hello Universe!")
    // @@@SNIPEND

    In the example above, "hellouniverse" is the unique identifier for the code snippet.

    Unique identifiers can contain letters, numbers, hyphens, and underscores.

    Target files

    In the target files wrap the location with comments that reference the identifier of the code snippet that will be placed there:

    <!--SNIPSTART hellouniverse-->

    In the example above, the "hellouniverse" code snippet will be spliced between the comments. Any text inside of the placeholders will be replaced by the code snippet when the tool runs. The tool will automatically specify the code type for markdown rendering. For example, if the source file ends in ".go" then the code section will be written like this: ```go

    Per-snip features

    To customize how a single snip is rendered, add a JSON feature configuration in the snip start line.

    <!--SNIPSTART hellouniverse {"enable_source_link": false, "enable_code_block": false}-->


    From the root directory of your project run the following command:


    Remove snippets

    In some cases, you may want to remove the snippets from your target files. Use the --clear flag to do that:

    snipsync --clear


    The snipsync tool is set up to test its own functionality during development. Git ignores the snipsync.config.yaml file and the 'docs' directory within the package itself. Run yarn dev to run snipsync from within the package.




    npm i snipsync

    DownloadsWeekly Downloads






    Unpacked Size

    22 kB

    Total Files


    Last publish


    • laurakwhit
    • rossedfort
    • alex.tideman
    • temporal-sdk-team
    • taillogs
    • flossypurse
    • tempbearpig