Configuration on Producthunt daily

eslint

Wed, 24 Sep 2025 15:28:00 +0800

eslint/eslint

ESLint

ESLint is a tool for identifying and reporting on patterns found in ECMAScript/JavaScript code. In many ways, it is similar to JSLint and JSHint with a few exceptions:

ESLint uses Espree for JavaScript parsing.
ESLint uses an AST to evaluate patterns in code.
ESLint is completely pluggable, every single rule is a plugin and you can add more at runtime.

Installation and Usage

Prerequisites: Node.js (^18.18.0, ^20.9.0, or >=21.1.0) built with SSL support. (If you are using an official Node.js distribution, SSL is always built in.)

You can install and configure ESLint using this command:

`1`	`npm init @eslint/config@latest`

After that, you can run ESLint on any file or directory like this:

`1`	`npx eslint yourfile.js`

pnpm Installation

To use ESLint with pnpm, we recommend setting up a .npmrc file with at least the following settings:

1
2

auto-install-peers=true
node-linker=hoisted

This ensures that pnpm installs dependencies in a way that is more compatible with npm and is less likely to produce errors.

Configuration

You can configure rules in your eslint.config.js files as in this example:

import { defineConfig } from "eslint/config";

export default defineConfig([
	{
		files: ["**/*.js", "**/*.cjs", "**/*.mjs"],
		rules: {
			"prefer-const": "warn",
			"no-constant-binary-expression": "error",
		},
	},
]);

The names "prefer-const" and "no-constant-binary-expression" are the names of rules in ESLint. The first value is the error level of the rule and can be one of these values:

"off" or 0 - turn the rule off
"warn" or 1 - turn the rule on as a warning (doesn’t affect exit code)
"error" or 2 - turn the rule on as an error (exit code will be 1)

The three error levels allow you fine-grained control over how ESLint applies rules (for more configuration options and details, see the configuration docs).

Version Support

The ESLint team provides ongoing support for the current version and six months of limited support for the previous version. Limited support includes critical bug fixes, security issues, and compatibility issues only.

ESLint offers commercial support for both current and previous versions through our partners, Tidelift and HeroDevs.

See Version Support for more details.

Code of Conduct

ESLint adheres to the OpenJS Foundation Code of Conduct.

Filing Issues

Before filing an issue, please be sure to read the guidelines for what you’re reporting:

Frequently Asked Questions

Does ESLint support JSX?

Yes, ESLint natively supports parsing JSX syntax (this must be enabled in configuration). Please note that supporting JSX syntax is not the same as supporting React. React applies specific semantics to JSX syntax that ESLint doesn’t recognize. We recommend using eslint-plugin-react if you are using React and want React semantics.

Does Prettier replace ESLint?

No, ESLint and Prettier have different jobs: ESLint is a linter (looking for problematic patterns) and Prettier is a code formatter. Using both tools is common, refer to Prettier’s documentation to learn how to configure them to work well with each other.

What ECMAScript versions does ESLint support?

ESLint has full support for ECMAScript 3, 5, and every year from 2015 up until the most recent stage 4 specification (the default). You can set your desired ECMAScript syntax and other settings (like global variables) through configuration.

What about experimental features?

ESLint’s parser only officially supports the latest final ECMAScript standard. We will make changes to core rules in order to avoid crashes on stage 3 ECMAScript syntax proposals (as long as they are implemented using the correct experimental ESTree syntax). We may make changes to core rules to better work with language extensions (such as JSX, Flow, and TypeScript) on a case-by-case basis.

In other cases (including if rules need to warn on more or fewer cases due to new syntax, rather than just not crashing), we recommend you use other parsers and/or rule plugins. If you are using Babel, you can use @babel/eslint-parser and @babel/eslint-plugin to use any option available in Babel.

Once a language feature has been adopted into the ECMAScript standard (stage 4 according to the TC39 process), we will accept issues and pull requests related to the new feature, subject to our contributing guidelines. Until then, please use the appropriate parser and plugin(s) for your experimental feature.

Which Node.js versions does ESLint support?

ESLint updates the supported Node.js versions with each major release of ESLint. At that time, ESLint’s supported Node.js versions are updated to be:

The most recent maintenance release of Node.js
The lowest minor version of the Node.js LTS release that includes the features the ESLint team wants to use.
The Node.js Current release

ESLint is also expected to work with Node.js versions released after the Node.js Current release.

Refer to the Quick Start Guide for the officially supported Node.js versions for a given ESLint release.

Where to ask for help?

Open a discussion or stop by our Discord server.

Why doesn’t ESLint lock dependency versions?

Lock files like package-lock.json are helpful for deployed applications. They ensure that dependencies are consistent between environments and across deployments.

Packages like eslint that get published to the npm registry do not include lock files. npm install eslint as a user will respect version constraints in ESLint’s package.json. ESLint and its dependencies will be included in the user’s lock file if one exists, but ESLint’s own lock file would not be used.

We intentionally don’t lock dependency versions so that we have the latest compatible dependency versions in development and CI that our users get when installing ESLint in a project.

The Twilio blog has a deeper dive to learn more.

Releases

We have scheduled releases every two weeks on Friday or Saturday. You can follow a release issue for updates about the scheduling of any particular release.

Security Policy

ESLint takes security seriously. We work hard to ensure that ESLint is safe for everyone and that security issues are addressed quickly and responsibly. Read the full security policy.

Semantic Versioning Policy

ESLint follows semantic versioning. However, due to the nature of ESLint as a code quality tool, it’s not always clear when a minor or major version bump occurs. To help clarify this for everyone, we’ve defined the following semantic versioning policy for ESLint:

Patch release (intended to not break your lint build)
- A bug fix in a rule that results in ESLint reporting fewer linting errors.
- A bug fix to the CLI or core (including formatters).
- Improvements to documentation.
- Non-user-facing changes such as refactoring code, adding, deleting, or modifying tests, and increasing test coverage.
- Re-releasing after a failed release (i.e., publishing a release that doesn’t work for anyone).
Minor release (might break your lint build)
- A bug fix in a rule that results in ESLint reporting more linting errors.
- A new rule is created.
- A new option to an existing rule that does not result in ESLint reporting more linting errors by default.
- A new addition to an existing rule to support a newly-added language feature (within the last 12 months) that will result in ESLint reporting more linting errors by default.
- An existing rule is deprecated.
- A new CLI capability is created.
- New capabilities to the public API are added (new classes, new methods, new arguments to existing methods, etc.).
- A new formatter is created.
- eslint:recommended is updated and will result in strictly fewer linting errors (e.g., rule removals).
Major release (likely to break your lint build)
- eslint:recommended is updated and may result in new linting errors (e.g., rule additions, most rule option updates).
- A new option to an existing rule that results in ESLint reporting more linting errors by default.
- An existing formatter is removed.
- Part of the public API is removed or changed in an incompatible way. The public API includes:
  - Rule schemas
  - Configuration schema
  - Command-line options
  - Node.js API
  - Rule, formatter, parser, plugin APIs

According to our policy, any minor update may report more linting errors than the previous release (ex: from a bug fix). As such, we recommend using the tilde (~) in package.json e.g. "eslint": "~3.1.0" to guarantee the results of your builds.

License

MIT License

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Team

These folks keep the project moving and are resources for help.

Technical Steering Committee (TSC)

The people who manage releases, review feature requests, and meet regularly to ensure ESLint is properly maintained.

Nicholas C. Zakas

Francesco Trotta

Milos Djermanovic

Reviewers

The people who review and implement new features.

唯然	Nitin Kumar

Committers

The people who review and fix bugs and help triage issues.

fnx

Josh Goldberg ✨

Tanuj Kanti

루밀LuMir

Website Team

Team members who focus specifically on eslint.org

Amaresh S M

Harish

Percy Ma

youtube-dl

Tue, 23 Sep 2025 15:28:59 +0800

ytdl-org/youtube-dl

youtube-dl - download videos from youtube.com or other video platforms

INSTALLATION

To install it right away for all UNIX users (Linux, macOS, etc.), type:

sudo curl -L https://yt-dl.org/downloads/latest/youtube-dl -o /usr/local/bin/youtube-dl
sudo chmod a+rx /usr/local/bin/youtube-dl

If you do not have curl, you can alternatively use a recent wget:

sudo wget https://yt-dl.org/downloads/latest/youtube-dl -O /usr/local/bin/youtube-dl
sudo chmod a+rx /usr/local/bin/youtube-dl

Windows users can download an .exe file and place it in any location on their PATH except for %SYSTEMROOT%\System32 (e.g. do not put in C:\Windows\System32).

You can also use pip:

sudo -H pip install --upgrade youtube-dl

This command will update youtube-dl if you have already installed it. See the pypi page for more information.

macOS users can install youtube-dl with Homebrew:

brew install youtube-dl

Or with MacPorts:

sudo port install youtube-dl

Alternatively, refer to the developer instructions for how to check out and work with the git repository. For further options, including PGP signatures, see the youtube-dl Download Page.

DESCRIPTION

youtube-dl is a command-line program to download videos from YouTube.com and a few more sites. It requires the Python interpreter, version 2.6, 2.7, or 3.2+, and it is not platform specific. It should work on your Unix box, on Windows or on macOS. It is released to the public domain, which means you can modify it, redistribute it or use it however you like.

youtube-dl [OPTIONS] URL [URL...]

OPTIONS

-h, --help                           Print this help text and exit
--version                            Print program version and exit
-U, --update                         Update this program to latest version.
                                     Make sure that you have sufficient
                                     permissions (run with sudo if needed)
-i, --ignore-errors                  Continue on download errors, for
                                     example to skip unavailable videos in a
                                     playlist
--abort-on-error                     Abort downloading of further videos (in
                                     the playlist or the command line) if an
                                     error occurs
--dump-user-agent                    Display the current browser
                                     identification
--list-extractors                    List all supported extractors
--extractor-descriptions             Output descriptions of all supported
                                     extractors
--force-generic-extractor            Force extraction to use the generic
                                     extractor
--default-search PREFIX              Use this prefix for unqualified URLs.
                                     For example "gvsearch2:" downloads two
                                     videos from google videos for youtube-
                                     dl "large apple". Use the value "auto"
                                     to let youtube-dl guess ("auto_warning"
                                     to emit a warning when guessing).
                                     "error" just throws an error. The
                                     default value "fixup_error" repairs
                                     broken URLs, but emits an error if this
                                     is not possible instead of searching.
--ignore-config                      Do not read configuration files. When
                                     given in the global configuration file
                                     /etc/youtube-dl.conf: Do not read the
                                     user configuration in
                                     ~/.config/youtube-dl/config
                                     (%APPDATA%/youtube-dl/config.txt on
                                     Windows)
--config-location PATH               Location of the configuration file;
                                     either the path to the config or its
                                     containing directory.
--flat-playlist                      Do not extract the videos of a
                                     playlist, only list them.
--mark-watched                       Mark videos watched (YouTube only)
--no-mark-watched                    Do not mark videos watched (YouTube
                                     only)
--no-color                           Do not emit color codes in output

Network Options:

--proxy URL                          Use the specified HTTP/HTTPS/SOCKS
                                     proxy. To enable SOCKS proxy, specify a
                                     proper scheme. For example
                                     socks5://127.0.0.1:1080/. Pass in an
                                     empty string (--proxy "") for direct
                                     connection
--socket-timeout SECONDS             Time to wait before giving up, in
                                     seconds
--source-address IP                  Client-side IP address to bind to
-4, --force-ipv4                     Make all connections via IPv4
-6, --force-ipv6                     Make all connections via IPv6

Geo Restriction:

--geo-verification-proxy URL         Use this proxy to verify the IP address
                                     for some geo-restricted sites. The
                                     default proxy specified by --proxy (or
                                     none, if the option is not present) is
                                     used for the actual downloading.
--geo-bypass                         Bypass geographic restriction via
                                     faking X-Forwarded-For HTTP header
--no-geo-bypass                      Do not bypass geographic restriction
                                     via faking X-Forwarded-For HTTP header
--geo-bypass-country CODE            Force bypass geographic restriction
                                     with explicitly provided two-letter ISO
                                     3166-2 country code
--geo-bypass-ip-block IP_BLOCK       Force bypass geographic restriction
                                     with explicitly provided IP block in
                                     CIDR notation

Video Selection:

--playlist-start NUMBER              Playlist video to start at (default is
                                     1)
--playlist-end NUMBER                Playlist video to end at (default is
                                     last)
--playlist-items ITEM_SPEC           Playlist video items to download.
                                     Specify indices of the videos in the
                                     playlist separated by commas like: "--
                                     playlist-items 1,2,5,8" if you want to
                                     download videos indexed 1, 2, 5, 8 in
                                     the playlist. You can specify range: "
                                     --playlist-items 1-3,7,10-13", it will
                                     download the videos at index 1, 2, 3,
                                     7, 10, 11, 12 and 13.
--match-title REGEX                  Download only matching titles (regex or
                                     caseless sub-string)
--reject-title REGEX                 Skip download for matching titles
                                     (regex or caseless sub-string)
--max-downloads NUMBER               Abort after downloading NUMBER files
--min-filesize SIZE                  Do not download any videos smaller than
                                     SIZE (e.g. 50k or 44.6m)
--max-filesize SIZE                  Do not download any videos larger than
                                     SIZE (e.g. 50k or 44.6m)
--date DATE                          Download only videos uploaded in this
                                     date
--datebefore DATE                    Download only videos uploaded on or
                                     before this date (i.e. inclusive)
--dateafter DATE                     Download only videos uploaded on or
                                     after this date (i.e. inclusive)
--min-views COUNT                    Do not download any videos with less
                                     than COUNT views
--max-views COUNT                    Do not download any videos with more
                                     than COUNT views
--match-filter FILTER                Generic video filter. Specify any key
                                     (see the "OUTPUT TEMPLATE" for a list
                                     of available keys) to match if the key
                                     is present, !key to check if the key is
                                     not present, key > NUMBER (like
                                     "comment_count > 12", also works with
                                     >=, <, <=, !=, =) to compare against a
                                     number, key = 'LITERAL' (like "uploader
                                     = 'Mike Smith'", also works with !=) to
                                     match against a string literal and & to
                                     require multiple matches. Values which
                                     are not known are excluded unless you
                                     put a question mark (?) after the
                                     operator. For example, to only match
                                     videos that have been liked more than
                                     100 times and disliked less than 50
                                     times (or the dislike functionality is
                                     not available at the given service),
                                     but who also have a description, use
                                     --match-filter "like_count > 100 &
                                     dislike_count <? 50 & description" .
--no-playlist                        Download only the video, if the URL
                                     refers to a video and a playlist.
--yes-playlist                       Download the playlist, if the URL
                                     refers to a video and a playlist.
--age-limit YEARS                    Download only videos suitable for the
                                     given age
--download-archive FILE              Download only videos not listed in the
                                     archive file. Record the IDs of all
                                     downloaded videos in it.
--include-ads                        Download advertisements as well
                                     (experimental)

Download Options:

-r, --limit-rate RATE                Maximum download rate in bytes per
                                     second (e.g. 50K or 4.2M)
-R, --retries RETRIES                Number of retries (default is 10), or
                                     "infinite".
--fragment-retries RETRIES           Number of retries for a fragment
                                     (default is 10), or "infinite" (DASH,
                                     hlsnative and ISM)
--skip-unavailable-fragments         Skip unavailable fragments (DASH,
                                     hlsnative and ISM)
--abort-on-unavailable-fragment      Abort downloading when some fragment is
                                     not available
--keep-fragments                     Keep downloaded fragments on disk after
                                     downloading is finished; fragments are
                                     erased by default
--buffer-size SIZE                   Size of download buffer (e.g. 1024 or
                                     16K) (default is 1024)
--no-resize-buffer                   Do not automatically adjust the buffer
                                     size. By default, the buffer size is
                                     automatically resized from an initial
                                     value of SIZE.
--http-chunk-size SIZE               Size of a chunk for chunk-based HTTP
                                     downloading (e.g. 10485760 or 10M)
                                     (default is disabled). May be useful
                                     for bypassing bandwidth throttling
                                     imposed by a webserver (experimental)
--playlist-reverse                   Download playlist videos in reverse
                                     order
--playlist-random                    Download playlist videos in random
                                     order
--xattr-set-filesize                 Set file xattribute ytdl.filesize with
                                     expected file size
--hls-prefer-native                  Use the native HLS downloader instead
                                     of ffmpeg
--hls-prefer-ffmpeg                  Use ffmpeg instead of the native HLS
                                     downloader
--hls-use-mpegts                     Use the mpegts container for HLS
                                     videos, allowing to play the video
                                     while downloading (some players may not
                                     be able to play it)
--external-downloader COMMAND        Use the specified external downloader.
                                     Currently supports aria2c,avconv,axel,c
                                     url,ffmpeg,httpie,wget
--external-downloader-args ARGS      Give these arguments to the external
                                     downloader

Filesystem Options:

-a, --batch-file FILE                File containing URLs to download ('-'
                                     for stdin), one URL per line. Lines
                                     starting with '#', ';' or ']' are
                                     considered as comments and ignored.
--id                                 Use only video ID in file name
-o, --output TEMPLATE                Output filename template, see the
                                     "OUTPUT TEMPLATE" for all the info
--output-na-placeholder PLACEHOLDER  Placeholder value for unavailable meta
                                     fields in output filename template
                                     (default is "NA")
--autonumber-start NUMBER            Specify the start value for
                                     %(autonumber)s (default is 1)
--restrict-filenames                 Restrict filenames to only ASCII
                                     characters, and avoid "&" and spaces in
                                     filenames
-w, --no-overwrites                  Do not overwrite files
-c, --continue                       Force resume of partially downloaded
                                     files. By default, youtube-dl will
                                     resume downloads if possible.
--no-continue                        Do not resume partially downloaded
                                     files (restart from beginning)
--no-part                            Do not use .part files - write directly
                                     into output file
--no-mtime                           Do not use the Last-modified header to
                                     set the file modification time
--write-description                  Write video description to a
                                     .description file
--write-info-json                    Write video metadata to a .info.json
                                     file
--write-annotations                  Write video annotations to a
                                     .annotations.xml file
--load-info-json FILE                JSON file containing the video
                                     information (created with the "--write-
                                     info-json" option)
--cookies FILE                       File to read cookies from and dump
                                     cookie jar in
--cache-dir DIR                      Location in the filesystem where
                                     youtube-dl can store some downloaded
                                     information permanently. By default
                                     $XDG_CACHE_HOME/youtube-dl or
                                     ~/.cache/youtube-dl . At the moment,
                                     only YouTube player files (for videos
                                     with obfuscated signatures) are cached,
                                     but that may change.
--no-cache-dir                       Disable filesystem caching
--rm-cache-dir                       Delete all filesystem cache files

Thumbnail Options:

--write-thumbnail                    Write thumbnail image to disk
--write-all-thumbnails               Write all thumbnail image formats to
                                     disk
--list-thumbnails                    Simulate and list all available
                                     thumbnail formats

Verbosity / Simulation Options:

-q, --quiet                          Activate quiet mode
--no-warnings                        Ignore warnings
-s, --simulate                       Do not download the video and do not
                                     write anything to disk
--skip-download                      Do not download the video
-g, --get-url                        Simulate, quiet but print URL
-e, --get-title                      Simulate, quiet but print title
--get-id                             Simulate, quiet but print id
--get-thumbnail                      Simulate, quiet but print thumbnail URL
--get-description                    Simulate, quiet but print video
                                     description
--get-duration                       Simulate, quiet but print video length
--get-filename                       Simulate, quiet but print output
                                     filename
--get-format                         Simulate, quiet but print output format
-j, --dump-json                      Simulate, quiet but print JSON
                                     information. See the "OUTPUT TEMPLATE"
                                     for a description of available keys.
-J, --dump-single-json               Simulate, quiet but print JSON
                                     information for each command-line
                                     argument. If the URL refers to a
                                     playlist, dump the whole playlist
                                     information in a single line.
--print-json                         Be quiet and print the video
                                     information as JSON (video is still
                                     being downloaded).
--newline                            Output progress bar as new lines
--no-progress                        Do not print progress bar
--console-title                      Display progress in console titlebar
-v, --verbose                        Print various debugging information
--dump-pages                         Print downloaded pages encoded using
                                     base64 to debug problems (very verbose)
--write-pages                        Write downloaded intermediary pages to
                                     files in the current directory to debug
                                     problems
--print-traffic                      Display sent and read HTTP traffic
-C, --call-home                      Contact the youtube-dl server for
                                     debugging
--no-call-home                       Do NOT contact the youtube-dl server
                                     for debugging

Workarounds:

--encoding ENCODING                  Force the specified encoding
                                     (experimental)
--no-check-certificate               Suppress HTTPS certificate validation
--prefer-insecure                    Use an unencrypted connection to
                                     retrieve information about the video.
                                     (Currently supported only for YouTube)
--user-agent UA                      Specify a custom user agent
--referer URL                        Specify a custom referer, use if the
                                     video access is restricted to one
                                     domain
--add-header FIELD:VALUE             Specify a custom HTTP header and its
                                     value, separated by a colon ':'. You
                                     can use this option multiple times
--bidi-workaround                    Work around terminals that lack
                                     bidirectional text support. Requires
                                     bidiv or fribidi executable in PATH
--sleep-interval SECONDS             Number of seconds to sleep before each
                                     download when used alone or a lower
                                     bound of a range for randomized sleep
                                     before each download (minimum possible
                                     number of seconds to sleep) when used
                                     along with --max-sleep-interval.
--max-sleep-interval SECONDS         Upper bound of a range for randomized
                                     sleep before each download (maximum
                                     possible number of seconds to sleep).
                                     Must only be used along with --min-
                                     sleep-interval.

Video Format Options:

-f, --format FORMAT                  Video format code, see the "FORMAT
                                     SELECTION" for all the info
--all-formats                        Download all available video formats
--prefer-free-formats                Prefer free video formats unless a
                                     specific one is requested
-F, --list-formats                   List all available formats of requested
                                     videos
--youtube-skip-dash-manifest         Do not download the DASH manifests and
                                     related data on YouTube videos
--merge-output-format FORMAT         If a merge is required (e.g.
                                     bestvideo+bestaudio), output to given
                                     container format. One of mkv, mp4, ogg,
                                     webm, flv. Ignored if no merge is
                                     required

Subtitle Options:

--write-sub                          Write subtitle file
--write-auto-sub                     Write automatically generated subtitle
                                     file (YouTube only)
--all-subs                           Download all the available subtitles of
                                     the video
--list-subs                          List all available subtitles for the
                                     video
--sub-format FORMAT                  Subtitle format, accepts formats
                                     preference, for example: "srt" or
                                     "ass/srt/best"
--sub-lang LANGS                     Languages of the subtitles to download
                                     (optional) separated by commas, use
                                     --list-subs for available language tags

Authentication Options:

-u, --username USERNAME              Login with this account ID
-p, --password PASSWORD              Account password. If this option is
                                     left out, youtube-dl will ask
                                     interactively.
-2, --twofactor TWOFACTOR            Two-factor authentication code
-n, --netrc                          Use .netrc authentication data
--video-password PASSWORD            Video password (vimeo, youku)

Adobe Pass Options:

--ap-mso MSO                         Adobe Pass multiple-system operator (TV
                                     provider) identifier, use --ap-list-mso
                                     for a list of available MSOs
--ap-username USERNAME               Multiple-system operator account login
--ap-password PASSWORD               Multiple-system operator account
                                     password. If this option is left out,
                                     youtube-dl will ask interactively.
--ap-list-mso                        List all supported multiple-system
                                     operators

Post-processing Options:

-x, --extract-audio                  Convert video files to audio-only files
                                     (requires ffmpeg/avconv and
                                     ffprobe/avprobe)
--audio-format FORMAT                Specify audio format: "best", "aac",
                                     "flac", "mp3", "m4a", "opus", "vorbis",
                                     or "wav"; "best" by default; No effect
                                     without -x
--audio-quality QUALITY              Specify ffmpeg/avconv audio quality,
                                     insert a value between 0 (better) and 9
                                     (worse) for VBR or a specific bitrate
                                     like 128K (default 5)
--recode-video FORMAT                Encode the video to another format if
                                     necessary (currently supported:
                                     mp4|flv|ogg|webm|mkv|avi)
--postprocessor-args ARGS            Give these arguments to the
                                     postprocessor
-k, --keep-video                     Keep the video file on disk after the
                                     post-processing; the video is erased by
                                     default
--no-post-overwrites                 Do not overwrite post-processed files;
                                     the post-processed files are
                                     overwritten by default
--embed-subs                         Embed subtitles in the video (only for
                                     mp4, webm and mkv videos)
--embed-thumbnail                    Embed thumbnail in the audio as cover
                                     art
--add-metadata                       Write metadata to the video file
--metadata-from-title FORMAT         Parse additional metadata like song
                                     title / artist from the video title.
                                     The format syntax is the same as
                                     --output. Regular expression with named
                                     capture groups may also be used. The
                                     parsed parameters replace existing
                                     values. Example: --metadata-from-title
                                     "%(artist)s - %(title)s" matches a
                                     title like "Coldplay - Paradise".
                                     Example (regex): --metadata-from-title
                                     "(?P<artist>.+?) - (?P<title>.+)"
--xattrs                             Write metadata to the video file's
                                     xattrs (using dublin core and xdg
                                     standards)
--fixup POLICY                       Automatically correct known faults of
                                     the file. One of never (do nothing),
                                     warn (only emit a warning),
                                     detect_or_warn (the default; fix file
                                     if we can, warn otherwise)
--prefer-avconv                      Prefer avconv over ffmpeg for running
                                     the postprocessors
--prefer-ffmpeg                      Prefer ffmpeg over avconv for running
                                     the postprocessors (default)
--ffmpeg-location PATH               Location of the ffmpeg/avconv binary;
                                     either the path to the binary or its
                                     containing directory.
--exec CMD                           Execute a command on the file after
                                     downloading and post-processing,
                                     similar to find's -exec syntax.
                                     Example: --exec 'adb push {}
                                     /sdcard/Music/ && rm {}'
--convert-subs FORMAT                Convert the subtitles to other format
                                     (currently supported: srt|ass|vtt|lrc)

CONFIGURATION

You can configure youtube-dl by placing any supported command line option to a configuration file. On Linux and macOS, the system wide configuration file is located at /etc/youtube-dl.conf and the user wide configuration file at ~/.config/youtube-dl/config. On Windows, the user wide configuration file locations are %APPDATA%\youtube-dl\config.txt or C:\Users\<user name>\youtube-dl.conf. Note that by default configuration file may not exist so you may need to create it yourself.

For example, with the following configuration file youtube-dl will always extract the audio, not copy the mtime, use a proxy and save all videos under Movies directory in your home directory:

# Lines starting with # are comments

# Always extract audio
-x

# Do not copy the mtime
--no-mtime

# Use this proxy
--proxy 127.0.0.1:3128

# Save all videos under Movies directory in your home directory
-o ~/Movies/%(title)s.%(ext)s

Note that options in configuration file are just the same options aka switches used in regular command line calls thus there must be no whitespace after - or --, e.g. -o or --proxy but not - o or -- proxy.

You can use --ignore-config if you want to disable the configuration file for a particular youtube-dl run.

You can also use --config-location if you want to use custom configuration file for a particular youtube-dl run.

Authentication with `.netrc` file

You may also want to configure automatic credentials storage for extractors that support authentication (by providing login and password with --username and --password) in order not to pass credentials as command line arguments on every youtube-dl execution and prevent tracking plain text passwords in the shell command history. You can achieve this using a .netrc file on a per extractor basis. For that you will need to create a .netrc file in your $HOME and restrict permissions to read/write by only you:

1
2

touch $HOME/.netrc
chmod a-rwx,u+rw $HOME/.netrc

After that you can add credentials for an extractor in the following format, where extractor is the name of the extractor in lowercase:

`1`	`machine <extractor> login <login> password <password>`

For example:

1
2

machine youtube login myaccount@gmail.com password my_youtube_password
machine twitch login my_twitch_account_name password my_twitch_password

To activate authentication with the .netrc file you should pass --netrc to youtube-dl or place it in the configuration file.

On Windows you may also need to setup the %HOME% environment variable manually. For example:

`1`	`set HOME=%USERPROFILE%`

OUTPUT TEMPLATE

The -o option allows users to indicate a template for the output file names.

tl;dr: navigate me to examples.

The basic usage is not to set any template arguments when downloading a single file, like in youtube-dl -o funny_video.flv "https://some/video". However, it may contain special sequences that will be replaced when downloading each video. The special sequences may be formatted according to python string formatting operations. For example, %(NAME)s or %(NAME)05d. To clarify, that is a percent symbol followed by a name in parentheses, followed by formatting operations. Allowed names along with sequence type are:

id (string): Video identifier
title (string): Video title
url (string): Video URL
ext (string): Video filename extension
alt_title (string): A secondary title of the video
display_id (string): An alternative identifier for the video
uploader (string): Full name of the video uploader
license (string): License name the video is licensed under
creator (string): The creator of the video
release_date (string): The date (YYYYMMDD) when the video was released
timestamp (numeric): UNIX timestamp of the moment the video became available
upload_date (string): Video upload date (YYYYMMDD)
uploader_id (string): Nickname or id of the video uploader
channel (string): Full name of the channel the video is uploaded on
channel_id (string): Id of the channel
location (string): Physical location where the video was filmed
duration (numeric): Length of the video in seconds
view_count (numeric): How many users have watched the video on the platform
like_count (numeric): Number of positive ratings of the video
dislike_count (numeric): Number of negative ratings of the video
repost_count (numeric): Number of reposts of the video
average_rating (numeric): Average rating give by users, the scale used depends on the webpage
comment_count (numeric): Number of comments on the video
age_limit (numeric): Age restriction for the video (years)
is_live (boolean): Whether this video is a live stream or a fixed-length video
start_time (numeric): Time in seconds where the reproduction should start, as specified in the URL
end_time (numeric): Time in seconds where the reproduction should end, as specified in the URL
format (string): A human-readable description of the format
format_id (string): Format code specified by --format
format_note (string): Additional info about the format
width (numeric): Width of the video
height (numeric): Height of the video
resolution (string): Textual description of width and height
tbr (numeric): Average bitrate of audio and video in KBit/s
abr (numeric): Average audio bitrate in KBit/s
acodec (string): Name of the audio codec in use
asr (numeric): Audio sampling rate in Hertz
vbr (numeric): Average video bitrate in KBit/s
fps (numeric): Frame rate
vcodec (string): Name of the video codec in use
container (string): Name of the container format
filesize (numeric): The number of bytes, if known in advance
filesize_approx (numeric): An estimate for the number of bytes
protocol (string): The protocol that will be used for the actual download
extractor (string): Name of the extractor
extractor_key (string): Key name of the extractor
epoch (numeric): Unix epoch when creating the file
autonumber (numeric): Number that will be increased with each download, starting at --autonumber-start
playlist (string): Name or id of the playlist that contains the video
playlist_index (numeric): Index of the video in the playlist padded with leading zeros according to the total length of the playlist
playlist_id (string): Playlist identifier
playlist_title (string): Playlist title
playlist_uploader (string): Full name of the playlist uploader
playlist_uploader_id (string): Nickname or id of the playlist uploader

Available for the video that belongs to some logical chapter or section:

chapter (string): Name or title of the chapter the video belongs to
chapter_number (numeric): Number of the chapter the video belongs to
chapter_id (string): Id of the chapter the video belongs to

Available for the video that is an episode of some series or programme:

series (string): Title of the series or programme the video episode belongs to
season (string): Title of the season the video episode belongs to
season_number (numeric): Number of the season the video episode belongs to
season_id (string): Id of the season the video episode belongs to
episode (string): Title of the video episode
episode_number (numeric): Number of the video episode within a season
episode_id (string): Id of the video episode

Available for the media that is a track or a part of a music album:

track (string): Title of the track
track_number (numeric): Number of the track within an album or a disc
track_id (string): Id of the track
artist (string): Artist(s) of the track
genre (string): Genre(s) of the track
album (string): Title of the album the track belongs to
album_type (string): Type of the album
album_artist (string): List of all artists appeared on the album
disc_number (numeric): Number of the disc or other physical medium the track belongs to
release_year (numeric): Year (YYYY) when the album was released

Each aforementioned sequence when referenced in an output template will be replaced by the actual value corresponding to the sequence name. Note that some of the sequences are not guaranteed to be present since they depend on the metadata obtained by a particular extractor. Such sequences will be replaced with placeholder value provided with --output-na-placeholder (NA by default).

For example for -o %(title)s-%(id)s.%(ext)s and an mp4 video with title youtube-dl test video and id BaW_jenozKcj, this will result in a youtube-dl test video-BaW_jenozKcj.mp4 file created in the current directory.

For numeric sequences you can use numeric related formatting, for example, %(view_count)05d will result in a string with view count padded with zeros up to 5 characters, like in 00042.

Output templates can also contain arbitrary hierarchical path, e.g. -o '%(playlist)s/%(playlist_index)s - %(title)s.%(ext)s' which will result in downloading each video in a directory corresponding to this path template. Any missing directory will be automatically created for you.

To use percent literals in an output template use %%. To output to stdout use -o -.

The current default template is %(title)s-%(id)s.%(ext)s.

In some cases, you don’t want special characters such as 中, spaces, or &, such as when transferring the downloaded filename to a Windows system or the filename through an 8bit-unsafe channel. In these cases, add the --restrict-filenames flag to get a shorter title.

Output template and Windows batch files

If you are using an output template inside a Windows batch file then you must escape plain percent characters (%) by doubling, so that -o "%(title)s-%(id)s.%(ext)s" should become -o "%%(title)s-%%(id)s.%%(ext)s". However you should not touch %’s that are not plain characters, e.g. environment variables for expansion should stay intact: -o "C:\%HOMEPATH%\Desktop\%%(title)s.%%(ext)s".

Output template examples

Note that on Windows you may need to use double quotes instead of single.

$ youtube-dl --get-filename -o '%(title)s.%(ext)s' BaW_jenozKc
youtube-dl test video ''_ä↭𝕐.mp4    # All kinds of weird characters

$ youtube-dl --get-filename -o '%(title)s.%(ext)s' BaW_jenozKc --restrict-filenames
youtube-dl_test_video_.mp4          # A simple file name

# Download YouTube playlist videos in separate directory indexed by video order in a playlist
$ youtube-dl -o '%(playlist)s/%(playlist_index)s - %(title)s.%(ext)s' https://www.youtube.com/playlist?list=PLwiyx1dc3P2JR9N8gQaQN_BCvlSlap7re

# Download all playlists of YouTube channel/user keeping each playlist in separate directory:
$ youtube-dl -o '%(uploader)s/%(playlist)s/%(playlist_index)s - %(title)s.%(ext)s' https://www.youtube.com/user/TheLinuxFoundation/playlists

# Download Udemy course keeping each chapter in separate directory under MyVideos directory in your home
$ youtube-dl -u user -p password -o '~/MyVideos/%(playlist)s/%(chapter_number)s - %(chapter)s/%(title)s.%(ext)s' https://www.udemy.com/java-tutorial/

# Download entire series season keeping each series and each season in separate directory under C:/MyVideos
$ youtube-dl -o "C:/MyVideos/%(series)s/%(season_number)s - %(season)s/%(episode_number)s - %(episode)s.%(ext)s" https://videomore.ru/kino_v_detalayah/5_sezon/367617

# Stream the video being downloaded to stdout
$ youtube-dl -o - BaW_jenozKc

FORMAT SELECTION

By default youtube-dl tries to download the best available quality, i.e. if you want the best quality you don’t need to pass any special options, youtube-dl will guess it for you by default.

But sometimes you may want to download in a different format, for example when you are on a slow or intermittent connection. The key mechanism for achieving this is so-called format selection based on which you can explicitly specify desired format, select formats based on some criterion or criteria, setup precedence and much more.

The general syntax for format selection is --format FORMAT or shorter -f FORMAT where FORMAT is a selector expression, i.e. an expression that describes format or formats you would like to download.

tl;dr: navigate me to examples.

The simplest case is requesting a specific format, for example with -f 22 you can download the format with format code equal to 22. You can get the list of available format codes for particular video using --list-formats or -F. Note that these format codes are extractor specific.

You can also use a file extension (currently 3gp, aac, flv, m4a, mp3, mp4, ogg, wav, webm are supported) to download the best quality format of a particular file extension served as a single file, e.g. -f webm will download the best quality format with the webm extension served as a single file.

You can also use special names to select particular edge case formats:

best: Select the best quality format represented by a single file with video and audio.
worst: Select the worst quality format represented by a single file with video and audio.
bestvideo: Select the best quality video-only format (e.g. DASH video). May not be available.
worstvideo: Select the worst quality video-only format. May not be available.
bestaudio: Select the best quality audio only-format. May not be available.
worstaudio: Select the worst quality audio only-format. May not be available.

For example, to download the worst quality video-only format you can use -f worstvideo.

If you want to download multiple videos and they don’t have the same formats available, you can specify the order of preference using slashes. Note that slash is left-associative, i.e. formats on the left hand side are preferred, for example -f 22/17/18 will download format 22 if it’s available, otherwise it will download format 17 if it’s available, otherwise it will download format 18 if it’s available, otherwise it will complain that no suitable formats are available for download.

If you want to download several formats of the same video use a comma as a separator, e.g. -f 22,17,18 will download all these three formats, of course if they are available. Or a more sophisticated example combined with the precedence feature: -f 136/137/mp4/bestvideo,140/m4a/bestaudio.

You can also filter the video formats by putting a condition in brackets, as in -f "best[height=720]" (or -f "[filesize>10M]").

The following numeric meta fields can be used with comparisons <, <=, >, >=, = (equals), != (not equals):

filesize: The number of bytes, if known in advance
width: Width of the video, if known
height: Height of the video, if known
tbr: Average bitrate of audio and video in KBit/s
abr: Average audio bitrate in KBit/s
vbr: Average video bitrate in KBit/s
asr: Audio sampling rate in Hertz
fps: Frame rate

Also filtering work for comparisons = (equals), ^= (starts with), $= (ends with), *= (contains) and following string meta fields:

ext: File extension
acodec: Name of the audio codec in use
vcodec: Name of the video codec in use
container: Name of the container format
protocol: The protocol that will be used for the actual download, lower-case (http, https, rtsp, rtmp, rtmpe, mms, f4m, ism, http_dash_segments, m3u8, or m3u8_native)
format_id: A short description of the format
language: Language code

Any string comparison may be prefixed with negation ! in order to produce an opposite comparison, e.g. !*= (does not contain).

Note that none of the aforementioned meta fields are guaranteed to be present since this solely depends on the metadata obtained by particular extractor, i.e. the metadata offered by the video hoster.

Formats for which the value is not known are excluded unless you put a question mark (?) after the operator. You can combine format filters, so -f "[height <=? 720][tbr>500]" selects up to 720p videos (or videos where the height is not known) with a bitrate of at least 500 KBit/s.

You can merge the video and audio of two formats into a single file using -f <video-format>+<audio-format> (requires ffmpeg or avconv installed), for example -f bestvideo+bestaudio will download the best video-only format, the best audio-only format and mux them together with ffmpeg/avconv.

Format selectors can also be grouped using parentheses, for example if you want to download the best mp4 and webm formats with a height lower than 480 you can use -f '(mp4,webm)[height<480]'.

Since the end of April 2015 and version 2015.04.26, youtube-dl uses -f bestvideo+bestaudio/best as the default format selection (see #5447, #5456). If ffmpeg or avconv are installed this results in downloading bestvideo and bestaudio separately and muxing them together into a single file giving the best overall quality available. Otherwise it falls back to best and results in downloading the best available quality served as a single file. best is also needed for videos that don’t come from YouTube because they don’t provide the audio and video in two different files. If you want to only download some DASH formats (for example if you are not interested in getting videos with a resolution higher than 1080p), you can add -f bestvideo[height<=?1080]+bestaudio/best to your configuration file. Note that if you use youtube-dl to stream to stdout (and most likely to pipe it to your media player then), i.e. you explicitly specify output template as -o -, youtube-dl still uses -f best format selection in order to start content delivery immediately to your player and not to wait until bestvideo and bestaudio are downloaded and muxed.

If you want to preserve the old format selection behavior (prior to youtube-dl 2015.04.26), i.e. you want to download the best available quality media served as a single file, you should explicitly specify your choice with -f best. You may want to add it to the configuration file in order not to type it every time you run youtube-dl.

Format selection examples

Note that on Windows you may need to use double quotes instead of single.

# Download best mp4 format available or any other best if no mp4 available
$ youtube-dl -f 'bestvideo[ext=mp4]+bestaudio[ext=m4a]/best[ext=mp4]/best'

# Download best format available but no better than 480p
$ youtube-dl -f 'bestvideo[height<=480]+bestaudio/best[height<=480]'

# Download best video only format but no bigger than 50 MB
$ youtube-dl -f 'best[filesize<50M]'

# Download best format available via direct link over HTTP/HTTPS protocol
$ youtube-dl -f '(bestvideo+bestaudio/best)[protocol^=http]'

# Download the best video format and the best audio format without merging them
$ youtube-dl -f 'bestvideo,bestaudio' -o '%(title)s.f%(format_id)s.%(ext)s'

Note that in the last example, an output template is recommended as bestvideo and bestaudio may have the same file name.

VIDEO SELECTION

Videos can be filtered by their upload date using the options --date, --datebefore or --dateafter. They accept dates in two formats:

Absolute dates: Dates in the format YYYYMMDD.
Relative dates: Dates in the format (now|today)[+-][0-9](day|week|month|year)(s)?

Examples:

# Download only the videos uploaded in the last 6 months
$ youtube-dl --dateafter now-6months

# Download only the videos uploaded on January 1, 1970
$ youtube-dl --date 19700101

$ # Download only the videos uploaded in the 200x decade
$ youtube-dl --dateafter 20000101 --datebefore 20091231

FAQ

How do I update youtube-dl?

If you’ve followed our manual installation instructions, you can simply run youtube-dl -U (or, on Linux, sudo youtube-dl -U).

If you have used pip, a simple sudo pip install -U youtube-dl is sufficient to update.

If you have installed youtube-dl using a package manager like apt-get or yum, use the standard system update mechanism to update. Note that distribution packages are often outdated. As a rule of thumb, youtube-dl releases at least once a month, and often weekly or even daily. Simply go to https://yt-dl.org to find out the current version. Unfortunately, there is nothing we youtube-dl developers can do if your distribution serves a really outdated version. You can (and should) complain to your distribution in their bugtracker or support forum.

As a last resort, you can also uninstall the version installed by your package manager and follow our manual installation instructions. For that, remove the distribution’s package, with a line like

sudo apt-get remove -y youtube-dl

Afterwards, simply follow our manual installation instructions:

1
2
3

sudo wget https://yt-dl.org/downloads/latest/youtube-dl -O /usr/local/bin/youtube-dl
sudo chmod a+rx /usr/local/bin/youtube-dl
hash -r

Again, from then on you’ll be able to update with sudo youtube-dl -U.

youtube-dl is extremely slow to start on Windows

Add a file exclusion for youtube-dl.exe in Windows Defender settings.

I’m getting an error `Unable to extract OpenGraph title` on YouTube playlists

YouTube changed their playlist format in March 2014 and later on, so you’ll need at least youtube-dl 2014.07.25 to download all YouTube videos.

If you have installed youtube-dl with a package manager, pip, setup.py or a tarball, please use that to update. Note that Ubuntu packages do not seem to get updated anymore. Since we are not affiliated with Ubuntu, there is little we can do. Feel free to report bugs to the Ubuntu packaging people - all they have to do is update the package to a somewhat recent version. See above for a way to update.

I’m getting an error when trying to use output template: `error: using output template conflicts with using title, video ID or auto number`

Make sure you are not using -o with any of these options -t, --title, --id, -A or --auto-number set in command line or in a configuration file. Remove the latter if any.

Do I always have to pass `-citw`?

By default, youtube-dl intends to have the best options (incidentally, if you have a convincing case that these should be different, please file an issue where you explain that). Therefore, it is unnecessary and sometimes harmful to copy long option strings from webpages. In particular, the only option out of -citw that is regularly useful is -i.

Can you please put the `-b` option back?

Most people asking this question are not aware that youtube-dl now defaults to downloading the highest available quality as reported by YouTube, which will be 1080p or 720p in some cases, so you no longer need the -b option. For some specific videos, maybe YouTube does not report them to be available in a specific high quality format you’re interested in. In that case, simply request it with the -f option and youtube-dl will try to download it.

I get HTTP error 402 when trying to download a video. What’s this?

Apparently YouTube requires you to pass a CAPTCHA test if you download too much. We’re considering to provide a way to let you solve the CAPTCHA, but at the moment, your best course of action is pointing a web browser to the youtube URL, solving the CAPTCHA, and restart youtube-dl.

Do I need any other programs?

youtube-dl works fine on its own on most sites. However, if you want to convert video/audio, you’ll need avconv or ffmpeg. On some sites - most notably YouTube - videos can be retrieved in a higher quality format without sound. youtube-dl will detect whether avconv/ffmpeg is present and automatically pick the best option.

Videos or video formats streamed via RTMP protocol can only be downloaded when rtmpdump is installed. Downloading MMS and RTSP videos requires either mplayer or mpv to be installed.

I have downloaded a video but how can I play it?

Once the video is fully downloaded, use any video player, such as mpv, vlc or mplayer.

I extracted a video URL with `-g`, but it does not play on another machine / in my web browser.

It depends a lot on the service. In many cases, requests for the video (to download/play it) must come from the same IP address and with the same cookies and/or HTTP headers. Use the --cookies option to write the required cookies into a file, and advise your downloader to read cookies from that file. Some sites also require a common user agent to be used, use --dump-user-agent to see the one in use by youtube-dl. You can also get necessary cookies and HTTP headers from JSON output obtained with --dump-json.

It may be beneficial to use IPv6; in some cases, the restrictions are only applied to IPv4. Some services (sometimes only for a subset of videos) do not restrict the video URL by IP address, cookie, or user-agent, but these are the exception rather than the rule.

Please bear in mind that some URL protocols are not supported by browsers out of the box, including RTMP. If you are using -g, your own downloader must support these as well.

If you want to play the video on a machine that is not running youtube-dl, you can relay the video content from the machine that runs youtube-dl. You can use -o - to let youtube-dl stream a video to stdout, or simply allow the player to download the files written by youtube-dl in turn.

ERROR: no fmt_url_map or conn information found in video info

YouTube has switched to a new video info format in July 2011 which is not supported by old versions of youtube-dl. See above for how to update youtube-dl.

ERROR: unable to download video

YouTube requires an additional signature since September 2012 which is not supported by old versions of youtube-dl. See above for how to update youtube-dl.

Video URL contains an ampersand and I’m getting some strange output `[1] 2839` or `'v' is not recognized as an internal or external command`

That’s actually the output from your shell. Since ampersand is one of the special shell characters it’s interpreted by the shell preventing you from passing the whole URL to youtube-dl. To disable your shell from interpreting the ampersands (or any other special characters) you have to either put the whole URL in quotes or escape them with a backslash (which approach will work depends on your shell).

For example if your URL is https://www.youtube.com/watch?t=4&v=BaW_jenozKc you should end up with following command:

youtube-dl 'https://www.youtube.com/watch?t=4&v=BaW_jenozKc'

youtube-dl https://www.youtube.com/watch?t=4\&v=BaW_jenozKc

For Windows you have to use the double quotes:

youtube-dl "https://www.youtube.com/watch?t=4&v=BaW_jenozKc"

ExtractorError: Could not find JS function u’OF'

In February 2015, the new YouTube player contained a character sequence in a string that was misinterpreted by old versions of youtube-dl. See above for how to update youtube-dl.

HTTP Error 429: Too Many Requests or 402: Payment Required

These two error codes indicate that the service is blocking your IP address because of overuse. Usually this is a soft block meaning that you can gain access again after solving CAPTCHA. Just open a browser and solve a CAPTCHA the service suggests you and after that pass cookies to youtube-dl. Note that if your machine has multiple external IPs then you should also pass exactly the same IP you’ve used for solving CAPTCHA with --source-address. Also you may need to pass a User-Agent HTTP header of your browser with --user-agent.

If this is not the case (no CAPTCHA suggested to solve by the service) then you can contact the service and ask them to unblock your IP address, or - if you have acquired a whitelisted IP address already - use the --proxy or --source-address options to select another IP address.

SyntaxError: Non-ASCII character

The error

File "youtube-dl", line 2
SyntaxError: Non-ASCII character '\x93' ...

means you’re using an outdated version of Python. Please update to Python 2.6 or 2.7.

What is this binary file? Where has the code gone?

Since June 2012 (#342) youtube-dl is packed as an executable zipfile, simply unzip it (might need renaming to youtube-dl.zip first on some systems) or clone the git repository, as laid out above. If you modify the code, you can run it by executing the __main__.py file. To recompile the executable, run make youtube-dl.

The exe throws an error due to missing `MSVCR100.dll`

To run the exe you need to install first the Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package (x86).

On Windows, how should I set up ffmpeg and youtube-dl? Where should I put the exe files?

If you put youtube-dl and ffmpeg in the same directory that you’re running the command from, it will work, but that’s rather cumbersome.

To make a different directory work - either for ffmpeg, or for youtube-dl, or for both - simply create the directory (say, C:\bin, or C:\Users\<User name>\bin), put all the executables directly in there, and then set your PATH environment variable to include that directory.

From then on, after restarting your shell, you will be able to access both youtube-dl and ffmpeg (and youtube-dl will be able to find ffmpeg) by simply typing youtube-dl or ffmpeg, no matter what directory you’re in.

How do I put downloads into a specific folder?

Use the -o to specify an output template, for example -o "/home/user/videos/%(title)s-%(id)s.%(ext)s". If you want this for all of your downloads, put the option into your configuration file.

How do I download a video starting with a `-`?

Either prepend https://www.youtube.com/watch?v= or separate the ID from the options with --:

youtube-dl -- -wNyEUrxzFU
youtube-dl "https://www.youtube.com/watch?v=-wNyEUrxzFU"

How do I pass cookies to youtube-dl?

Use the --cookies option, for example --cookies /path/to/cookies/file.txt.

In order to extract cookies from browser use any conforming browser extension for exporting cookies. For example, Get cookies.txt LOCALLY (for Chrome) or cookies.txt (for Firefox).

Note that the cookies file must be in Mozilla/Netscape format and the first line of the cookies file must be either # HTTP Cookie File or # Netscape HTTP Cookie File. Make sure you have correct newline format in the cookies file and convert newlines if necessary to correspond with your OS, namely CRLF (\r\n) for Windows and LF (\n) for Unix and Unix-like systems (Linux, macOS, etc.). HTTP Error 400: Bad Request when using --cookies is a good sign of invalid newline format.

Passing cookies to youtube-dl is a good way to workaround login when a particular extractor does not implement it explicitly. Another use case is working around CAPTCHA some websites require you to solve in particular cases in order to get access (e.g. YouTube, CloudFlare).

How do I stream directly to media player?

You will first need to tell youtube-dl to stream media to stdout with -o -, and also tell your media player to read from stdin (it must be capable of this for streaming) and then pipe former to latter. For example, streaming to vlc can be achieved with:

youtube-dl -o - "https://www.youtube.com/watch?v=BaW_jenozKcj" | vlc -

How do I download only new videos from a playlist?

Use download-archive feature. With this feature you should initially download the complete playlist with --download-archive /path/to/download/archive/file.txt that will record identifiers of all the videos in a special file. Each subsequent run with the same --download-archive will download only new videos and skip all videos that have been downloaded before. Note that only successful downloads are recorded in the file.

For example, at first,

youtube-dl --download-archive archive.txt "https://www.youtube.com/playlist?list=PLwiyx1dc3P2JR9N8gQaQN_BCvlSlap7re"

will download the complete PLwiyx1dc3P2JR9N8gQaQN_BCvlSlap7re playlist and create a file archive.txt. Each subsequent run will only download new videos if any:

youtube-dl --download-archive archive.txt "https://www.youtube.com/playlist?list=PLwiyx1dc3P2JR9N8gQaQN_BCvlSlap7re"

Should I add `--hls-prefer-native` into my config?

When youtube-dl detects an HLS video, it can download it either with the built-in downloader or ffmpeg. Since many HLS streams are slightly invalid and ffmpeg/youtube-dl each handle some invalid cases better than the other, there is an option to switch the downloader if needed.

When youtube-dl knows that one particular downloader works better for a given website, that downloader will be picked. Otherwise, youtube-dl will pick the best downloader for general compatibility, which at the moment happens to be ffmpeg. This choice may change in future versions of youtube-dl, with improvements of the built-in downloader and/or ffmpeg.

In particular, the generic extractor (used when your website is not in the list of supported sites by youtube-dl cannot mandate one specific downloader.

If you put either --hls-prefer-native or --hls-prefer-ffmpeg into your configuration, a different subset of videos will fail to download correctly. Instead, it is much better to file an issue or a pull request which details why the native or the ffmpeg HLS downloader is a better choice for your use case.

Can you add support for this anime video site, or site which shows current movies for free?

As a matter of policy (as well as legality), youtube-dl does not include support for services that specialize in infringing copyright. As a rule of thumb, if you cannot easily find a video that the service is quite obviously allowed to distribute (i.e. that has been uploaded by the creator, the creator’s distributor, or is published under a free license), the service is probably unfit for inclusion to youtube-dl.

A note on the service that they don’t host the infringing content, but just link to those who do, is evidence that the service should not be included into youtube-dl. The same goes for any DMCA note when the whole front page of the service is filled with videos they are not allowed to distribute. A “fair use” note is equally unconvincing if the service shows copyright-protected videos in full without authorization.

Support requests for services that do purchase the rights to distribute their content are perfectly fine though. If in doubt, you can simply include a source that mentions the legitimate purchase of content.

How can I speed up work on my issue?

(Also known as: Help, my important issue not being solved!) The youtube-dl core developer team is quite small. While we do our best to solve as many issues as possible, sometimes that can take quite a while. To speed up your issue, here’s what you can do:

First of all, please do report the issue at our issue tracker. That allows us to coordinate all efforts by users and developers, and serves as a unified point. Unfortunately, the youtube-dl project has grown too large to use personal email as an effective communication channel.

Please read the bug reporting instructions below. A lot of bugs lack all the necessary information. If you can, offer proxy, VPN, or shell access to the youtube-dl developers. If you are able to, test the issue from multiple computers in multiple countries to exclude local censorship or misconfiguration issues.

If nobody is interested in solving your issue, you are welcome to take matters into your own hands and submit a pull request (or coerce/pay somebody else to do so).

Feel free to bump the issue from time to time by writing a small comment (“Issue is still present in youtube-dl version …from France, but fixed from Belgium”), but please not more than once a month. Please do not declare your issue as important or urgent.

How can I detect whether a given URL is supported by youtube-dl?

For one, have a look at the list of supported sites. Note that it can sometimes happen that the site changes its URL scheme (say, from https://example.com/video/1234567 to https://example.com/v/1234567 ) and youtube-dl reports an URL of a service in that list as unsupported. In that case, simply report a bug.

It is not possible to detect whether a URL is supported or not. That’s because youtube-dl contains a generic extractor which matches all URLs. You may be tempted to disable, exclude, or remove the generic extractor, but the generic extractor not only allows users to extract videos from lots of websites that embed a video from another service, but may also be used to extract video from a service that it’s hosting itself. Therefore, we neither recommend nor support disabling, excluding, or removing the generic extractor.

If you want to find out whether a given URL is supported, simply call youtube-dl with it. If you get no videos back, chances are the URL is either not referring to a video or unsupported. You can find out which by examining the output (if you run youtube-dl on the console) or catching an UnsupportedError exception if you run it from a Python program.

Why do I need to go through that much red tape when filing bugs?

Before we had the issue template, despite our extensive bug reporting instructions, about 80% of the issue reports we got were useless, for instance because people used ancient versions hundreds of releases old, because of simple syntactic errors (not in youtube-dl but in general shell usage), because the problem was already reported multiple times before, because people did not actually read an error message, even if it said “please install ffmpeg”, because people did not mention the URL they were trying to download and many more simple, easy-to-avoid problems, many of whom were totally unrelated to youtube-dl.

youtube-dl is an open-source project manned by too few volunteers, so we’d rather spend time fixing bugs where we are certain none of those simple problems apply, and where we can be reasonably confident to be able to reproduce the issue without asking the reporter repeatedly. As such, the output of youtube-dl -v YOUR_URL_HERE is really all that’s required to file an issue. The issue template also guides you through some basic steps you can do, such as checking that your version of youtube-dl is current.

DEVELOPER INSTRUCTIONS

Most users do not need to build youtube-dl and can download the builds or get them from their distribution.

To run youtube-dl as a developer, you don’t need to build anything either. Simply execute

python -m youtube_dl

To run the test, simply invoke your favorite test runner, or execute a test file directly; any of the following work:

python -m unittest discover
python test/test_download.py
nosetests

For Python versions 3.6 and later, you can use pynose to implement nosetests. The original nose has not been upgraded for 3.10 and later.

See item 6 of new extractor tutorial for how to run extractor specific test cases.

If you want to create a build of youtube-dl yourself, you’ll need

python
make (only GNU make is supported)
pandoc
zip
nosetests

Adding support for a new site

If you want to add support for a new site, first of all make sure this site is not dedicated to copyright infringement. youtube-dl does not support such sites thus pull requests adding support for them will be rejected.

After you have ensured this site is distributing its content legally, you can follow this quick list (assuming your service is called yourextractor):

Fork this repository

Check out the source code with:

 git clone git@github.com:YOUR_GITHUB_USERNAME/youtube-dl.git

Start a new git branch with

 cd youtube-dl
 git checkout -b yourextractor

Start with this simple template and save it to youtube_dl/extractor/yourextractor.py:

# coding: utf-8
from __future__ import unicode_literals

from .common import InfoExtractor


class YourExtractorIE(InfoExtractor):
    _VALID_URL = r'https?://(?:www\.)?yourextractor\.com/watch/(?P<id>[0-9]+)'
    _TEST = {
        'url': 'https://yourextractor.com/watch/42',
        'md5': 'TODO: md5 sum of the first 10241 bytes of the video file (use --test)',
        'info_dict': {
            'id': '42',
            'ext': 'mp4',
            'title': 'Video title goes here',
            'thumbnail': r're:^https?://.*\.jpg$',
            # TODO more properties, either as:
            # * A value
            # * MD5 checksum; start the string with md5:
            # * A regular expression; start the string with re:
            # * Any Python type (for example int or float)
        }
    }

    def _real_extract(self, url):
        video_id = self._match_id(url)
        webpage = self._download_webpage(url, video_id)

        # TODO more code goes here, for example ...
        title = self._html_search_regex(r'<h1>(.+?)</h1>', webpage, 'title')

        return {
            'id': video_id,
            'title': title,
            'description': self._og_search_description(webpage),
            'uploader': self._search_regex(r'<div[^>]+id="uploader"[^>]*>([^<]+)<', webpage, 'uploader', fatal=False),
            # TODO more properties (see youtube_dl/extractor/common.py)
        }

Add an import in youtube_dl/extractor/extractors.py.
Run python test/test_download.py TestDownload.test_YourExtractor. This should fail at first, but you can continually re-run it until you’re done. If you decide to add more than one test (actually, test case) then rename _TEST to _TESTS and make it into a list of dictionaries. The tests will then be named TestDownload.test_YourExtractor, TestDownload.test_YourExtractor_1, TestDownload.test_YourExtractor_2, etc. Note:
- the test names use the extractor class name without the trailing IE
- tests with only_matching key in test’s dict are not counted.
Have a look at youtube_dl/extractor/common.py for possible helper methods and a detailed description of what your extractor should and may return. Add tests and code for as many as you want.
Make sure your code follows youtube-dl coding conventions and check the code with flake8:
```
 $ flake8 youtube_dl/extractor/yourextractor.py
```
Make sure your code works under all Python versions claimed supported by youtube-dl, namely 2.6, 2.7, and 3.2+.

When the tests pass, add the new files and commit them and push the result, like this:

$ git add youtube_dl/extractor/extractors.py
$ git add youtube_dl/extractor/yourextractor.py
$ git commit -m '[yourextractor] Add new extractor'
$ git push origin yourextractor

Finally, create a pull request. We’ll then review and merge it.

In any case, thank you very much for your contributions!

youtube-dl coding conventions

This section introduces guidelines for writing idiomatic, robust and future-proof extractor code.

Extractors are very fragile by nature since they depend on the layout of the source data provided by 3rd party media hosters out of your control and this layout tends to change. As an extractor implementer your task is not only to write code that will extract media links and metadata correctly but also to minimize dependency on the source’s layout and even to make the code foresee potential future changes and be ready for that. This is important because it will allow the extractor not to break on minor layout changes thus keeping old youtube-dl versions working. Even though this breakage issue is easily fixed by emitting a new version of youtube-dl with a fix incorporated, all the previous versions become broken in all repositories and distros’ packages that may not be so prompt in fetching the update from us. Needless to say, some non rolling release distros may never receive an update at all.

Mandatory and optional metafields

For extraction to work youtube-dl relies on metadata your extractor extracts and provides to youtube-dl expressed by an information dictionary or simply info dict. Only the following meta fields in the info dict are considered mandatory for a successful extraction process by youtube-dl:

id (media identifier)
title (media title)
url (media download URL) or formats

In fact only the last option is technically mandatory (i.e. if you can’t figure out the download location of the media the extraction does not make any sense). But by convention youtube-dl also treats id and title as mandatory. Thus the aforementioned metafields are the critical data that the extraction does not make any sense without and if any of them fail to be extracted then the extractor is considered completely broken.

Any field apart from the aforementioned ones are considered optional. That means that extraction should be tolerant to situations when sources for these fields can potentially be unavailable (even if they are always available at the moment) and future-proof in order not to break the extraction of general purpose mandatory fields.

Example

Say you have some source dictionary meta that you’ve fetched as JSON with HTTP request and it has a key summary:

`1`	`meta = self._download_json(url, video_id)`

Assume at this point meta’s layout is:

{
    ...
    "summary": "some fancy summary text",
    ...
}

Assume you want to extract summary and put it into the resulting info dict as description. Since description is an optional meta field you should be ready that this key may be missing from the meta dict, so that you should extract it like:

`1`	`description = meta.get('summary') # correct`

and not like:

`1`	`description = meta['summary'] # incorrect`

The latter will break extraction process with KeyError if summary disappears from meta at some later time but with the former approach extraction will just go ahead with description set to None which is perfectly fine (remember None is equivalent to the absence of data).

Similarly, you should pass fatal=False when extracting optional data from a webpage with _search_regex, _html_search_regex or similar methods, for instance:

1
2
3

description = self._search_regex(
    r'<span[^>]+id="title"[^>]*>([^<]+)<',
    webpage, 'description', fatal=False)

With fatal set to False if _search_regex fails to extract description it will emit a warning and continue extraction.

You can also pass default=<some fallback value>, for example:

1
2
3

description = self._search_regex(
    r'<span[^>]+id="title"[^>]*>([^<]+)<',
    webpage, 'description', default=None)

On failure this code will silently continue the extraction with description set to None. That is useful for metafields that may or may not be present.

Provide fallbacks

When extracting metadata try to do so from multiple sources. For example if title is present in several places, try extracting from at least some of them. This makes it more future-proof in case some of the sources become unavailable.

Example

Say meta from the previous example has a title and you are about to extract it. Since title is a mandatory meta field you should end up with something like:

`1`	`title = meta['title']`

If title disappears from meta in future due to some changes on the hoster’s side the extraction would fail since title is mandatory. That’s expected.

Assume that you have some another source you can extract title from, for example og:title HTML meta of a webpage. In this case you can provide a fallback scenario:

`1`	`title = meta.get('title') or self._og_search_title(webpage)`

This code will try to extract from meta first and if it fails it will try extracting og:title from a webpage.

Regular expressions

Don’t capture groups you don’t use

Capturing group must be an indication that it’s used somewhere in the code. Any group that is not used must be non capturing.

Example

Don’t capture id attribute name here since you can’t use it for anything anyway.

Correct:

`1`	`r'(?:id\|ID)=(?P<id>\d+)'`

Incorrect:

`1`	`r'(id\|ID)=(?P<id>\d+)'`

Make regular expressions relaxed and flexible

When using regular expressions try to write them fuzzy, relaxed and flexible, skipping insignificant parts that are more likely to change, allowing both single and double quotes for quoted values and so on.

Example

Say you need to extract title from the following HTML code:

`1`	`<span style="position: absolute; left: 910px; width: 90px; float: right; z-index: 9999;" class="title">some fancy title</span>`

The code for that task should look similar to:

1
2

title = self._search_regex(
    r'<span[^>]+class="title"[^>]*>([^<]+)', webpage, 'title')

Or even better:

1
2
3

title = self._search_regex(
    r'<span[^>]+class=(["\'])title\1[^>]*>(?P<title>[^<]+)',
    webpage, 'title', group='title')

Note how you tolerate potential changes in the style attribute’s value or switch from using double quotes to single for class attribute:

The code definitely should not look like:

1
2
3

title = self._search_regex(
    r'<span style="position: absolute; left: 910px; width: 90px; float: right; z-index: 9999;" class="title">(.*?)</span>',
    webpage, 'title', group='title')

Long lines policy

There is a soft limit to keep lines of code under 80 characters long. This means it should be respected if possible and if it does not make readability and code maintenance worse.

For example, you should never split long string literals like URLs or some other often copied entities over multiple lines to fit this limit:

Correct:

`1`	`'https://www.youtube.com/watch?v=FqZTN594JQw&list=PLMYEtVRpaqY00V9W81Cwmzp6N6vZqfUKD4'`

Incorrect:

1
2

'https://www.youtube.com/watch?v=FqZTN594JQw&list='
'PLMYEtVRpaqY00V9W81Cwmzp6N6vZqfUKD4'

Inline values

Extracting variables is acceptable for reducing code duplication and improving readability of complex expressions. However, you should avoid extracting variables used only once and moving them to opposite parts of the extractor file, which makes reading the linear flow difficult.

Example

Correct:

`1`	`title = self._html_search_regex(r'<title>([^<]+)</title>', webpage, 'title')`

Incorrect:

1
2
3

TITLE_RE = r'<title>([^<]+)</title>'
# ...some lines of code...
title = self._html_search_regex(TITLE_RE, webpage, 'title')

Collapse fallbacks

Multiple fallback values can quickly become unwieldy. Collapse multiple fallback values into a single expression via a list of patterns.

Example

Good:

1
2
3

description = self._html_search_meta(
    ['og:description', 'description', 'twitter:description'],
    webpage, 'description', default=None)

Unwieldy:

description = (
    self._og_search_description(webpage, default=None)
    or self._html_search_meta('description', webpage, default=None)
    or self._html_search_meta('twitter:description', webpage, default=None))

Methods supporting list of patterns are: _search_regex, _html_search_regex, _og_search_property, _html_search_meta.

Trailing parentheses

Always move trailing parentheses after the last argument.

Example

Correct:

1
2

    lambda x: x['ResultSet']['Result'][0]['VideoUrlSet']['VideoUrl'],
    list)

Incorrect:

1
2
3

    lambda x: x['ResultSet']['Result'][0]['VideoUrlSet']['VideoUrl'],
    list,
)

Use convenience conversion and parsing functions

Wrap all extracted numeric data into safe functions from youtube_dl/utils.py: int_or_none, float_or_none. Use them for string to number conversions as well.

Use url_or_none for safe URL processing.

Use traverse_obj for safe metadata extraction from parsed JSON.

Use unified_strdate for uniform upload_date or any YYYYMMDD meta field extraction, unified_timestamp for uniform timestamp extraction, parse_filesize for filesize extraction, parse_count for count meta fields extraction, parse_resolution, parse_duration for duration extraction, parse_age_limit for age_limit extraction.

Explore youtube_dl/utils.py for more useful convenience functions.

More examples

Safely extract optional description from parsed JSON

When processing complex JSON, as often returned by site API requests or stashed in web pages for “hydration”, you can use the traverse_obj() utility function to handle multiple fallback values and to ensure the expected type of metadata items. The function’s docstring defines how the function works: also review usage in the codebase for more examples.

In this example, a text description, or None, is pulled from the .result.video[0].summary member of the parsed JSON response, if available.

`1`	`description = traverse_obj(response, ('result', 'video', 0, 'summary', T(compat_str)))`

T(...) is a shorthand for a set literal; if you hate people who still run Python 2.6, T(type_or_transformation) could be written as a set literal {type_or_transformation}.

Some extractors use the older and less capable try_get() function in the same way.

`1`	`description = try_get(response, lambda x: x['result']['video'][0]['summary'], compat_str)`

Safely extract more optional metadata

In this example, various optional metadata values are extracted from the .result.video[0] member of the parsed JSON response, which is expected to be a JS object, parsed into a dict, with no crash if that isn’t so, or if any of the target values are missing or invalid.

video = traverse_obj(response, ('result', 'video', 0, T(dict))) or {}
# formerly:
# video = try_get(response, lambda x: x['result']['video'][0], dict) or {}
description = video.get('summary')
duration = float_or_none(video.get('durationMs'), scale=1000)
view_count = int_or_none(video.get('views'))

Safely extract nested lists

Suppose you’ve extracted JSON like this into a Python data structure named media_json using, say, the _download_json() or _parse_json() methods of InfoExtractor:

{
    "title": "Example video",
    "comment": "try extracting this",
    "media": [{
        "type": "bad",
        "size": 320,
        "url": "https://some.cdn.site/bad.mp4"
    }, {
        "type": "streaming",
        "url": "https://some.cdn.site/hls.m3u8"
    }, {
        "type": "super",
        "size": 1280,
        "url": "https://some.cdn.site/good.webm"
    }],
    "moreStuff": "more values",
    ...
}

Then extractor code like this can collect the various fields of the JSON:

...
from ..utils import (
    determine_ext,
    int_or_none,
    T,
    traverse_obj,
    txt_or_none,
    url_or_none,
)
...
        ...
        info_dict = {}
        # extract title and description if valid and not empty
        info_dict.update(traverse_obj(media_json, {
            'title': ('title', T(txt_or_none)),
            'description': ('comment', T(txt_or_none)),
        }))

        # extract any recognisable media formats
        fmts = []
        # traverse into "media" list, extract `dict`s with desired keys
        for fmt in traverse_obj(media_json, ('media', Ellipsis, {
                'format_id': ('type', T(txt_or_none)),
                'url': ('url', T(url_or_none)),
                'width': ('size', T(int_or_none)), })):
            # bad `fmt` values were `None` and removed
            if 'url' not in fmt:
                continue
            fmt_url = fmt['url']  # known to be valid URL
            ext = determine_ext(fmt_url)
            if ext == 'm3u8':
                fmts.extend(self._extract_m3u8_formats(fmt_url, video_id, 'mp4', fatal=False))
            else:
                fmt['ext'] = ext
                fmts.append(fmt)

        # sort, raise if no formats
        self._sort_formats(fmts)

        info_dict['formats'] = fmts
        ...

The extractor raises an exception rather than random crashes if the JSON structure changes so that no formats are found.

EMBEDDING YOUTUBE-DL

youtube-dl makes the best effort to be a good command-line program, and thus should be callable from any programming language. If you encounter any problems parsing its output, feel free to create a report.

From a Python program, you can embed youtube-dl in a more powerful fashion, like this:

from __future__ import unicode_literals
import youtube_dl

ydl_opts = {}
with youtube_dl.YoutubeDL(ydl_opts) as ydl:
    ydl.download(['https://www.youtube.com/watch?v=BaW_jenozKc'])

Most likely, you’ll want to use various options. For a list of options available, have a look at youtube_dl/YoutubeDL.py. For a start, if you want to intercept youtube-dl’s output, set a logger object.

Here’s a more complete example of a program that outputs only errors (and a short message after the download is finished), and downloads/converts the video to an mp3 file:

from __future__ import unicode_literals
import youtube_dl


class MyLogger(object):
    def debug(self, msg):
        pass

    def warning(self, msg):
        pass

    def error(self, msg):
        print(msg)


def my_hook(d):
    if d['status'] == 'finished':
        print('Done downloading, now converting ...')


ydl_opts = {
    'format': 'bestaudio/best',
    'postprocessors': [{
        'key': 'FFmpegExtractAudio',
        'preferredcodec': 'mp3',
        'preferredquality': '192',
    }],
    'logger': MyLogger(),
    'progress_hooks': [my_hook],
}
with youtube_dl.YoutubeDL(ydl_opts) as ydl:
    ydl.download(['https://www.youtube.com/watch?v=BaW_jenozKc'])

BUGS

Bugs and suggestions should be reported in the issue tracker: https://github.com/ytdl-org/youtube-dl/issues (https://yt-dl.org/bug is an alias for this). Unless you were prompted to or there is another pertinent reason (e.g. GitHub fails to accept the bug report), please do not send bug reports via personal email. For discussions, join us in the IRC channel #youtube-dl on freenode (webchat).

Opening a bug report or suggestion

Be sure to follow instructions provided below and in the issue tracker. Complete the appropriate issue template fully. Consider whether your problem is covered by an existing issue: if so, follow the discussion there. Avoid commenting on existing duplicate issues as such comments do not add to the discussion of the issue and are liable to be treated as spam.

Please include the full output of youtube-dl when run with -v, i.e. add -v flag to your command line, copy the whole output and post it in the issue body wrapped in ``` for better formatting. It should look similar to this:

$ youtube-dl -v <your command line>
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v', u'https://www.youtube.com/watch?v=BaW_jenozKcj']
[debug] Encodings: locale cp1251, fs mbcs, out cp866, pref cp1251
[debug] youtube-dl version 2015.12.06
[debug] Git HEAD: 135392e
[debug] Python version 2.6.6 - Windows-2003Server-5.2.3790-SP2
[debug] exe versions: ffmpeg N-75573-g1d0487f, ffprobe N-75573-g1d0487f, rtmpdump 2.4
[debug] Proxy map: {}
...

Do not post screenshots of verbose logs; only plain text is acceptable.

The output (including the first lines) contains important debugging information. Issues without the full output are often not reproducible and therefore do not get solved in short order, if ever.

Finally please review your issue to avoid various common mistakes (you can and should use this as a checklist) listed below.

Is the description of the issue itself sufficient?

We often get issue reports that are hard to understand. To avoid subsequent clarifications, and to assist participants who are not native English speakers, please elaborate on what feature you are requesting, or what bug you want to be fixed.

Make sure that it’s obvious

What the problem is
How it could be fixed
How your proposed solution would look

If your report is shorter than two lines, it is almost certainly missing some of these, which makes it hard for us to respond to it. We’re often too polite to close the issue outright, but the missing info makes misinterpretation likely. As a committer myself, I often get frustrated by these issues, since the only possible way for me to move forward on them is to ask for clarification over and over.

For bug reports, this means that your report should contain the complete output of youtube-dl when called with the -v flag. The error message you get for (most) bugs even says so, but you would not believe how many of our bug reports do not contain this information.

If your server has multiple IPs or you suspect censorship, adding --call-home may be a good idea to get more diagnostics. If the error is ERROR: Unable to extract ... and you cannot reproduce it from multiple countries, add --dump-pages (warning: this will yield a rather large output, redirect it to the file log.txt by adding >log.txt 2>&1 to your command-line) or upload the .dump files you get when you add --write-pages somewhere.

Site support requests must contain an example URL. An example URL is a URL you might want to download, like https://www.youtube.com/watch?v=BaW_jenozKc. There should be an obvious video present. Except under very special circumstances, the main page of a video service (e.g. https://www.youtube.com/) is not an example URL.

Is the issue already documented?

Make sure that someone has not already opened the issue you’re trying to open. Search at the top of the window or browse the GitHub Issues of this repository. Initially, at least, use the search term -label:duplicate to focus on active issues. If there is an issue, feel free to write something along the lines of “This affects me as well, with version 2015.01.01. Here is some more information on the issue: …”. While some issues may be old, a new post into them often spurs rapid activity.

Are you using the latest version?

Before reporting any issue, type youtube-dl -U. This should report that you’re up-to-date. About 20% of the reports we receive are already fixed, but people are using outdated versions. This goes for feature requests as well.

Why are existing options not enough?

Before requesting a new feature, please have a quick peek at the list of supported options. Many feature requests are for features that actually exist already! Please, absolutely do show off your work in the issue report and detail how the existing similar options do not solve your problem.

Is there enough context in your bug report?

People want to solve problems, and often think they do us a favor by breaking down their larger problems (e.g. wanting to skip already downloaded files) to a specific request (e.g. requesting us to look whether the file exists before downloading the info page). However, what often happens is that they break down the problem into two steps: One simple, and one impossible (or extremely complicated one).

We are then presented with a very complicated request when the original problem could be solved far easier, e.g. by recording the downloaded video IDs in a separate file. To avoid this, you must include the greater context where it is non-obvious. In particular, every feature request that does not consist of adding support for a new site should contain a use case scenario that explains in what situation the missing feature would be useful.

Does the issue involve one problem, and one problem only?

Some of our users seem to think there is a limit of issues they can or should open. There is no limit of issues they can or should open. While it may seem appealing to be able to dump all your issues into one ticket, that means that someone who solves one of your issues cannot mark the issue as closed. Typically, reporting a bunch of issues leads to the ticket lingering since nobody wants to attack that behemoth, until someone mercifully splits the issue into multiple ones.

In particular, every site support request issue should only pertain to services at one site (generally under a common domain, but always using the same backend technology). Do not request support for vimeo user videos, White house podcasts, and Google Plus pages in the same issue. Also, make sure that you don’t post bug reports alongside feature requests. As a rule of thumb, a feature request does not include outputs of youtube-dl that are not immediately related to the feature at hand. Do not post reports of a network error alongside the request for a new video service.

Is anyone going to need the feature?

Only post features that you (or an incapacitated friend you can personally talk to) require. Do not post features because they seem like a good idea. If they are really useful, they will be requested by someone who requires them.

Is your question about youtube-dl?

It may sound strange, but some bug reports we receive are completely unrelated to youtube-dl and relate to a different, or even the reporter’s own, application. Please make sure that you are actually using youtube-dl. If you are using a UI for youtube-dl, report the bug to the maintainer of the actual application providing the UI. On the other hand, if your UI for youtube-dl fails in some way you believe is related to youtube-dl, by all means, go ahead and report the bug.

COPYRIGHT

youtube-dl is released into the public domain by the copyright holders.

This README file was originally written by Daniel Bolton and is likewise released into the public domain.

LazyVim

Mon, 22 Sep 2025 15:30:38 +0800

LazyVim/LazyVim

Install · Configure · Docs

LazyVim is a Neovim setup powered by 💤 lazy.nvim to make it easy to customize and extend your config. Rather than having to choose between starting from scratch or using a pre-made distro, LazyVim offers the best of both worlds - the flexibility to tweak your config as needed, along with the convenience of a pre-configured setup.

✨ Features

🔥 Transform your Neovim into a full-fledged IDE
💤 Easily customize and extend your config with lazy.nvim
🚀 Blazingly fast
🧹 Sane default settings for options, autocmds, and keymaps
📦 Comes with a wealth of plugins pre-configured and ready to use

⚡️ Requirements

Neovim >= 0.11.2 (needs to be built with LuaJIT)
Git >= 2.19.0 (for partial clones support)
a Nerd Font (optional)
a C compiler for nvim-treesitter. See here

🚀 Getting Started

You can find a starter template for LazyVim here

Try it with Docker

docker run -w /root -it --rm alpine:edge sh -uelic '
  apk add git lazygit fzf curl neovim ripgrep alpine-sdk --update
  git clone https://github.com/LazyVim/starter ~/.config/nvim
  cd ~/.config/nvim
  nvim
'

Install the LazyVim Starter

Make a backup of your current Neovim files:

1
2

mv ~/.config/nvim ~/.config/nvim.bak
mv ~/.local/share/nvim ~/.local/share/nvim.bak

Clone the starter

`1`	`git clone https://github.com/LazyVim/starter ~/.config/nvim`

Remove the .git folder, so you can add it to your own repo later
1

rm -rf ~/.config/nvim/.git
Start Neovim!
1

nvim
Refer to the comments in the files on how to customize LazyVim.

There’s a great video created by @elijahmanor with a walkthrough to get started.

@dusty-phillips wrote a comprehensive book called LazyVim for Ambitious Developers available for free online.

📂 File Structure

The files under config will be automatically loaded at the appropriate time, so you don’t need to require those files manually. LazyVim comes with a set of default config files that will be loaded before your own. See here

You can add your custom plugin specs under lua/plugins/. All files there will be automatically loaded by lazy.nvim

~/.config/nvim
├── lua
│   ├── config
│   │   ├── autocmds.lua
│   │   ├── keymaps.lua
│   │   ├── lazy.lua
│   │   └── options.lua
│   └── plugins
│       ├── spec1.lua
│       ├── **
│       └── spec2.lua
└── init.lua

⚙️ Configuration

Refer to the docs

nem

Fri, 01 Aug 2025 15:38:22 +0800

NemProject/nem

NIS client

This project contains NEM Infrastructure Server and all its dependencies. It is the simplest way to quickly build and launch a NEM node.

Package Organization

The main folders are:

Folder	Content
`core`	The core dependency.
`deploy`	The deploy dependency.
`peer`	The peer dependency.
`nis`	The nis dependency.

Building the package

The package uses Apache Maven and minimum required Java SDK version to build is Java 11.

Please make sure that the Java version is 11+ by running the following command:

1
2

java -version
# should print sth similar to: openjdk version "11.0.2" 2019-01-15

Build the package as usual:

`1`	`mvn package`

Then check that unit tests are passing by running:

`1`	`mvn test`

Optionally, check if the slower integration tests are passing by running:

`1`	`mvn failsafe:integration-test`

Running the package

NIS nodes are configured through property files. Create a folder named staging and add any required property files inside.

Then run the node with:

`1`	`java -Xms6G -Xmx6G -cp ./staging:./nis/target/libs/:./nis/target/ org.nem.deploy.CommonStarter`

Read the NEM node documentation to know more about handling NIS nodes.

Running a testnet node

Create a config-user.properties with the following properties

# update <ReplaceWithYourName> value below
cat >> staging/config-user.properties << EOF
nis.bootName = <ReplaceWithYourName>

nem.network = testnet

nis.treasuryReissuanceForkHeight = 1
nis.treasuryReissuanceForkTransactionHashes =
nis.treasuryReissuanceForkFallbackTransactionHashes =
nis.multisigMOfNForkHeight = 1
nis.mosaicsForkHeight = 1
nis.firstFeeForkHeight = 1
nis.secondFeeForkHeight = 1
nis.remoteAccountForkHeight = 1
nis.mosaicRedefinitionForkHeight = 1
EOF

Contributing

Before contributing please read the CONTRIBUTING instructions.

Getting Help

License

dashy

Tue, 22 Jul 2025 15:33:52 +0800

Lissy93/dashy

Dashy

Dashy helps you organize your self-hosted services by making them accessible from a single place

User Showcase | Live Demo | Getting Started | Documentation | GitHub

^{Dashy is kindly sponsored by Umbrel - the personal home cloud and OS for self-hosting}

[!NOTE] Version 3.0.0 has been released, and requires some changes to your setup, see #1529 for details.

Table of Contents

Features 🌈

📃 Support for multiple pages
🚦 Real-time status monitoring for each of your apps/links
📊 Use widgets to display info and dynamic content from self-hosted services
🔎 Instant search by name, domain, or tags + customizable hotkeys & keyboard shortcuts
🎨 Many built-in color themes, with UI color editor and support for custom CSS
🧸 Many icon options - Font-Awesome, homelab icons, auto-fetching Favicon, images, emojis, etc.
💂 Optional authentication with multi-user access, configurable privileges, and SSO support
🌎 Multi-language support, with 10+ human-translated languages, and more on the way
☁ Optional, encrypted, free off-site cloud backup and restore feature available
💼 A workspace view, for easily switching between multiple apps simultaneously
🛩️ A minimal view, for use as a fast-loading browser Startpage
🖱️ Choose app launch methods: new tab, same tab, clipboard, pop-up modal, or open in workspace view
📏 Customizable layout, sizes, text, component visibility, sort order, behavior, etc.
🖼️ Options for a full-screen background image, custom nav-bar links, HTML footer, title, etc.
🚀 Easy to setup with Docker, or on bare metal, or with 1-Click cloud deployment
⚙️ Easy single-file YAML-based configuration, and option to configure app through the UI
✨ Under active development with improvements and new features added regularly
🤏 Small bundle size, fully responsive UI, and PWA for basic offline access
🆓 100% free and open-source
🔐 Strong focus on privacy
🌈 And loads more…

⬆️ Back to Top

Demo ⚡

Live Instances: Demo 1 (Live Demo) ┆ Demo 2 (Dashy Links) ┆ Demo 3 (Dev Preview)

Screenshots: Checkout the Showcase, to see example dashboards from the community

Spin up your own demo: [

⬆️ Back to Top

Getting Started 🚀

For full setup instructions, see: Deployment

Deploying from Docker Hub 🐳

You will need Docker installed on your system

`1`	`docker run -p 8080:8080 lissy93/dashy`

docker run -d \
  -p 4000:8080 \
  -v /root/my-local-conf.yml:/app/user-data/conf.yml \
  --name my-dashboard \
  --restart=always \
  lissy93/dashy:latest

See also: examples with Docker Compose. Dashy is also available via GHCR, and tags for other architectures (arm32v7, arm64v8, etc.) and set versions are supported

Once you’ve got Dashy running, see App Management Docs for info on using health checks, updating, backups, web-server configs, logs, performance, security, and more.

Deploying from Source 🔨

You will need git, the latest or LTS version of Node.js and (optionally) Yarn installed on your system.

Clone the Repo: git clone https://github.com/Lissy93/dashy.git and cd dashy
Configuration: Fill in your settings in ./user-data/conf.yml
Install dependencies: yarn
Build: yarn build
Run: yarn start

See docs: Full list of Dashy’s commands

Deploy to the Cloud ☁️

Dashy supports 1-Click deployments on several popular cloud platforms. To spin up a new instance, just click a link below:

For more 1-click cloud deployments, see Cloud Deployment

⬆️ Back to Top

Configuring 🔧

For full configuration documentation, see: Configuring

Dashy is configured through a YAML file, located at ./user-data/conf.yml. In addition, you can find a complete list of available options in the Configuring Docs. The config can also be edited and saved directly through the UI.

⬆️ Back to Top

Theming 🎨

For full theming documentation, see: Theming

Dashy comes pre-bundled with several built-in themes, which you can preview, apply and edit through the UI. With the theme configurator and support for custom CSS, everything is in place to quickly develop your own unique-looking dashboard.

⬆️ Back to Top

Icons 🧸

For full iconography documentation, see: Icons

Both sections and items can have an icon associated with them, defined under the icon attribute. With several different icon packs supported, you’ll be able to find the perfect thumbnail for any app or service.

The following icon types are supported:

Favicon - Automatically fetch an apps icon from its Favicon or logo image
Icon Packs - Use any icon from font-awesome, simple-icons, selfh.st/icons, or material icons
Emoji - Any valid emoji can be used as an icon
Generative - Unique, auto-generated images for easily identifying services
URL - Pass the URL of any valid image in to have it fetched and rendered
Local - Store custom images locally and reference by filename
Homelab Icons - Using dashboard-icons for logos of commonly self-hosted services

⬆️ Back to Top

Status Indicators 🚦

For full monitoring documentation, see: Status Indicators

Dashy has an optional feature to check if each app/ service is up and responding, then display a small status indicator icon. Hovering over it will show additional stats like response time and status code.

Status indicators can be globally enabled by setting appConfig.statusCheck: true or enabled/ disabled on a per-item basis. Status is checked on page load, but you can allow continuous polling by specifying a time interval between checks, in seconds under appConfig.statusCheckInterval. You can also use a different endpoint for status checking, with statusCheckUrl, and if needed, pass in custom headers under statusCheckHeaders.

⬆️ Back to Top

Widgets 📊

For full widget documentation, see: Widgets

You can display dynamic content from services in the form of widgets. There are several pre-built widgets available for showing useful info, and integrations with commonly self-hosted services, but you can also easily create your own for almost any app.

⬆️ Back to Top

Authentication 🔐

For full authentication documentation, see: Authentication

Dashy has full support for secure single-sign-on using Keycloak for secure, easy authentication, see setup docs for a full usage guide.

There is also a basic auth feature, which doesn’t require additional setup. To enable this, add an auth attribute under appConfig, containing an array of users, each with a username, SHA-256 hashed password and optional user type. Basic auth also supports several access control features, including read-only guest access and granular controls.

appConfig:
  auth:
    users:
    - user: alicia
      hash: 4D1E58C90B3B94BCAD9848ECCACD6D2A8C9FBC5CA913304BBA5CDEAB36FEEFA3
      type: admin

Other access control systems are also supported, see the Alternative Auth Methods docs.

⬆️ Back to Top

Alternate Views 👓

As well as the default homepage, there is also:

A minimal view, valid for use as a browser start page
A workspace view, useful for visiting many apps simultaneously

You can change the view from the UI, using the switch icon in the top-right corner, or select a default view in the config under appConfig.startingView attribute.

Example of Workspace View

Example of Minimal View

⬆️ Back to Top

Opening Methods 🖱️

For full documentation on views and opening methods, see: Alternate Views

There are several different ways you can launch apps. You can specify the default opening method for any given item under the target attribute or set a site-wide default under appConfig.defaultOpeningMethod. Right-click on an item to item for all options. The following options are supported:

sametab - The app will be launched in the current tab
newtab - The app will be launched in a new tab (or use Ctrl + Click)
modal - Launch app in a resizable/ movable popup modal on the current page (or use Alt + Click)
workspace - Changes to Workspace view and launches app
clipboard - Copy the app’s URL to your system clipboard
top - Opens in the top-most browsing context, useful if you’re accessing Dashy through an iframe

⬆️ Back to Top

Searching and Shortcuts 🔎

For full documentation on searching, see: Searching & Shortcuts

Quickly finding and launching applications is the primary aim of Dashy. To that end, instant search and customizable keyboard shortcuts are built-in.

To start filtering, start typing—no need to select the search bar or use any special key. Then use either the tab key or arrow keys to select and move between results, and hit enter to launch the currently selected application.

For apps that you use regularly, you can set a custom keybinding. Use the hotkey parameter on a certain item to specify a numeric key between 0 - 9. You can then launch that app by just pressing that key.

You can also add custom tags to a given item to make finding them based on keywords easier. For example, in the following example, searching for ‘Movies’ will show ‘Plex’

  items:
  - title: Plex
    hotkey: 8
    icon: favicon
    description: Media library
    url: https://plex.lab.local
    tags: [ movies, videos, music ]

To search the web directly through Dashy, just press enter after typing your query. Options for web search are set under appConfig.webSearch. There is built-in support for 10+ search engines, or use your own custom provider or self-hosted instance. With the web search, you can also define your bangs to redirect results to any given app, website, or search engine, when the query is preceded with a certain character sequence (usually beginning in /, ! or :).

webSearch:
  searchEngine: duckduckgo
  openingMethod: newtab
  searchBangs:
    /r: reddit
    /w: wikipedia
    /s: https://whoogle.local/search?q=
    ':wolf': wolframalpha
    ':so': stackoverflow
    ':git': github

Hit Esc at any time to close any open apps, clear the search field, or hide any modals.

⬆️ Back to Top

Config Editor ⚙️

For full config documentation, see: Configuring

As well as passing in a YAML config file, you can also configure the app directly through the UI and preview changes live.

To edit any section or item, right-click on it, and select “Edit”, or enter the Edit Mode (using the Pen icon in the top-right), then click any part of the page to edit. Changes will be visible immediately but will not be saved until clicking “Save to Disk” or “Save Locally”.

Under the config menu, you can export, view, backup, or reset app config and edit the raw config file in a text editor with built-in schema validation. It’s recommended to keep a backup of your config.

⬆️ Back to Top

Cloud Backup & Sync ☁

For full backup documentation, see: Cloud Backup & Sync

Dashy has an optional built-in feature for securely backing up your config to a hosted cloud service and then restoring it on another instance. This is useful not only for backing up your configuration off-site but also enables Dashy to be used without having to write a YAML config file.

All data is fully E2E encrypted before being sent to the backend (done in CloudBackup.js using crypto.js ’s AES method). The data is then sent to a Cloudflare worker and stored in a KV data store.

⬆️ Back to Top

Language Switching 🌎

For full internationalization documentation, see: Multi-Language Support

Dashy supports multiple languages and locales. When available, your language should be automatically detected and applied on load. But you can also select a language through the UI (under config –> Switch Language) or set appConfig.language to your language (specified as a 2-digit ISO 639-1 code), as seen below, e.g. language: de.

Supported Languages

🇬🇧 English: en - Default
🇦🇪 Arabic: ar - Auto-generated
🇧🇩 Bengali: bn - Contributed by @soaibsafi
🇧🇬 Bulgarian: bg - Contributed by @asenov
🇨🇳 Chinese: cn - Contributed by @FormatToday
🇨🇿 Czech: cs - Contributed by @Tuzi555
🇩🇰 Danish: da - Contributed by @lordpansar
🇳🇱 Dutch: nl - Contributed by @evroon
🇫🇷 French: fr - Contributed by @EVOTk
🇩🇪 German: de - Contributed by @Niklashere
🇬🇷 Greek: el - Contributed by @aviolaris
🇮🇳 Hindi: hi - Auto-generated
🇮🇹 Italian: it - Contributed by @alexdelprete
🇯🇵 Japanese: ja - Auto-generated
🇰🇷 Korean: ko - Contributed by @boggy-cs
🇳🇴 Norwegian Bokmål: nb - Contributed by @rubjo
🇵🇱 Polish: pl - Contributed by @skaarj1989
🇵🇹 Portuguese: pt - Contributed by @LeoColman
🛰️ Galician: gl - Contributed by @pvillaverde
🇷🇺 Russian: ru -Contributed by @sasetz
🇸🇰 Slovak: sk - Contributed by @Smexhy
🇸🇮 Slovenian: sl - Contributed by @UrekD
🇪🇸 Spanish: es - Contributed by @lu4t
🇸🇪 Swedish: sv - Contributed by @BOZG
🇹🇼 Traditional Chinese: zh-TW - Contributed by @stanly0726
🇹🇷 Turkish: tr - Contributed by @imsakg
🇺🇦 Ukrainian: uk - Contributed by @allozavrr
🏴‍☠️ Pirate: pirate - Contributed by @Lissy93

Add your Language

I would love Dashy to be available to everyone without language being a barrier to entry. If you’ve got a few minutes to spare, consider adding translations for your language. It’s a quick task, and all text is in a single JSON file. Since any missing text will fall back to English, you don’t need to translate it all.

⬆️ Back to Top

Multi-Page Support 📃

For full multi-page documentation, see: Pages & Sections

Within your dashboard, you can have as many sub-pages as you require. To load additional pages, specify a name, and path to a config file under pages. The config file can be either local (stored in /public), or remote (located anywhere accessible).

pages:
- name: Networking Services
  path: 'networking.yml'
- name: Work Stuff
  path: 'work.yml'

pages:
- name: Getting Started
  path: 'https://snippet.host/tvcw/raw'
- name: Homelab
  path: 'https://snippet.host/tetp/raw'
- name: Browser Startpage
  path: 'https://snippet.host/zcom/raw'

System Requirements 📊

If running on bare metal, Dashy requires Node V 16.0.0 or later, LTS (16.13.2) is recommended.

If running in Docker container, the recommended base image is Alpine (3.15)

The hardware requirements vary depending on where and how you are running Dashy. Generally speaking, on a bare-metal system or Docker container, 1GB of memory should be more than enough, and depending on whether you are using your own assets, then 1GB of disk space should be sufficient.

If you are using one of the 1-click cloud deployment methods, serving the app through a CDN or using a static hosting provider, then there are no specific requirements, as the built app is just a series of static JS files, and so is very light-weight.

Dashy also wells run on low-powered ARM-based single board computers, such as a Raspberry Pi (tested on Pi 3)

Browser Support


Latest ✔	Latest ✔	10+ ✔	Latest ✔	6.1+ ❌

⬆️ Back to Top

Support 🙋‍♀️

If you’re having trouble getting Dashy up and running, or have a question about usage or configuration, feel free to ask. The best place to do this is via the Discussions.

If you’ve found something which isn’t working as it should, please raise a bug by opening a ticket.

It’s best to check the docs, previous issues and troubleshooting guide first.

⬆️ Back to Top

Supporting Dashy 💖

For full details and other ways you can help out, see: Contributing

If you’re using Dashy and would like to help support its development, then that would be awesome! Contributions of any type, any size, are always very much appreciated, and we will appropriately credit you for your effort.

Several areas that we need a bit of help with at the moment are:

Translating - Help make Dashy available to non-native English speakers by adding your language
Donate a small amount by Sponsoring @Lissy93 on GitHub and receive some extra perks!
Complete a short survey to have your say about future features
Share your dashboard in the Showcase, to inspire others
Spread the word by sharing Dashy or a screenshot of your dashboard to help new users discover it
Submit a PR to add a new feature, fix a bug, update the docs, add a theme, widget or something else
Star Dashy on GitHub/ DockerHub or leave an upvote / review on these platforms

⬆️ Back to Top

Credits 🏆

For a complete list of credits, and attributions to packages used within Dashy, see: Credits

Thank you so much to everyone who has helped with Dashy so far; every contribution is very much appreciated.

Contributors

[

Stats

⬆️ Back to Top

Developing 🧱

For full development documentation, see: Developing

Before getting started, you’ll need Git, Node and optionally Yarn (run npm i -g yarn) installed.

To set up the development environment:

Get Code: git clone https://github.com/Lissy93/dashy.git and cd dashy
Install dependencies: yarn
Start dev server: yarn dev
Open the browser: http://localhost:8080

When you’re ready, you can build the production app with yarn build, and then run it with yarn start

If you’re new to web development, I’ve put together a short list of resources to help beginners get started

Repo Status:

⬆️ Back to Top

Documentation 📘

For full docs, see: Documentation Contents

Running Dashy

💨 Quick Start - TDLR guide on getting Dashy up and running in under 5 minutes
🚀 Deployment - Full guide on setting up Dashy on various different environments
🔧 Configuring - Complete list of all available options in the config file
💻 Management - Managing your app, updating, security, web server configuration, etc
🚒 Troubleshooting - Common errors and problems, and how to fix them

Feature Docs

🛡️ Authentication - Guide to setting up authentication to protect your dashboard
🌈 Alternate Views - Outline of available pages / views and item opening methods
💾 Backup & Restore - Guide to backing up config with Dashy’s cloud sync feature
🧸 Icons - Outline of all available icon types for sections and items, with examples
🌐 Multi-Language Support - Switching languages, and adding a new locales
🚦 Status Indicators - Using Dashy to monitor uptime and status of your apps
🔍 Searching & Shortcuts - Searching, launching methods + keyboard shortcuts
🎨 Theming - Complete guide to applying, writing and modifying themes + styles
📊 Widgets - List of all dynamic content widgets, with usage guides and examples

Development and Contributing

🧱 Developing - Running Dashy development server locally, and general workflow
🛎️ Development Guides - Common development tasks, to help new contributors
💖 Contributing - How to contribute to Dashy
🌟 Showcase - See how others are using Dashy, and share your dashboard
🏆 Credits - Shout out to the amazing people who have contributed so far
🗞️ Release Workflow - Info about releases, CI and automated tasks

Misc

🔐 Privacy & Security - List of requests, potential issues, and security resources
📄 License - Copy of the MIT License
⚖️ Legal - Licenses of direct dependencies
📏 Code of Conduct - Contributor Covenant Code of Conduct
🌳 Changelog - Details of recent changes, and historical versions

⬆️ Back to Top

Roadmap 🛣️

For upcoming features that will be released in the near future, see the Current Roadmap

For past updates, see the Changelog

⬆️ Back to Top

Alternatives 🙌

A few self-hosted web apps serve a similar purpose to Dashy. If you’re looking for a dashboard, and Dashy doesn’t meet your needs, I highly recommend you check these projects out!

Flame by @pawelmalak (MIT)
HomeDash2
Homer (Apache License 2.0)
Organizr (GPL-3.0 License)
Heimdall (MIT)
Smashing (MIT)
See more 👉 Awesome Self-Hosted

⬆️ Back to Top

License 📜

Dashy is Licensed under MIT X11

Copyright © 2021-2024 Alicia Sykes <https://aliciasykes.com>

Permission is hereby granted, free of charge, to any person obtaining a copy of this
software and associated documentation files (the "Software"), to deal in the Software
without restriction, including without limitation the rights to use, copy, modify, merge,
publish, distribute, sublicense, and/or sell copies of the Software, and to permit
persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or
substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES, OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF, OR IN CONNECTION WITH THE SOFTWARE OR THE USE
OR OTHER DEALINGS IN THE SOFTWARE.

Except as contained in this notice, Dashy shall not be used in advertising or otherwise
to promote the sale, use, or other dealings in this Software without prior written
authorization from the repo owner.

TDLR; You can do whatever you like with Dashy: use it in private or commercial settings, redistribute and modify it. But you must display this license and credit the author. There is no warranty that this app will work as expected, and the author cannot be held liable for anything that goes wrong. For more info, see TLDR Legal’s Explanation of MIT

⬆️ Back to Top

© Alicia Sykes 2024
Licensed under MIT

^{Thanks for visiting :)}

open_deep_research

Tue, 22 Jul 2025 15:33:16 +0800

langchain-ai/open_deep_research

Open Deep Research

Deep research has broken out as one of the most popular agent applications. This is a simple, configurable, fully open source deep research agent that works across many model providers, search tools, and MCP servers.

Read more in our blog
See our video for a quick overview

🚀 Quickstart

Clone the repository and activate a virtual environment:

git clone https://github.com/langchain-ai/open_deep_research.git
cd open_deep_research
uv venv
source .venv/bin/activate  # On Windows: .venv\Scripts\activate

Install dependencies:

`1`	`uv pip install -r pyproject.toml`

Set up your .env file to customize the environment variables (for model selection, search tools, and other configuration settings):

`1`	`cp .env.example .env`

Launch the assistant with the LangGraph server locally to open LangGraph Studio in your browser:

1
2

# Install dependencies and start the LangGraph server
uvx --refresh --from "langgraph-cli[inmem]" --with-editable . --python 3.11 langgraph dev --allow-blocking

Use this to open the Studio UI:

1
2
3

- 🚀 API: http://127.0.0.1:2024
- 🎨 Studio UI: https://smith.langchain.com/studio/?baseUrl=http://127.0.0.1:2024
- 📚 API Docs: http://127.0.0.1:2024/docs

Ask a question in the messages input field and click Submit.

Configurations

Open Deep Research offers extensive configuration options to customize the research process and model behavior. All configurations can be set via the web UI, environment variables, or by modifying the configuration directly.

General Settings

Max Structured Output Retries (default: 3): Maximum number of retries for structured output calls from models when parsing fails
Allow Clarification (default: true): Whether to allow the researcher to ask clarifying questions before starting research
Max Concurrent Research Units (default: 5): Maximum number of research units to run concurrently using sub-agents. Higher values enable faster research but may hit rate limits

Research Configuration

Search API (default: Tavily): Choose from Tavily (works with all models), OpenAI Native Web Search, Anthropic Native Web Search, or None
Max Researcher Iterations (default: 3): Number of times the Research Supervisor will reflect on research and ask follow-up questions
Max React Tool Calls (default: 5): Maximum number of tool calling iterations in a single researcher step

Models

Open Deep Research uses multiple specialized models for different research tasks:

Summarization Model (default: openai:gpt-4.1-nano): Summarizes research results from search APIs
Research Model (default: openai:gpt-4.1): Conducts research and analysis
Compression Model (default: openai:gpt-4.1-mini): Compresses research findings from sub-agents
Final Report Model (default: openai:gpt-4.1): Writes the final comprehensive report

All models are configured using init_chat_model() API which supports providers like OpenAI, Anthropic, Google Vertex AI, and others.

Important Model Requirements:

Structured Outputs: All models must support structured outputs. Check support here.
Search API Compatibility: Research and Compression models must support your selected search API:
- Anthropic search requires Anthropic models with web search capability
- OpenAI search requires OpenAI models with web search capability
- Tavily works with all models
Tool Calling: All models must support tool calling functionality
Special Configurations:
- For OpenRouter: Follow this guide
- For local models via Ollama: See setup instructions

Example MCP (Model Context Protocol) Servers

Open Deep Research supports MCP servers to extend research capabilities.

Local MCP Servers

Filesystem MCP Server provides secure file system operations with robust access control:

Read, write, and manage files and directories
Perform operations like reading file contents, creating directories, moving files, and searching
Restrict operations to predefined directories for security
Support for both command-line configuration and dynamic MCP roots

Example usage:

`1`	`mcp-server-filesystem /path/to/allowed/dir1 /path/to/allowed/dir2`

Remote MCP Servers

Remote MCP servers enable distributed agent coordination and support streamable HTTP requests. Unlike local servers, they can be multi-tenant and require more complex authentication.

Arcade MCP Server Example:

{
  "url": "https://api.arcade.dev/v1/mcps/ms_0ujssxh0cECutqzMgbtXSGnjorm",
  "tools": ["Search_SearchHotels", "Search_SearchOneWayFlights", "Search_SearchRoundtripFlights"]
}

Remote servers can be configured as authenticated or unauthenticated and support JWT-based authentication through OAuth endpoints.

Evaluation

A comprehensive batch evaluation system designed for detailed analysis and comparative studies.

Features:

Multi-dimensional Scoring: Specialized evaluators with 0-1 scale ratings
Dataset-driven Evaluation: Batch processing across multiple test cases

Usage:

1
2

# Run comprehensive evaluation on LangSmith datasets
python tests/run_evaluate.py

Key Files:

tests/run_evaluate.py: Main evaluation script
tests/evaluators.py: Specialized evaluator functions
tests/prompts.py: Evaluation prompts for each dimension

Deployments and Usages

LangGraph Studio

Follow the quickstart to start LangGraph server locally and test the agent out on LangGraph Studio.

Hosted deployment

You can easily deploy to LangGraph Platform.

Open Agent Platform

Open Agent Platform (OAP) is a UI from which non-technical users can build and configure their own agents. OAP is great for allowing users to configure the Deep Researcher with different MCP tools and search APIs that are best suited to their needs and the problems that they want to solve.

We’ve deployed Open Deep Research to our public demo instance of OAP. All you need to do is add your API Keys, and you can test out the Deep Researcher for yourself! Try it out here

You can also deploy your own instance of OAP, and make your own custom agents (like Deep Researcher) available on it to your users.

Updates 🔥

Legacy Implementations 🏛️

The src/legacy/ folder contains two earlier implementations that provide alternative approaches to automated research:

1. Workflow Implementation (`legacy/graph.py`)

Plan-and-Execute: Structured workflow with human-in-the-loop planning
Sequential Processing: Creates sections one by one with reflection
Interactive Control: Allows feedback and approval of report plans
Quality Focused: Emphasizes accuracy through iterative refinement

2. Multi-Agent Implementation (`legacy/multi_agent.py`)

Supervisor-Researcher Architecture: Coordinated multi-agent system
Parallel Processing: Multiple researchers work simultaneously
Speed Optimized: Faster report generation through concurrency
MCP Support: Extensive Model Context Protocol integration

See src/legacy/legacy.md for detailed documentation, configuration options, and usage examples for both legacy implementations.

filebrowser

Tue, 17 Jun 2025 15:30:09 +0800

gtsteffaniak/filebrowser

FileBrowser Quantum

The best free self-hosted web-based file manager.

[!WARNING] There is no stable version – :construction: planned for 2025. (Read more)

Poll: how much RAM does your install use?

About

FileBrowser Quantum provides an easy way to access and manage your files from the web. It has has a web page interface that allows you to create secure shared links, users with their own specific permissions and settings, and offers a great viewing experience for many file types.

This version is called “Quantum” because it packs tons of advanced features into a tiny easy to run file. Unlike the majority of alternative options, FileBrowser Quantum is simple to install and easy to configure.

The goal for this repo is to become the best open-source self-hosted file browsing application that exists – all for free. This repo will always be free and open-source.

Ready to try it out? See Getting Started Wiki.

How its different

FileBrowser Quantum is a massive fork of the file browser open-source project with the following changes:

✅ Multiple sources support
✅ Login support for OIDC, password + 2FA, and proxy.
✅ Revamped UI
✅ Simplified configuration via config.yaml config file.
✅ Ultra-efficient indexing and real-time updates
- Real-time search results as you type.
- Real-time monitoring and updates in the UI.
- Search supports file and folder sizes, along with various filters.
✅ Better listing browsing
- More file type previews, such as office and video file previews
- Instantly switches view modes and sort order without reloading data.
- Folder sizes are displayed.
- Navigating remembers the last scroll position.
✅ Developer API support
- Ability to create long-lived API Tokens.
- A helpful Swagger page is available at /swagger endpoint for API enabled users.

Notable features that this fork does not have (removed):

:construction: jobs are not supported yet.
:construction: rules are not supported yet.
❌ shell commands are completely removed and will not be returned.

[!WARNING] Every file and directory in the source gets indexed (by default). This enables powerful features such as instant search, but large source filesystems can increase your system requirements. See indexing wiki for more info.

FileBrowser Quantum differs significantly from the original version. Many of these changes required a significant overhaul. Creating a fork was a necessary process to make the program better. There have been many growing pains, but a stable release is planned and coming soon.

The UI

The UI has a simple three-component navigation system:

(Left) Multi-action button with slide-out panel.
(Middle) The powerful search bar.
(Right) The view change toggle.

All other functions are moved either into the action menu or pop-up menus. If the action does not depend on context, it will exist in the slide-out action panel. If the action is available based on context, it will show up as a pop-up menu.

Install and Configuration

Check out the Getting Started Wiki

For help configuring your filebrowser see Configuration Wiki

Command Line Usage

See the CLI Wiki

API Usage

See the API Wiki

Office File Support

See Office Support Wiki on how to enable office file editing and office-related features.

Migration from the original filebrowser

See the Migration Wiki

Comparison Chart

Application Name	Quantum	Filebrowser	Filestash	Nextcloud	Google_Drive	FileRun
Filesystem support	✅	✅	✅	❌	❌	✅
Linux	✅	✅	✅	✅	❌	✅
Windows	✅	✅	✅	❌	❌	✅
Mac	✅	✅	✅	❌	❌	✅
Self hostable	✅	✅	✅	✅	❌	✅
Has Stable Release?	:construction:	✅	✅	✅	✅	✅
S3 support	❌	❌	✅	✅	❌	❌
webdav support	❌	❌	✅	✅	❌	✅
FTP support	❌	❌	✅	✅	❌	✅
Dedicated docs site?	:construction:	✅	✅	✅	❌	✅
Multiple sources at once	✅	❌	✅	✅	❌	✅
Docker image size	200 MB (with ffmpeg)	31 MB	240 MB (main image)	250 MB	❌	> 2 GB
Min. Memory Requirements	256 MB	128 MB	128 MB (main image)	512 MB	❌	512 MB
has standalone binary	✅	✅	❌	❌	❌	❌
price	free	free	free	free tier	free tier	$99+
rich media preview	✅	✅	✅	✅	✅	✅
Upload files from the web?	✅	✅	✅	✅	✅	✅
Advanced Search?	✅	❌	❌	configurable	✅	✅
Indexed Search?	✅	❌	❌	configurable	✅	✅
Content-aware search?	❌	❌	❌	configurable	✅	✅
Custom job support	:construction:	✅	❌	✅	❌	✅
Multiple users	✅	✅	✅	✅	✅	✅
Single sign-on support	✅	❌	❌	✅	✅	✅
LDAP sign-on support	:construction:	❌	❌	✅	❌	✅
Long-live API key support	✅	❌	✅	✅	✅	✅
API documentation page	✅	❌	✅	✅	❌	✅
Mobile App	❌	❌	❌	✅	✅	❌
open source?	✅	✅	✅	✅	❌	❌
tags support	:construction:	❌	❌	✅	❌	✅
shareable web links?	✅	✅	✅	✅	✅	✅
Event-based notifications	:construction:	❌	❌	❌	❌	✅
Metrics	:construction:	❌	❌	❌	❌	❌
file space quotas	:construction:	❌	❌	❌	✅	✅
text-based files editor	✅	✅	✅	✅	✅	✅
Office file support	✅	❌	✅	✅	✅	✅
Office file previews	✅	❌	❌	✅	✅	✅
Themes	✅	✅	❌	❌	❌	✅
Branding support	✅	✅	❌	❌	❌	✅
activity log	:construction:	❌	❌	✅	✅	✅
Comments support	❌	❌	❌	✅	✅	✅
trash support	:construction:	❌	❌	✅	✅	✅
Starred/pinned files	❌	❌	❌	❌	✅	✅
Chromecast support	❌	❌	✅	❌	❌	❌
Share collections of files	:construction:	❌	❌	❌	❌	✅
Can archive selected files	:construction:	❌	❌	❌	❌	✅
Can browse archive files	:construction:	❌	❌	❌	❌	✅
Can convert documents	:construction:	❌	❌	❌	❌	✅
Can convert videos	:construction:	❌	❌	❌	❌	❌
Can convert photos	:construction:	❌	❌	❌	❌	❌

nvim-treesitter

Tue, 27 May 2025 15:30:52 +0800

nvim-treesitter/nvim-treesitter

nvim-treesitter

Treesitter configurations and abstraction layer for Neovim.

Logo by @steelsojka

[!CAUTION] The master branch is frozen and provided for backward compatibility only. All future updates happen on the main branch, which will become the default branch in the future.

The goal of nvim-treesitter is both to provide a simple and easy way to use the interface for tree-sitter in Neovim and to provide some basic functionality such as highlighting based on it:

Traditional highlighting (left) vs Treesitter-based highlighting (right). More examples can be found in our gallery.

Warning: Treesitter and nvim-treesitter highlighting are an experimental feature of Neovim. Please consider the experience with this plug-in as experimental until Tree-Sitter support in Neovim is stable! We recommend using the nightly builds of Neovim if possible. You can find the current roadmap here. The roadmap and all features of this plugin are open to change, and any suggestion will be highly appreciated!

Nvim-treesitter is based on three interlocking features: language parsers, queries, and modules, where modules provide features – e.g., highlighting – based on queries for syntax objects extracted from a given buffer by language parsers. Users will generally only need to interact with parsers and modules as explained in the next section. For more detailed information on setting these up, see “Advanced setup”.

Quickstart

Requirements

Neovim 0.10 or later (supported up to Neovim 0.12);
tar and curl in your path (or alternatively git);
a C compiler in your path and libstdc++ installed (Windows users please read this!).

Installation

You can install nvim-treesitter with your favorite package manager (or using the native package feature of vim, see :h packages).

NOTE: This plugin is only guaranteed to work with specific versions of language parsers (as specified in the lockfile.json). When upgrading the plugin, you must make sure that all installed parsers are updated to the latest version via :TSUpdate. It is strongly recommended to automate this; e.g., if you are using lazy.nvim, put this in your init.lua file:

1
2
3

require("lazy").setup({
  {"nvim-treesitter/nvim-treesitter", branch = 'master', lazy = false, build = ":TSUpdate"}
})

[!CAUTION]

This plugin does not support lazy-loading.

Make sure to specify the master branch, as the default branch will switch to main in the future.

For other plugin managers such as packer.nvim, see this Installation page from the wiki (Note that this page is community maintained).

Language parsers

Treesitter uses a different parser for every language, which needs to be generated via tree-sitter-cli from a grammar.js file, then compiled to a .so library that needs to be placed in neovim’s runtimepath (typically under parser/{language}.so). To simplify this, nvim-treesitter provides commands to automate this process. If the language is already supported by nvim-treesitter, you can install it with

`1`	`:TSInstall <language_to_install>`

This command supports tab expansion. You can also get a list of all available languages and their installation status with :TSInstallInfo. Parsers not on this list can be added manually by following the steps described under “Adding parsers” below.

To make sure a parser is at the latest compatible version (as specified in nvim-treesitter’s lockfile.json), use :TSUpdate {language}. To update all parsers unconditionally, use :TSUpdate all or just :TSUpdate.

Modules

Each module provides a distinct tree-sitter-based feature such as highlighting, indentation, or folding; see :h nvim-treesitter-modules or “Available modules” below for a list of modules and their options.

Following examples assume that you are configuring neovim with lua. If you are using vimscript, see :h lua-heredoc. All modules are disabled by default and need to be activated explicitly in your init.lua, e.g., via

require'nvim-treesitter.configs'.setup {
  -- A list of parser names, or "all" (the listed parsers MUST always be installed)
  ensure_installed = { "c", "lua", "vim", "vimdoc", "query", "markdown", "markdown_inline" },

  -- Install parsers synchronously (only applied to `ensure_installed`)
  sync_install = false,

  -- Automatically install missing parsers when entering buffer
  -- Recommendation: set to false if you don't have `tree-sitter` CLI installed locally
  auto_install = true,

  -- List of parsers to ignore installing (or "all")
  ignore_install = { "javascript" },

  ---- If you need to change the installation directory of the parsers (see -> Advanced Setup)
  -- parser_install_dir = "/some/path/to/store/parsers", -- Remember to run vim.opt.runtimepath:append("/some/path/to/store/parsers")!

  highlight = {
    enable = true,

    -- NOTE: these are the names of the parsers and not the filetype. (for example if you want to
    -- disable highlighting for the `tex` filetype, you need to include `latex` in this list as this is
    -- the name of the parser)
    -- list of language that will be disabled
    disable = { "c", "rust" },
    -- Or use a function for more flexibility, e.g. to disable slow treesitter highlight for large files
    disable = function(lang, buf)
        local max_filesize = 100 * 1024 -- 100 KB
        local ok, stats = pcall(vim.loop.fs_stat, vim.api.nvim_buf_get_name(buf))
        if ok and stats and stats.size > max_filesize then
            return true
        end
    end,

    -- Setting this to true will run `:h syntax` and tree-sitter at the same time.
    -- Set this to `true` if you depend on 'syntax' being enabled (like for indentation).
    -- Using this option may slow down your editor, and you may see some duplicate highlights.
    -- Instead of true it can also be a list of languages
    additional_vim_regex_highlighting = false,
  },
}

Each module can also be enabled or disabled interactively through the following commands:

:TSBufEnable {module} " enable module on current buffer
:TSBufDisable {module} " disable module on current buffer
:TSEnable {module} [{ft}] " enable module on every buffer. If filetype is specified, enable only for this filetype.
:TSDisable {module} [{ft}] " disable module on every buffer. If filetype is specified, disable only for this filetype.
:TSModuleInfo [{module}] " list information about modules state for each filetype

Check :h nvim-treesitter-commands for a list of all available commands. It may be necessary to reload the buffer (e.g., via :e) after enabling a module interactively.

Supported languages

For nvim-treesitter to support a specific feature for a specific language requires both a parser for that language and an appropriate language-specific query file for that feature.

The following is a list of languages for which a parser can be installed through :TSInstall; a checked box means that nvim-treesitter also contains queries at least for the highlight module.

Experimental parsers are parsers that have a maintainer but are not stable enough for daily use yet.

We are looking for maintainers to add more parsers and to write query files for their languages. Check our tracking issue for open language requests.

ada (maintained by @briot)
agda (maintained by @Decodetalkers)
angular (experimental, maintained by @dlvandenberg)
apex (maintained by @aheber, @xixiaofinland)
arduino (maintained by @ObserverOfTime)
asm (maintained by @RubixDev)
astro (maintained by @virchau13)
authzed (maintained by @mattpolzin)
awk
bash (maintained by @TravonteD)
bass (maintained by @amaanq)
beancount (maintained by @polarmutex)
bibtex (maintained by @theHamsta, @clason)
bicep (maintained by @amaanq)
bitbake (maintained by @amaanq)
blade (maintained by @calebdw)
blueprint (experimental, maintained by @gabmus)
bp (maintained by @ambroisie)
brightscript (maintained by @ajdelcimmuto)
c (maintained by @amaanq)
c_sharp (maintained by @amaanq)
caddy (maintained by @opa-oz)
cairo (maintained by @amaanq)
capnp (maintained by @amaanq)
chatito (maintained by @ObserverOfTime)
circom (maintained by @alexandr-martirosyan)
clojure (maintained by @NoahTheDuke)
cmake (maintained by @uyha)
comment (maintained by @stsewd)
commonlisp (maintained by @theHamsta)
cooklang (maintained by @addcninblue)
corn (maintained by @jakestanger)
cpon (maintained by @amaanq)
cpp (maintained by @theHamsta)
css (maintained by @TravonteD)
csv (maintained by @amaanq)
cuda (maintained by @theHamsta)
cue (maintained by @amaanq)
cylc (maintained by @elliotfontaine)
d (maintained by @amaanq)
dart (maintained by @akinsho)
desktop (maintained by @ValdezFOmar)
devicetree (maintained by @jedrzejboczar)
dhall (maintained by @amaanq)
diff (maintained by @gbprod)
disassembly (maintained by @ColinKennedy)
djot (maintained by @NoahTheDuke)
dockerfile (maintained by @camdencheek)
dot (maintained by @rydesun)
doxygen (maintained by @amaanq)
dtd (maintained by @ObserverOfTime)
earthfile (maintained by @glehmann)
ebnf (experimental, maintained by @RubixDev)
editorconfig (maintained by @ValdezFOmar)
eds (maintained by @uyha)
eex (maintained by @connorlay)
elixir (maintained by @connorlay)
elm (maintained by @zweimach)
elsa (maintained by @glapa-grossklag, @amaanq)
elvish (maintained by @elves)
embedded_template
enforce (maintained by @simonvic)
erlang (maintained by @filmor)
facility (maintained by @bryankenote)
faust (maintained by @khiner)
fennel (maintained by @alexmozaidze)
fidl (maintained by @chaopeng)
firrtl (maintained by @amaanq)
fish (maintained by @ram02z)
foam (experimental, maintained by @FoamScience)
forth (maintained by @amaanq)
fortran (maintained by @amaanq)
fsh (maintained by @mgramigna)
fsharp (maintained by @nsidorenco)
func (maintained by @amaanq)
fusion (maintained by @jirgn)
GAP system (maintained by @reiniscirpons)
GAP system test files (maintained by @reiniscirpons)
Godot (gdscript) (maintained by @PrestonKnopp)
gdshader (maintained by @godofavacyn)
git_config (maintained by @amaanq)
git_rebase (maintained by @gbprod)
gitattributes (maintained by @ObserverOfTime)
gitcommit (maintained by @gbprod)
gitignore (maintained by @theHamsta)
gleam (maintained by @amaanq)
Glimmer and Ember (maintained by @NullVoxPopuli)
glimmer_javascript (maintained by @NullVoxPopuli)
glimmer_typescript (maintained by @NullVoxPopuli)
glsl (maintained by @theHamsta)
GN (Generate Ninja) (maintained by @amaanq)
gnuplot (maintained by @dpezto)
go (maintained by @theHamsta, @WinWisely268)
goctl (maintained by @chaozwn)
Godot Resources (gdresource) (maintained by @pierpo)
gomod (maintained by @camdencheek)
gosum (maintained by @amaanq)
gotmpl (maintained by @qvalentin)
gowork (maintained by @omertuc)
gpg (maintained by @ObserverOfTime)
graphql (maintained by @bkegley)
gren (maintained by @MaeBrooks)
groovy (maintained by @murtaza64)
gstlaunch (maintained by @theHamsta)
hack
hare (maintained by @amaanq)
haskell (maintained by @mrcjkb)
haskell_persistent (maintained by @lykahb)
hcl (maintained by @MichaHoffmann)
heex (maintained by @connorlay)
helm (maintained by @qvalentin)
hjson (maintained by @winston0410)
hlsl (maintained by @theHamsta)
hlsplaylist (maintained by @Freed-Wu)
hocon (maintained by @antosha417)
hoon (experimental, maintained by @urbit-pilled)
html (maintained by @TravonteD)
htmldjango (experimental, maintained by @ObserverOfTime)
http (maintained by @amaanq, @NTBBloodbath)
hurl (maintained by @pfeiferj)
hyprlang (maintained by @luckasRanarison)
idl (maintained by @cathaysia)
idris (maintained by @srghma)
ini (experimental, maintained by @theHamsta)
inko (maintained by @yorickpeterse)
ipkg (maintained by @srghma)
ispc (maintained by @fab4100)
janet_simple (maintained by @sogaiu)
java (maintained by @p00f)
javadoc (maintained by @rmuir)
javascript (maintained by @steelsojka)
jinja (maintained by @cathaysia)
jinja_inline (maintained by @cathaysia)
jq (maintained by @ObserverOfTime)
jsdoc (maintained by @steelsojka)
json (maintained by @steelsojka)
json5 (maintained by @Joakker)
JSON with comments (maintained by @WhyNotHugo)
jsonnet (maintained by @nawordar)
julia (maintained by @fredrikekre)
just (maintained by @Hubro)
kcl (maintained by @bertbaron)
kconfig (maintained by @amaanq)
kdl (maintained by @amaanq)
kotlin (maintained by @SalBakraa)
koto (maintained by @irh)
kusto (maintained by @Willem-J-an)
lalrpop (maintained by @traxys)
latex (maintained by @theHamsta, @clason)
ledger (maintained by @cbarrete)
leo (maintained by @r001)
linkerscript (maintained by @amaanq)
liquid (maintained by @hankthetank27)
liquidsoap (maintained by @toots)
llvm (maintained by @benwilliamgraham)
lua (maintained by @muniftanjim)
luadoc (maintained by @amaanq)
lua patterns (maintained by @amaanq)
luau (maintained by @amaanq)
m68k (maintained by @grahambates)
make (maintained by @lewis6991)
markdown (basic highlighting) (experimental, maintained by @MDeiml)
markdown_inline (needed for full highlighting) (experimental, maintained by @MDeiml)
matlab (maintained by @acristoffers)
menhir (maintained by @Kerl13)
mermaid (experimental)
meson (maintained by @Decodetalkers)
mlir (experimental, maintained by @artagnon)
muttrc (maintained by @Freed-Wu)
nasm (maintained by @ObserverOfTime)
nginx (maintained by @opa-oz)
nickel
nim (maintained by @aMOPel)
nim_format_string (maintained by @aMOPel)
ninja (maintained by @alemuller)
nix (maintained by @leo60228)
norg (maintained by @JoeyGrajciar, @vhyrro)
nqc (maintained by @amaanq)
nu (maintained by @abhisheksingh0x558)
objc (maintained by @amaanq)
objdump (maintained by @ColinKennedy)
ocaml (maintained by @undu)
ocaml_interface (maintained by @undu)
ocamllex (maintained by @undu)
odin (maintained by @amaanq)
pascal (maintained by @Isopod)
passwd (maintained by @amaanq)
pem (maintained by @ObserverOfTime)
perl (maintained by @RabbiVeesh, @LeoNerd)
php (maintained by @tk-shirasaka, @calebdw)
php_only (maintained by @tk-shirasaka, @calebdw)
phpdoc (experimental, maintained by @mikehaertl)
pioasm (maintained by @leo60228)
po (maintained by @amaanq)
pod (maintained by @RabbiVeesh, @LeoNerd)
Path of Exile item filter (experimental, maintained by @ObserverOfTime)
pony (maintained by @amaanq, @mfelsche)
powershell (maintained by @L2jLiga)
printf (maintained by @ObserverOfTime)
prisma (maintained by @elianiva)
problog (maintained by @foxyseta)
prolog (maintained by @foxyseta)
promql (maintained by @MichaHoffmann)
properties (maintained by @ObserverOfTime)
proto (maintained by @treywood)
prql (maintained by @matthias-Q)
psv (maintained by @amaanq)
pug (experimental, maintained by @zealot128)
puppet (maintained by @amaanq)
purescript (maintained by @postsolar)
PyPA manifest (maintained by @ObserverOfTime)
python (maintained by @stsewd, @theHamsta)
ql (maintained by @pwntester)
qmldir (maintained by @amaanq)
qmljs (maintained by @Decodetalkers)
Tree-Sitter query language (maintained by @steelsojka)
r (maintained by @ribru17)
racket
ralph (maintained by @tdroxler)
rasi (maintained by @Fymyte)
razor (maintained by @tris203)
rbs (maintained by @joker1007)
re2c (maintained by @amaanq)
readline (maintained by @ribru17)
regex (maintained by @theHamsta)
rego (maintained by @FallenAngel97)
pip requirements (maintained by @ObserverOfTime)
rescript (maintained by @ribru17)
rnoweb (maintained by @bamonroe)
robot (maintained by @Hubro)
robots (maintained by @opa-oz)
roc (maintained by @nat-418)
ron (maintained by @amaanq)
rst (maintained by @stsewd)
ruby (maintained by @TravonteD)
runescript (maintained by @2004Scape)
rust (maintained by @amaanq)
scala (maintained by @stevanmilic)
scfg (maintained by @WhyNotHugo)
scheme
scss (maintained by @elianiva)
sflog (maintained by @aheber, @xixiaofinland)
slang (experimental, maintained by @theHamsta)
slim (maintained by @theoo)
slint (maintained by @hunger)
smali (maintained by @amaanq)
smithy (maintained by @amaanq, @keynmol)
snakemake (experimental)
solidity (maintained by @amaanq)
soql (maintained by @aheber, @xixiaofinland)
sosl (maintained by @aheber, @xixiaofinland)
sourcepawn (maintained by @Sarrus1)
sparql (maintained by @GordianDziwis)
sql (maintained by @derekstride)
squirrel (maintained by @amaanq)
ssh_config (maintained by @ObserverOfTime)
starlark (maintained by @amaanq)
strace (maintained by @amaanq)
styled (maintained by @mskelton)
supercollider (maintained by @madskjeldgaard)
superhtml (maintained by @rockorager)
surface (maintained by @connorlay)
svelte (maintained by @amaanq)
sway (maintained by @ribru17)
swift (maintained by @alex-pinkus)
sxhkdrc (maintained by @RaafatTurki)
systemtap (maintained by @ok-ryoko)
t32 (maintained by @xasc)
tablegen (maintained by @amaanq)
tact (maintained by @novusnota)
tcl (maintained by @lewis6991)
teal (maintained by @euclidianAce)
templ (maintained by @vrischmann)
tera (maintained by @uncenter)
terraform (maintained by @MichaHoffmann)
textproto (maintained by @Porter)
thrift (maintained by @amaanq, @duskmoon314)
tiger (maintained by @ambroisie)
tlaplus (maintained by @ahelwer, @susliko)
tmux (maintained by @Freed-Wu)
todotxt (experimental, maintained by @arnarg)
toml (maintained by @tk-shirasaka)
tsv (maintained by @amaanq)
tsx (maintained by @steelsojka)
turtle (maintained by @GordianDziwis)
twig (maintained by @gbprod)
typescript (maintained by @steelsojka)
typespec (maintained by @happenslol)
typoscript (maintained by @Teddytrombone)
typst (maintained by @uben0, @RaafatTurki)
udev (maintained by @ObserverOfTime)
ungrammar (maintained by @Philipp-M, @amaanq)
unison (maintained by @tapegram)
usd (maintained by @ColinKennedy)
uxn tal (maintained by @amaanq)
v (maintained by @kkharji, @amaanq)
vala (maintained by @Prince781)
vento (maintained by @wrapperup, @oscarotero)
verilog (maintained by @zhangwwpeng)
vhdl (maintained by @jpt13653903)
vhs (maintained by @caarlos0)
vim (maintained by @clason)
vimdoc (maintained by @clason)
vrl (maintained by @belltoy)
vue (maintained by @WhyNotHugo, @lucario387)
wgsl (maintained by @szebniok)
wgsl_bevy (maintained by @theHamsta)
wing (maintained by @gshpychka, @MarkMcCulloh)
wit (maintained by @liamwh)
xcompose (maintained by @ObserverOfTime)
xml (maintained by @ObserverOfTime)
xresources (maintained by @ValdezFOmar)
yaml (maintained by @amaanq)
yang (maintained by @Hubro)
yuck (maintained by @Philipp-M, @amaanq)
zathurarc (maintained by @Freed-Wu)
zig (maintained by @amaanq)
ziggy (maintained by @rockorager)
ziggy_schema (maintained by @rockorager)

For related information on the supported languages, including related plugins, see this wiki page.

Available modules

Modules provide the top-level features of nvim-treesitter. The following is a list of modules included in nvim-treesitter and their configuration via init.lua (where multiple modules can be combined in a single call to setup). Note that not all modules work for all languages (depending on the queries available for them). Additional modules can be provided as external plugins.

Highlight

Consistent syntax highlighting.

require'nvim-treesitter.configs'.setup {
  highlight = {
    enable = true,
    -- Setting this to true will run `:h syntax` and tree-sitter at the same time.
    -- Set this to `true` if you depend on 'syntax' being enabled (like for indentation).
    -- Using this option may slow down your editor, and you may see some duplicate highlights.
    -- Instead of true it can also be a list of languages
    additional_vim_regex_highlighting = false,
  },
}

To customize the syntax highlighting of a capture, simply define or link a highlight group of the same name:

1
2

-- Highlight the @foo.bar capture group with the "Identifier" highlight group
vim.api.nvim_set_hl(0, "@foo.bar", { link = "Identifier" })

For a language-specific highlight, append the name of the language:

1
2

-- Highlight @foo.bar as "Identifier" only in Lua files
vim.api.nvim_set_hl(0, "@foo.bar.lua", { link = "Identifier" })

See :h treesitter-highlight-groups for details.

Incremental selection

Incremental selection based on the named nodes from the grammar.

require'nvim-treesitter.configs'.setup {
  incremental_selection = {
    enable = true,
    keymaps = {
      init_selection = "gnn", -- set to `false` to disable one of the mappings
      node_incremental = "grn",
      scope_incremental = "grc",
      node_decremental = "grm",
    },
  },
}

Indentation

Indentation based on treesitter for the = operator. NOTE: This is an experimental feature.

require'nvim-treesitter.configs'.setup {
  indent = {
    enable = true
  }
}

Folding

Tree-sitter based folding (implemented in Neovim itself, see :h vim.treesitter.foldexpr()). To enable it for the current window, set

1
2

vim.wo.foldmethod = 'expr'
vim.wo.foldexpr = 'v:lua.vim.treesitter.foldexpr()'

This will respect your foldminlines and foldnestmax settings.

Advanced setup

Changing the parser install directory

If you want to install the parsers to a custom directory you can specify this directory with parser_install_dir option in that is passed to setup. nvim-treesitter will then install the parser files into this directory.

This directory must be writeable and must be explicitly prepended to the runtimepath. For example:

  -- It MUST be at the beginning of runtimepath. Otherwise the parsers from Neovim itself
  -- is loaded that may not be compatible with the queries from the 'nvim-treesitter' plugin.
  vim.opt.runtimepath:prepend("/some/path/to/store/parsers")

  require'nvim-treesitter.configs'.setup {
    parser_install_dir = "/some/path/to/store/parsers",

    ...

  }

If this option is not included in the setup options, or is explicitly set to nil then the default install directories will be used. If this value is set the default directories will be ignored.

Bear in mind that any parser installed into a parser folder on the runtime path will still be considered installed. (For example if “~/.local/share/nvim/site/parser/c.so” exists then the “c” parser will be considered installed, even though it is not in parser_install_dir)

The default paths are:

first the package folder. Where nvim-treesitter is installed.
second the site directory. This is the “site” subdirectory of stdpath("data").

Adding parsers

If you have a parser that is not on the list of supported languages (either as a repository on Github or in a local directory), you can add it manually for use by nvim-treesitter as follows:

Clone the repository or create a new project in, say, ~/projects/tree-sitter-zimbu. Make sure that the tree-sitter-cli executable is installed and in your path; see https://tree-sitter.github.io/tree-sitter/creating-parsers#installation for installation instructions.
Run tree-sitter generate in this directory (followed by tree-sitter test for good measure).
Add the following snippet to your init.lua:

local parser_config = require "nvim-treesitter.parsers".get_parser_configs()
parser_config.zimbu = {
  install_info = {
    url = "~/projects/tree-sitter-zimbu", -- local path or git repo
    files = {"src/parser.c"}, -- note that some parsers also require src/scanner.c or src/scanner.cc
    -- optional entries:
    branch = "main", -- default branch in case of git repo if different from master
    generate_requires_npm = false, -- if stand-alone parser without npm dependencies
    requires_generate_from_grammar = false, -- if folder contains pre-generated src/parser.c
  },
  filetype = "zu", -- if filetype does not match the parser name
}

If you wish to set a specific parser for a filetype, you should use vim.treesitter.language.register():

`1`	`vim.treesitter.language.register('python', 'someft') -- the someft filetype will use the python parser and queries.`

Note this requires Nvim v0.9.

Start nvim and :TSInstall zimbu.

You can also skip step 2 and use :TSInstallFromGrammar zimbu to install directly from a grammar.js in the top-level directory specified by url. Once the parser is installed, you can update it (from the latest revision of the main branch if url is a Github repository) with :TSUpdate zimbu.

Note that neither :TSInstall nor :TSInstallFromGrammar copy query files from the grammar repository. If you want your installed grammar to be useful, you must manually add query files to your local nvim-treesitter installation. Note also that module functionality is only triggered if your language’s filetype is correctly identified. If Neovim does not detect your language’s filetype by default, you can use Neovim’s vim.filetype.add() to add a custom detection rule.

If you use a git repository for your parser and want to use a specific version, you can set the revision key in the install_info table for you parser config.

Adding queries

Queries are what nvim-treesitter uses to extract information from the syntax tree; they are located in the queries/{language}/* runtime directories (see :h rtp), like the queries folder of this plugin, e.g. queries/{language}/{locals,highlights,textobjects}.scm. Other modules may require additional queries such as folding.scm. You can find a list of all supported capture names in CONTRIBUTING.md.

The first query file on runtimepath will be used (see :h treesitter-query). If you want to make a query on the user config extend other queries instead of replacing them, see :h treesitter-query-modeline-extends.

If you want to completely override a query, you can use :h vim.treesitter.query.set(). For example, to override the injections queries from c with your own:

`1`	`vim.treesitter.query.set("c", "injections", "(comment) @comment")`

Note: when using query.set(), all queries in the runtime directories will be ignored.

Adding modules

If you wish you write your own module, you need to support

tree-sitter language detection support;
attaching and detaching to buffers;
all nvim-treesitter commands.

At the top level, you can use the define_modules function to define one or more modules or module groups:

require'nvim-treesitter'.define_modules {
  my_cool_plugin = {
    attach = function(bufnr, lang)
      -- Do cool stuff here
    end,
    detach = function(bufnr)
      -- Undo cool stuff here
    end,
    is_supported = function(lang)
      -- Check if the language is supported
    end
  }
}

with the following properties:

module_path specifies a require path (string) that exports a module with an attach and detach function. This is not required if the functions are on this definition.
enable determines if the module is enabled by default. This is usually overridden by the user.
disable takes a list of languages that this module is disabled for. This is usually overridden by the user.
is_supported takes a function that takes a language and determines if this module supports that language.
attach takes a function that attaches to a buffer. This is required if module_path is not provided.
detach takes a function that detaches from a buffer. This is required if module_path is not provided.

Extra features

Statusline indicator

1
2

echo nvim_treesitter#statusline(90)  " 90 can be any length
module->expression_statement->call->identifier

Utilities

You can get some utility functions with

`1`	`local ts_utils = require 'nvim-treesitter.ts_utils'`

Check :h nvim-treesitter-utils for more information.

Troubleshooting

Before doing anything, make sure you have the latest version of this plugin and run :checkhealth nvim-treesitter. It can also help to update the parsers via :TSUpdate.

Feature `X` does not work for `{language}`…

First, check the health#nvim_treesitter#check and the health#treesitter#check sections of :checkhealth for any warning. If there is one, it’s highly likely that this is the cause of the problem.

Next check the ## Parser/Features subsection of the health#nvim_treesitter#check section of :checkhealth to ensure the desired module is enabled for your language. If not, you might be missing query files; see Adding queries.

Finally, ensure Neovim is correctly identifying your language’s filetype using the :echo &filetype command while one of your language’s files is open in Neovim. If not, add a short Vimscript file to nvim-treesitter’s ftdetect runtime directory following Neovim’s documentation on filetype detection. You can also quickly & temporarily set the filetype for a single buffer with the :set filetype=langname command to test whether it fixes the problem.

If everything is okay, then it might be an actual error. In that case, feel free to open an issue here.

I get `module 'vim.treesitter.query' not found`

Make sure you have the latest version of Neovim.

I get `Error detected while processing .../plugin/nvim-treesitter.vim` every time I open Neovim

This is probably due to a change in a parser’s grammar or its queries. Try updating the parser that you suspect has changed (:TSUpdate {language}) or all of them (:TSUpdate). If the error persists after updating all parsers, please open an issue.

I get `query error: invalid node type at position`

This could be due a query file outside this plugin using outdated nodes, or due to an outdated parser.

Make sure you have the parsers up to date with :TSUpdate
Make sure you don’t have more than one parser runtime directory. You can execute this command :echo nvim_get_runtime_file('parser', v:true) to find all runtime directories. If you get more than one path, remove the ones that are outside this plugin (nvim-treesitter directory), so the correct version of the parser is used.

I experience weird highlighting issues similar to #78

This is a well known issue, which arises when the tree and the buffer have gotten out of sync. As this is an upstream issue, we don’t have any definite fix. To get around this, you can force reparsing the buffer with

`1`	`:write \| edit \| TSBufEnable highlight`

This will save, restore and enable highlighting for the current buffer.

I experience bugs when using `nvim-treesitter`’s `foldexpr` similar to #194

This might happen, and is known to happen, with vim-clap. To avoid these kind of errors, please use setlocal instead of set for the respective filetypes.

I run into errors like `module 'nvim-treesitter.configs' not found` at startup

This is because of rtp management in nvim, adding packadd nvim-treesitter should fix the issue.

I want to use Git instead of curl for downloading the parsers

In your Lua config:

`1`	`require("nvim-treesitter.install").prefer_git = true`

I want to use a HTTP proxy for downloading the parsers

You can either configure curl to use additional CLI arguments in your Lua config:

1
2
3

require("nvim-treesitter.install").command_extra_args = {
    curl = { "--proxy", "<proxy url>" },
}

or you can configure git via .gitconfig and use git instead of curl

`1`	`require("nvim-treesitter.install").prefer_git = true`

I want to use a mirror instead of “https://github.com/"

In your Lua config:

for _, config in pairs(require("nvim-treesitter.parsers").get_parser_configs()) do
  config.install_info.url = config.install_info.url:gsub("https://github.com/", "something else")
end

require'nvim-treesitter.configs'.setup {
    --
    --
}

Using an existing parser for another filetype

For example, to use the bash tree-sitter to highlight file with filetype=apkbuild, use:

`1`	`vim.treesitter.language.register("bash", "apkbuild")`

The bash tree-sitter must be installed following the usual procedure as described above.

kickstart.nvim

Wed, 14 May 2025 15:30:02 +0800

nvim-lua/kickstart.nvim

kickstart.nvim

Introduction

A starting point for Neovim that is:

Small
Single-file
Completely Documented

NOT a Neovim distribution, but instead a starting point for your configuration.

Installation

Install Neovim

Kickstart.nvim targets only the latest ‘stable’ and latest ’nightly’ of Neovim. If you are experiencing issues, please make sure you have the latest versions.

Install External Dependencies

External Requirements:

Basic utils: git, make, unzip, C Compiler (gcc)
ripgrep, fd-find
Clipboard tool (xclip/xsel/win32yank or other depending on the platform)
A Nerd Font: optional, provides various icons
- if you have it set vim.g.have_nerd_font in init.lua to true
Emoji fonts (Ubuntu only, and only if you want emoji!) sudo apt install fonts-noto-color-emoji
Language Setup:
- If you want to write Typescript, you need npm
- If you want to write Golang, you will need go
- etc.

[!NOTE] See Install Recipes for additional Windows and Linux specific notes and quick install snippets

Install Kickstart

[!NOTE] Backup your previous configuration (if any exists)

Neovim’s configurations are located under the following paths, depending on your OS:

OS	PATH
Linux, MacOS	`$XDG_CONFIG_HOME/nvim`, `~/.config/nvim`
Windows (cmd)	`%localappdata%\nvim\`
Windows (powershell)	`$env:LOCALAPPDATA\nvim\`

Recommended Step

Fork this repo so that you have your own copy that you can modify, then install by cloning the fork to your machine using one of the commands below, depending on your OS.

[!NOTE] Your fork’s URL will be something like this: https://github.com/<your_github_username>/kickstart.nvim.git

You likely want to remove lazy-lock.json from your fork’s .gitignore file too - it’s ignored in the kickstart repo to make maintenance easier, but it’s recommended to track it in version control.

Clone kickstart.nvim

[!NOTE] If following the recommended step above (i.e., forking the repo), replace nvim-lua with <your_github_username> in the commands below

Linux and Mac

`1`	`git clone https://github.com/nvim-lua/kickstart.nvim.git "${XDG_CONFIG_HOME:-$HOME/.config}"/nvim`

Windows

If you’re using cmd.exe:

`1`	`git clone https://github.com/nvim-lua/kickstart.nvim.git "%localappdata%\nvim"`

If you’re using powershell.exe

`1`	`git clone https://github.com/nvim-lua/kickstart.nvim.git "${env:LOCALAPPDATA}\nvim"`

Post Installation

Start Neovim

nvim

That’s it! Lazy will install all the plugins you have. Use :Lazy to view the current plugin status. Hit q to close the window.

Read The Friendly Documentation

Read through the init.lua file in your configuration folder for more information about extending and exploring Neovim. That also includes examples of adding popularly requested plugins.

[!NOTE] For more information about a particular plugin check its repository’s documentation.

Getting Started

The Only Video You Need to Get Started with Neovim

FAQ

What should I do if I already have a pre-existing Neovim configuration?
- You should back it up and then delete all associated files.
- This includes your existing init.lua and the Neovim files in ~/.local which can be deleted with rm -rf ~/.local/share/nvim/
Can I keep my existing configuration in parallel to kickstart?
- Yes! You can use NVIM_APPNAME=nvim-NAME to maintain multiple configurations. For example, you can install the kickstart configuration in ~/.config/nvim-kickstart and create an alias:
  1
  
  alias nvim-kickstart='NVIM_APPNAME="nvim-kickstart" nvim'
  When you run Neovim using nvim-kickstart alias it will use the alternative config directory and the matching local directory ~/.local/share/nvim-kickstart. You can apply this approach to any Neovim distribution that you would like to try out.
What if I want to “uninstall” this configuration:
- See lazy.nvim uninstall information
Why is the kickstart init.lua a single file? Wouldn’t it make sense to split it into multiple files?
- The main purpose of kickstart is to serve as a teaching tool and a reference configuration that someone can easily use to git clone as a basis for their own. As you progress in learning Neovim and Lua, you might consider splitting init.lua into smaller parts. A fork of kickstart that does this while maintaining the same functionality is available here:
  - kickstart-modular.nvim
- Discussions on this topic can be found here:
  - Restructure the configuration
  - Reorganize init.lua into a multi-file setup

Install Recipes

Below you can find OS specific install instructions for Neovim and dependencies.

After installing all the dependencies continue with the Install Kickstart step.

Windows Installation

Windows with Microsoft C++ Build Tools and CMake

Installation may require installing build tools and updating the run command for `telescope-fzf-native`

See telescope-fzf-native documentation for more details

This requires:

Install CMake and the Microsoft C++ Build Tools on Windows

`1`	`{'nvim-telescope/telescope-fzf-native.nvim', build = 'cmake -S. -Bbuild -DCMAKE_BUILD_TYPE=Release && cmake --build build --config Release && cmake --install build --prefix build' }`

Windows with gcc/make using chocolatey

Alternatively, one can install gcc and make which don't require changing the config, the easiest way is to use choco:

install chocolatey either follow the instructions on the page or use winget, run in cmd as admin:

`1`	`winget install --accept-source-agreements chocolatey.chocolatey`

install all requirements using choco, exit the previous cmd and open a new one so that choco path is set, and run in cmd as admin:

`1`	`choco install -y neovim git ripgrep wget fd unzip gzip mingw make`

WSL (Windows Subsystem for Linux)

wsl --install
wsl
sudo add-apt-repository ppa:neovim-ppa/unstable -y
sudo apt update
sudo apt install make gcc ripgrep unzip git xclip neovim

Linux Install

Ubuntu Install Steps

1
2
3

sudo add-apt-repository ppa:neovim-ppa/unstable -y
sudo apt update
sudo apt install make gcc ripgrep unzip git xclip neovim

Debian Install Steps

sudo apt update
sudo apt install make gcc ripgrep unzip git xclip curl

# Now we install nvim
curl -LO https://github.com/neovim/neovim/releases/latest/download/nvim-linux-x86_64.tar.gz
sudo rm -rf /opt/nvim-linux-x86_64
sudo mkdir -p /opt/nvim-linux-x86_64
sudo chmod a+rX /opt/nvim-linux-x86_64
sudo tar -C /opt -xzf nvim-linux-x86_64.tar.gz

# make it available in /usr/local/bin, distro installs to /usr/bin
sudo ln -sf /opt/nvim-linux-x86_64/bin/nvim /usr/local/bin/

Fedora Install Steps

`1`	`sudo dnf install -y gcc make git ripgrep fd-find unzip neovim`

Arch Install Steps

`1`	`sudo pacman -S --noconfirm --needed gcc make git ripgrep fd unzip neovim`

glance

Wed, 07 May 2025 15:29:28 +0800

glanceapp/glance

What if you could see everything at a...

Glance

Install • Configuration • Discord • Sponsor

Community widgets • Preconfigured pages • Themes

Features

Various widgets

RSS feeds
Subreddit posts
Hacker News posts
Weather forecasts
YouTube channel uploads
Twitch channels
Market prices
Docker containers status
Server stats
Custom widgets
and many more…

Fast and lightweight

Low memory usage
Few dependencies
Minimal vanilla JS
Single <20mb binary available for multiple OSs & architectures and just as small Docker container
Uncached pages usually load within ~1s (depending on internet speed and number of widgets)

Tons of customizability

Different layouts
As many pages/tabs as you need
Numerous configuration options for each widget
Multiple styles for some widgets
Custom CSS

Optimized for mobile devices

Because you’ll want to take it with you on the go.

Themeable

Easily create your own theme by tweaking a few numbers or choose from one of the already available themes.

Configuration

Configuration is done through YAML files, to learn more about how the layout works, how to add more pages and how to configure widgets, visit the configuration documentation.

Preview example configuration file

pages:
  - name: Home
    columns:
      - size: small
        widgets:
          - type: calendar
            first-day-of-week: monday

          - type: rss
            limit: 10
            collapse-after: 3
            cache: 12h
            feeds:
              - url: https://selfh.st/rss/
                title: selfh.st
                limit: 4
              - url: https://ciechanow.ski/atom.xml
              - url: https://www.joshwcomeau.com/rss.xml
                title: Josh Comeau
              - url: https://samwho.dev/rss.xml
              - url: https://ishadeed.com/feed.xml
                title: Ahmad Shadeed

          - type: twitch-channels
            channels:
              - theprimeagen
              - j_blow
              - piratesoftware
              - cohhcarnage
              - christitustech
              - EJ_SA

      - size: full
        widgets:
          - type: group
            widgets:
              - type: hacker-news
              - type: lobsters

          - type: videos
            channels:
              - UCXuqSBlHAE6Xw-yeJA0Tunw # Linus Tech Tips
              - UCR-DXc1voovS8nhAvccRZhg # Jeff Geerling
              - UCsBjURrPoezykLs9EqgamOA # Fireship
              - UCBJycsmduvYEL83R_U4JriQ # Marques Brownlee
              - UCHnyfMqiRRG1u-2MsSQLbXA # Veritasium

          - type: group
            widgets:
              - type: reddit
                subreddit: technology
                show-thumbnails: true
              - type: reddit
                subreddit: selfhosted
                show-thumbnails: true

      - size: small
        widgets:
          - type: weather
            location: London, United Kingdom
            units: metric
            hour-format: 12h

          - type: markets
            markets:
              - symbol: SPY
                name: S&P 500
              - symbol: BTC-USD
                name: Bitcoin
              - symbol: NVDA
                name: NVIDIA
              - symbol: AAPL
                name: Apple
              - symbol: MSFT
                name: Microsoft

          - type: releases
            cache: 1d
            repositories:
              - glanceapp/glance
              - go-gitea/gitea
              - immich-app/immich
              - syncthing/syncthing

Installation

Choose one of the following methods:

Docker compose using provided directory structure (recommended)

Create a new directory called glance as well as the template files within it by running:

`1`	`mkdir glance && cd glance && curl -sL https://github.com/glanceapp/docker-compose-template/archive/refs/heads/main.tar.gz \| tar -xzf - --strip-components 2`

click here to view the files that will be created

Then, edit the following files as desired:

docker-compose.yml to configure the port, volumes and other containery things
config/home.yml to configure the widgets or layout of the home page
config/glance.yml if you want to change the theme or add more pages

Other files you may want to edit

.env to configure environment variables that will be available inside configuration files
assets/user.css to add custom CSS

When ready, run:

`1`	`docker compose up -d`

If you encounter any issues, you can check the logs by running:

`1`	`docker compose logs`

Docker compose manual

Create a docker-compose.yml file with the following contents:

services:
  glance:
    container_name: glance
    image: glanceapp/glance
    restart: unless-stopped
    volumes:
      - ./config:/app/config
    ports:
      - 8080:8080

Then, create a new directory called config and download the example starting glance.yml file into it by running:

`1`	`mkdir config && wget -O config/glance.yml https://raw.githubusercontent.com/glanceapp/glance/refs/heads/main/docs/glance.yml`

Feel free to edit the glance.yml file to your liking, and when ready run:

`1`	`docker compose up -d`

If you encounter any issues, you can check the logs by running:

`1`	`docker logs glance`

Manual binary installation

Precompiled binaries are available for Linux, Windows and macOS (x86, x86_64, ARM and ARM64 architectures).

Linux

Visit the latest release page for available binaries. You can place the binary in /opt/glance/ and have it start with your server via a systemd service. By default, when running the binary, it will look for a glance.yml file in the directory it’s placed in. To specify a different path for the config file, use the --config option:

`1`	`/opt/glance/glance --config /etc/glance.yml`

To grab a starting template for the config file, run:

`1`	`wget https://raw.githubusercontent.com/glanceapp/glance/refs/heads/main/docs/glance.yml`

Windows

Download and extract the executable from the latest release (most likely the file called glance-windows-amd64.zip if you’re on a 64-bit system) and place it in a folder of your choice. Then, create a new text file called glance.yml in the same folder and paste the content from here in it. You should then be able to run the executable and access the dashboard by visiting http://localhost:8080 in your browser.

Other

Glance can also be installed through the following 3rd party channels:

Common issues

Requests timing out

The most common cause of this is when using Pi-Hole, AdGuard Home or other ad-blocking DNS services, which by default have a fairly low rate limit. Depending on the number of widgets you have in a single page, this limit can very easily be exceeded. To fix this, increase the rate limit in the settings of your DNS service.

If using Podman, in some rare cases the timeout can be caused by an unknown issue, in which case it may be resolved by adding the following to the bottom of your docker-compose.yml file:

1
2
3

networks:
  podman:
    external: true

Broken layout for markets, bookmarks or other widgets

This is almost always caused by the browser extension Dark Reader. To fix this, disable dark mode for the domain where Glance is hosted.

cannot unmarshal !!map into []glance.page

The most common cause of this is having a pages key in your glance.yml and then also having a pages key inside one of your included pages. To fix this, remove the pages key from the top of your included pages.

FAQ

Does the information on the page update automatically?

No, a page refresh is required to update the information. Some things do dynamically update where it makes sense, like the clock widget and the relative time showing how long ago something happened.

How frequently do widgets update?

No requests are made periodically in the background, information is only fetched upon loading the page and then cached. The default cache lifetime is different for each widget and can be configured.

Can I create my own widgets?

Yes, there are multiple ways to create custom widgets:

iframe widget - allows you to embed things from other websites
html widget - allows you to insert your own static HTML
extension widget - fetch HTML from a URL
custom-api widget - fetch JSON from a URL and render it using custom HTML

Can I change the title of a widget?

Yes, the title of all widgets can be changed by specifying the title property in the widget’s configuration:

- type: rss
  title: My custom title

- type: markets
  title: My custom title

- type: videos
  title: My custom title

# and so on for all widgets...

Feature requests

New feature suggestions are always welcome and will be considered, though please keep in mind that some of them may be out of scope for what the project is trying to achieve (or is reasonably capable of). If you have an idea for a new feature and would like to share it, you can do so here.

Feature requests are tagged with one of the following:

Roadmap - will be implemented in a future release
Backlog - may be implemented in the future but needs further feedback or interest from the community
Icebox - no plans to implement as it doesn’t currently align with the project’s goals or capabilities, may be revised at a later date

Building from source

Choose one of the following methods:

Build binary with Go

Requirements: Go >= v1.23

To build the project for your current OS and architecture, run:

`1`	`go build -o build/glance .`

To build for a specific OS and architecture, run:

`1`	`GOOS=linux GOARCH=amd64 go build -o build/glance .`

click here for a full list of GOOS and GOARCH combinations

Alternatively, if you just want to run the app without creating a binary, like when you’re testing out changes, you can run:

`1`	`go run .`

Build project and Docker image with Docker

Requirements: Docker

To build the project and image using just Docker, run:

(replace owner with your name or organization)

`1`	`docker build -t owner/glance:latest .`

If you wish to push the image to a registry (by default Docker Hub), run:

`1`	`docker push owner/glance:latest`

Contributing guidelines

Before working on a new feature it’s preferable to submit a feature request first and state that you’d like to implement it yourself
Please don’t submit PRs for feature requests that are either in the roadmap^[1], backlog^[2] or icebox^[3]
Use dev for the base branch if you’re adding new features or fixing bugs, otherwise use main
Avoid introducing new dependencies
Avoid making backwards-incompatible configuration changes
Avoid introducing new colors or hard-coding colors, use the standard primary, positive and negative
For icons, try to use heroicons where applicable
Provide a screenshot of the changes if UI related where possible
No package.json

^{[1] [2] [3]}

[1] The feature likely already has work put into it that may conflict with your implementation

[2] The demand, implementation or functionality for this feature is not yet clear

[3] No plans to add this feature for the time being

Thank you

To all the people who were generous enough to sponsor the project and to everyone who has contributed in any way, be it PRs, submitting issues, helping others in the discussions or Discord server, creating guides and tools or just mentioning Glance on social media. Your support is greatly appreciated and helps keep the project going.

alacritty

Sun, 04 May 2025 15:27:28 +0800

alacritty/alacritty

Alacritty - A fast, cross-platform, OpenGL terminal emulator

About

Alacritty is a modern terminal emulator that comes with sensible defaults, but allows for extensive configuration. By integrating with other applications, rather than reimplementing their functionality, it manages to provide a flexible set of features with high performance. The supported platforms currently consist of BSD, Linux, macOS and Windows.

The software is considered to be at a beta level of readiness; there are a few missing features and bugs to be fixed, but it is already used by many as a daily driver.

Precompiled binaries are available from the GitHub releases page.

Join #alacritty on libera.chat if you have questions or looking for a quick help.

Features

You can find an overview over the features available in Alacritty here.

Further information

Announcing Alacritty, a GPU-Accelerated Terminal Emulator January 6, 2017
A talk about Alacritty at the Rust Meetup January 2017 January 19, 2017
Alacritty Lands Scrollback, Publishes Benchmarks September 17, 2018

Installation

Alacritty can be installed by using various package managers on Linux, BSD, macOS and Windows.

Prebuilt binaries for macOS and Windows can also be downloaded from the GitHub releases page.

For everyone else, the detailed instructions to install Alacritty can be found here.

Requirements

At least OpenGL ES 2.0
[Windows] ConPTY support (Windows 10 version 1809 or higher)

Configuration

You can find the documentation for Alacritty’s configuration in man 5 alacritty, or by looking at the website if you do not have the manpages installed.

Alacritty doesn’t create the config file for you, but it looks for one in the following locations:

$XDG_CONFIG_HOME/alacritty/alacritty.toml
$XDG_CONFIG_HOME/alacritty.toml
$HOME/.config/alacritty/alacritty.toml
$HOME/.alacritty.toml

On Windows, the config file will be looked for in:

%APPDATA%\alacritty\alacritty.toml

Contributing

A guideline about contributing to Alacritty can be found in the CONTRIBUTING.md file.

FAQ

Is it really the fastest terminal emulator?

Benchmarking terminal emulators is complicated. Alacritty uses vtebench to quantify terminal emulator throughput and manages to consistently score better than the competition using it. If you have found an example where this is not the case, please report a bug.

Other aspects like latency or framerate and frame consistency are more difficult to quantify. Some terminal emulators also intentionally slow down to save resources, which might be preferred by some users.

If you have doubts about Alacritty’s performance or usability, the best way to quantify terminal emulators is always to test them with your specific usecases.

Why isn’t feature X implemented?

Alacritty has many great features, but not every feature from every other terminal. This could be for a number of reasons, but sometimes it’s just not a good fit for Alacritty. This means you won’t find things like tabs or splits (which are best left to a window manager or terminal multiplexer) nor niceties like a GUI config editor.

License

Alacritty is released under the Apache License, Version 2.0.

winutil

Sun, 04 May 2025 15:26:19 +0800

ChrisTitusTech/winutil

Chris Titus Tech’s Windows Utility

This utility is a compilation of Windows tasks I perform on each Windows system I use. It is meant to streamline installs, debloat with tweaks, troubleshoot with config, and fix Windows updates. I am extremely picky about any contributions to keep this project clean and efficient.

💡 Usage

Winutil must be run in Admin mode because it performs system-wide tweaks. To achieve this, run PowerShell as an administrator. Here are a few ways to do it:

Start menu Method:
- Right-click on the start menu.
- Choose “Windows PowerShell (Admin)” (for Windows 10) or “Terminal (Admin)” (for Windows 11).
Search and Launch Method:
- Press the Windows key.
- Type “PowerShell” or “Terminal” (for Windows 11).
- Press Ctrl + Shift + Enter or Right-click and choose “Run as administrator” to launch it with administrator privileges.

Launch Command

Stable Branch (Recommended)

`1`	`irm "https://christitus.com/win" \| iex`

Dev Branch

`1`	`irm "https://christitus.com/windev" \| iex`

If you have Issues, refer to Known Issues

🎓 Documentation

WinUtil Official Documentation

YouTube Tutorial

ChrisTitus.com Article

💖 Support

To morally and mentally support the project, make sure to leave a ⭐️!
EXE Wrapper for $10 @ https://www.cttstore.com/windows-toolbox

💖 Sponsors

These are the sponsors that help keep this project alive with monthly contributions.

🏅 Thanks to all Contributors

Thanks a lot for spending your time helping Winutil grow. Thanks a lot! Keep rocking 🍻.

📊 GitHub Stats

AeroSpace

Tue, 29 Apr 2025 15:30:55 +0800

nikitabobko/AeroSpace

AeroSpace Beta

AeroSpace is an i3-like tiling window manager for macOS

Videos:

Docs:

Project status

Public Beta. AeroSpace can be used as a daily driver, but expect breaking changes until 1.0 is reached.

Key features

Tiling window manager based on a tree paradigm
i3 inspired
Fast workspaces switching without animations and without the necessity to disable SIP
AeroSpace employs its own emulation of virtual workspaces instead of relying on native macOS Spaces due to their considerable limitations
Plain text configuration (dotfiles friendly). See: default-config.toml
CLI first (manpages and shell completion included)
Doesn’t require disabling SIP (System Integrity Protection)
Proper multi-monitor support (i3-like paradigm)

Installation

Install via Homebrew to get autoupdates (Preferred)

`1`	`brew install --cask nikitabobko/tap/aerospace`

In multi-monitor setup please make sure that monitors are properly arranged.

Other installation options: https://nikitabobko.github.io/AeroSpace/guide#installation

[!NOTE] By using AeroSpace, you acknowledge that it’s not notarized.

Notarization is a “security” feature by Apple. You send binaries to Apple, and they either approve them or not. In reality, notarization is about building binaries the way Apple likes it.

I don’t have anything against notarization as a concept. I specifically don’t like the way Apple does notarization. I don’t have time to deal with Apple.

Homebrew installation script is configured to automatically delete com.apple.quarantine attribute, that’s why the app should work out of the box, without any warnings that “Apple cannot check AeroSpace for malicious software”

Community, discussions, issues

Unfortunately, AeroSpace project doesn’t openly accept Issues. Please read CONTRIBUTING.md for more details.

Community discussions happen at GitHub Discussions. There you can discuss bugs, propose new features, ask your questions, show off your setup, or just chat.

There are 7 channels:

#all. RSS. Feed with all discussions.
#announcements. RSS. Only maintainers can post here. Highly moderated traffic.
#announcements-releases. RSS. Announcements about non-patch releases. Only maintainers can post here.
#feature-ideas. RSS.
#general. RSS.
#potential-bugs. RSS. If you think that you have encountered a bug, you can discuss your bugs here.
#questions-and-answers. RSS. Everyone is welcome to ask questions. Everyone is encouraged to answer other people’s questions.

Development

A notes on how to setup the project, build it, how to run the tests, etc. can be found here: dev-docs/development.md

Project values

Values

AeroSpace is targeted at advanced users and developers
Keyboard centric
Breaking changes (configuration files, CLI, behavior) are avoided as much as possible, but it must not let the software stagnate. Thus breaking changes can happen, but with careful considerations and helpful message. Semver major version is bumped in case of a breaking change (It’s all guaranteed once AeroSpace reaches 1.0 version, until then breaking changes just happen)
AeroSpace doesn’t use GUI, unless necessarily
- AeroSpace will never provide a GUI for configuration. For advanced users, it’s easier to edit a configuration file in text editor rather than navigating through checkboxes in GUI.
- Status menu icon is ok, because visual feedback is needed
Provide practical features. Fancy appearance features are not practical (e.g. window borders, transparency, animations, etc.)
“dark magic” (aka “private APIs”, “code injections”, etc.) must be avoided as much as possible
- Right now, AeroSpace uses only a single private API to get window ID of accessibility object _AXUIElementGetWindow. Everything else is macOS public accessibility API.
- AeroSpace will never require you to disable SIP (System Integrity Protection).
- The goal is to make AeroSpace easily maintainable, and resistant to macOS updates.

Non Values

Play nicely with existing macOS features. If limitations are imposed then AeroSpace won’t play nicely with existing macOS features (For example, AeroSpace doesn’t acknowledge the existence of macOS Spaces, and it uses emulation of its own workspaces)
Ricing. AeroSpace provides only a very minimal support for ricing - gaps and a few callbacks for integrations with bars. The current maintainer doesn’t care about ricing. Ricing issues are not a priority, and they are mostly ignored. The ricing stance can change only with the appearance of more maintainers.

Tip of the day

`1`	`defaults write -g NSWindowShouldDragOnGesture -bool true`

Now, you can move windows by holding ctrl+cmd and dragging any part of the window (not necessarily the window title)

Source: reddit

godotenv

Sat, 26 Apr 2025 15:26:32 +0800

joho/godotenv

GoDotEnv

A Go (golang) port of the Ruby dotenv project (which loads env vars from a .env file).

From the original Library:

Storing configuration in the environment is one of the tenets of a twelve-factor app. Anything that is likely to change between deployment environments–such as resource handles for databases or credentials for external services–should be extracted from the code into environment variables.

But it is not always practical to set environment variables on development machines or continuous integration servers where multiple projects are run. Dotenv load variables from a .env file into ENV when the environment is bootstrapped.

It can be used as a library (for loading in env for your own daemons etc.) or as a bin command.

There is test coverage and CI for both linuxish and Windows environments, but I make no guarantees about the bin version working on Windows.

Installation

As a library

`1`	`go get github.com/joho/godotenv`

or if you want to use it as a bin command

go >= 1.17

`1`	`go install github.com/joho/godotenv/cmd/godotenv@latest`

go < 1.17

`1`	`go get github.com/joho/godotenv/cmd/godotenv`

Usage

Add your application configuration to your .env file in the root of your project:

1
2

S3_BUCKET=YOURS3BUCKET
SECRET_KEY=YOURSECRETKEYGOESHERE

Then in your Go app you can do something like

package main

import (
    "log"
    "os"

    "github.com/joho/godotenv"
)

func main() {
  err := godotenv.Load()
  if err != nil {
    log.Fatal("Error loading .env file")
  }

  s3Bucket := os.Getenv("S3_BUCKET")
  secretKey := os.Getenv("SECRET_KEY")

  // now do something with s3 or whatever
}

If you’re even lazier than that, you can just take advantage of the autoload package which will read in .env on import

`1`	`import _ "github.com/joho/godotenv/autoload"`

While .env in the project root is the default, you don’t have to be constrained, both examples below are 100% legit

1
2

godotenv.Load("somerandomfile")
godotenv.Load("filenumberone.env", "filenumbertwo.env")

If you want to be really fancy with your env file you can do comments and exports (below is a valid env file)

# I am a comment and that is OK
SOME_VAR=someval
FOO=BAR # comments at line end are OK too
export BAR=BAZ

Or finally you can do YAML(ish) style

1
2

FOO: bar
BAR: baz

as a final aside, if you don’t want godotenv munging your env you can just get a map back instead

var myEnv map[string]string
myEnv, err := godotenv.Read()

s3Bucket := myEnv["S3_BUCKET"]

… or from an io.Reader instead of a local file

1
2

reader := getRemoteFile()
myEnv, err := godotenv.Parse(reader)

… or from a string if you so desire

1
2

content := getRemoteFileContent()
myEnv, err := godotenv.Unmarshal(content)

Precedence & Conventions

Existing envs take precedence of envs that are loaded later.

The convention for managing multiple environments (i.e. development, test, production) is to create an env named {YOURAPP}_ENV and load envs in this order:

env := os.Getenv("FOO_ENV")
if "" == env {
  env = "development"
}

godotenv.Load(".env." + env + ".local")
if "test" != env {
  godotenv.Load(".env.local")
}
godotenv.Load(".env." + env)
godotenv.Load() // The Original .env

If you need to, you can also use godotenv.Overload() to defy this convention and overwrite existing envs instead of only supplanting them. Use with caution.

Command Mode

Assuming you’ve installed the command as above and you’ve got $GOPATH/bin in your $PATH

`1`	`godotenv -f /some/path/to/.env some_command with some args`

If you don’t specify -f it will fall back on the default of loading .env in PWD

By default, it won’t override existing environment variables; you can do that with the -o flag.

Writing Env Files

Godotenv can also write a map representing the environment to a correctly-formatted and escaped file

1
2

env, err := godotenv.Unmarshal("KEY=value")
err := godotenv.Write(env, "./.env")

… or to a string

1
2

env, err := godotenv.Unmarshal("KEY=value")
content, err := godotenv.Marshal(env)

Contributing

Contributions are welcome, but with some caveats.

This library has been declared feature complete (see #182 for background) and will not be accepting issues or pull requests adding new functionality or breaking the library API.

Contributions would be gladly accepted that:

bring this library’s parsing into closer compatibility with the mainline dotenv implementations, in particular Ruby’s dotenv and Node.js’ dotenv
keep the library up to date with the go ecosystem (ie CI bumps, documentation changes, changes in the core libraries)
bug fixes for use cases that pertain to the library’s purpose of easing development of codebases deployed into twelve factor environments

code changes without tests and references to peer dotenv implementations will not be accepted

Fork it
Create your feature branch (git checkout -b my-new-feature)
Commit your changes (git commit -am 'Added some feature')
Push to the branch (git push origin my-new-feature)
Create new Pull Request

Releases

Releases should follow Semver though the first couple of releases are v1 and v1.1.

Use annotated tags for all releases. Example git tag -a v1.2.1

Who?

The original library dotenv was written by Brandon Keepers, and this port was done by John Barton based off the tests/fixtures in the original library.

nvim-lspconfig

Thu, 17 Apr 2025 15:30:46 +0800

neovim/nvim-lspconfig

nvim-lspconfig

nvim-lspconfig is a “data only” repo, providing basic, default Nvim LSP client configurations for various LSP servers.

View all configs or :help lspconfig-all from Nvim.

Important ⚠️

These configs are best-effort and supported by the community (you). See contributions.
If you found a bug in Nvim LSP (:help lsp), report it to Neovim core.
- Do not report it here. Only configuration data lives here.
This repo only provides configurations. Its programmatic API is deprecated and must not be used externally.
- The “framework” parts (not the configs) of nvim-lspconfig will be upstreamed to Nvim core.

Install

Requires Nvim 0.10 above. Update Nvim and nvim-lspconfig before reporting an issue.

Install nvim-lspconfig using Vim’s “packages” feature:

`1`	`git clone https://github.com/neovim/nvim-lspconfig ~/.config/nvim/pack/nvim/start/nvim-lspconfig`

Or use a 3rd-party plugin manager (consult the documentation for your plugin manager).

Quickstart

Install a language server, e.g. pyright
1

npm i -g pyright
Add the language server setup to your init.lua.
- Nvim 0.11+ (see vim.lsp.config)
  1
  
  vim.lsp.enable('pyright')
- Nvim 0.10 (legacy, not supported)
  1
  
  require'lspconfig'.pyright.setup{}
Ensure your project/workspace contains a root marker as specified in :help lspconfig-all.
Open a code file in Nvim. LSP will attach and provide diagnostics.
1

nvim main.py
Run :checkhealth lsp to see the status or to troubleshoot.

Read :help lspconfig for details. Read :help lspconfig-all for the full list of server-specific details. For servers not on your $PATH (e.g., jdtls, elixirls), you must manually set the cmd parameter, see vim.lsp.config.

Configuration

Nvim sets some default options and mappings when a buffer attaches to LSP (see :help lsp-config). In particular:

'tagfunc'
- Enables “go to definition” capabilities using <C-]> and other tag commands.
'omnifunc'
- Enables (manual) omni mode completion with <C-X><C-O> in Insert mode. For autocompletion, an autocompletion plugin is required.
'formatexpr'
- Enables LSP formatting with gq.
K maps to vim.lsp.buf.hover() in Normal mode.
[d and ]d map to vim.diagnostic.goto_prev() and vim.diagnostic.goto_next(), respectively.
<C-W>d maps to vim.diagnostic.open_float().

Further customization can be achieved using the LspAttach autocommand event. The LspDetach autocommand event can be used to “cleanup” mappings if a buffer becomes detached from an LSP server. See :h LspAttach and :h LspDetach for details and examples. See :h lsp-buf for details on other LSP functions.

Extra settings can be specified for each LSP server:

Nvim 0.11+ (see vim.lsp.config)

vim.lsp.config('rust_analyzer', {
  -- Server-specific settings. See `:help lsp-quickstart`
  settings = {
    ['rust-analyzer'] = {},
  },
})

Nvim 0.10 (legacy, not supported)

local lspconfig = require('lspconfig')
lspconfig.rust_analyzer.setup {
  -- Server-specific settings. See `:help lspconfig-setup`
  settings = {
    ['rust-analyzer'] = {},
  },
}

vim.lsp.config

nvim-lspconfig includes configurations compatible with vim.lsp under lsp/, so servers can be enabled (auto-activated when a filetype is opened) with:

`1`	`vim.lsp.enable('pyright')`

and configured with:

1
2
3

vim.lsp.config('pyright', {
  cmd = { … },
})

which extends the configuration under lsp/. For further information see :help lsp-config.

[!WARNING]
Some servers are currently missing.

Troubleshooting

The most common reasons a language server does not start or attach are:

Language server is not installed. nvim-lspconfig does not install language servers for you. You should be able to run the cmd defined in each server’s Lua module from the command line and see that the language server starts. If the cmd is an executable name instead of an absolute path to the executable, ensure it is on your path.
Missing filetype plugins. Certain languages are not detecting by Vim/Nvim because they have not yet been added to the filetype detection system. Ensure :set ft? shows the filetype and not an empty value.
Not triggering root detection. Some language servers will only start if it is opened in a directory, or child directory, containing a file which signals the root of the project. Most of the time, this is a .git folder, but each server defines the root config in the lua file. See doc/configs.md or the source for the list of root directories.
You must pass capabilities for each setup {} if you want these to take effect.
Do not call setup {} twice for the same server. The second call to setup {} will overwrite the first.

Bug reports

If you found a bug with LSP functionality, report it to Neovim core.

Before reporting a bug, check your logs and the output of :LspInfo. Add the following to your init.vim to enable logging:

`1`	`vim.lsp.set_log_level("debug")`

Attempt to run the language server, and open the log with:

:LspLog

Most of the time, the reason for failure is present in the logs.

Commands

:LspInfo (alias to :checkhealth vim.lsp) shows the status of active and configured language servers.
:LspStart <config_name> Start the requested server name. Will only successfully start if the command detects a root directory matching the current config. Pass autostart = false to your .setup{} call for a language server if you would like to launch clients solely with this command. Defaults to all servers matching current buffer filetype.
:LspStop [<client_id_or_name> ...] Stops the given server(s). Defaults to stopping all servers active on the current buffer. To force stop add ++force
:LspRestart [<client_id_or_name> ...] Restarts the given client(s), and attempts to reattach to all previously attached buffers.

Contributions

If a language server is missing from configs.md, contributing a new configuration for it helps others, especially if the server requires special setup. Follow these steps:

Read CONTRIBUTING.md.
Create a new file at lsp/SERVER_NAME.lua.
- Copy an existing config to get started. Most configs are simple. For an extensive example see texlab.lua.
Ask questions on GitHub Discussions or in the Neovim Matrix room.

Release process

To publish a release:

Create and push a new tag.
After pushing the tag, a GitHub action will automatically package the plugin and publish the release to LuaRocks.

License

nvim-lspconfig is licensed under the terms of the Apache 2.0 license.

See LICENSE.md

caddy

Fri, 11 Apr 2025 15:27:14 +0800

caddyserver/caddy

a project

Every site on HTTPS

Caddy is an extensible server platform that uses TLS by default.

Releases · Documentation · Get Help

Powered by

Features

Easy configuration with the Caddyfile
Powerful configuration with its native JSON config
Dynamic configuration with the JSON API
Config adapters if you don’t like JSON
Automatic HTTPS by default
- ZeroSSL and Let’s Encrypt for public names
- Fully-managed local CA for internal names & IPs
- Can coordinate with other Caddy instances in a cluster
- Multi-issuer fallback
- Encrypted ClientHello (ECH) support
Stays up when other servers go down due to TLS/OCSP/certificate-related issues
Production-ready after serving trillions of requests and managing millions of TLS certificates
Scales to hundreds of thousands of sites as proven in production
HTTP/1.1, HTTP/2, and HTTP/3 all supported by default
Highly extensible modular architecture lets Caddy do anything without bloat
Runs anywhere with no external dependencies (not even libc)
Written in Go, a language with higher memory safety guarantees than other servers
Actually fun to use
So much more to discover

Install

The simplest, cross-platform way to get started is to download Caddy from GitHub Releases and place the executable file in your PATH.

See our online documentation for other install instructions.

Build from source

Requirements:

Go 1.24.0 or newer

For development

Note: These steps will not embed proper version information. For that, please follow the instructions in the next section.

1
2
3

$ git clone "https://github.com/caddyserver/caddy.git"
$ cd caddy/cmd/caddy/
$ go build

When you run Caddy, it may try to bind to low ports unless otherwise specified in your config. If your OS requires elevated privileges for this, you will need to give your new binary permission to do so. On Linux, this can be done easily with: sudo setcap cap_net_bind_service=+ep ./caddy

If you prefer to use go run which only creates temporary binaries, you can still do this with the included setcap.sh like so:

`1`	`$ go run -exec ./setcap.sh main.go`

If you don’t want to type your password for setcap, use sudo visudo to edit your sudoers file and allow your user account to run that command without a password, for example:

`1`	`username ALL=(ALL:ALL) NOPASSWD: /usr/sbin/setcap`

replacing username with your actual username. Please be careful and only do this if you know what you are doing! We are only qualified to document how to use Caddy, not Go tooling or your computer, and we are providing these instructions for convenience only; please learn how to use your own computer at your own risk and make any needful adjustments.

With version information and/or plugins

Using our builder tool, xcaddy…

`1`	`$ xcaddy build`

…the following steps are automated:

Create a new folder: mkdir caddy
Change into it: cd caddy
Copy Caddy’s main.go into the empty folder. Add imports for any custom plugins you want to add.
Initialize a Go module: go mod init caddy
(Optional) Pin Caddy version: go get github.com/caddyserver/caddy/v2@version replacing version with a git tag, commit, or branch name.
(Optional) Add plugins by adding their import: _ "import/path/here"
Compile: go build -tags=nobadger,nomysql,nopgx

Quick start

The Caddy website has documentation that includes tutorials, quick-start guides, reference, and more.

We recommend that all users – regardless of experience level – do our Getting Started guide to become familiar with using Caddy.

If you’ve only got a minute, the website has several quick-start tutorials to choose from! However, after finishing a quick-start tutorial, please read more documentation to understand how the software works. 🙂

Overview

Caddy is most often used as an HTTPS server, but it is suitable for any long-running Go program. First and foremost, it is a platform to run Go applications. Caddy “apps” are just Go programs that are implemented as Caddy modules. Two apps – tls and http – ship standard with Caddy.

Caddy apps instantly benefit from automated documentation, graceful on-line config changes via API, and unification with other Caddy apps.

Although JSON is Caddy’s native config language, Caddy can accept input from config adapters which can essentially convert any config format of your choice into JSON: Caddyfile, JSON 5, YAML, TOML, NGINX config, and more.

The primary way to configure Caddy is through its API, but if you prefer config files, the command-line interface supports those too.

Caddy exposes an unprecedented level of control compared to any web server in existence. In Caddy, you are usually setting the actual values of the initialized types in memory that power everything from your HTTP handlers and TLS handshakes to your storage medium. Caddy is also ridiculously extensible, with a powerful plugin system that makes vast improvements over other web servers.

To wield the power of this design, you need to know how the config document is structured. Please see our documentation site for details about Caddy’s config structure.

Nearly all of Caddy’s configuration is contained in a single config document, rather than being scattered across CLI flags and env variables and a configuration file as with other web servers. This makes managing your server config more straightforward and reduces hidden variables/factors.

Full documentation

Our website has complete documentation:

https://caddyserver.com/docs/

The docs are also open source. You can contribute to them here: https://github.com/caddyserver/website

Getting help

We advise companies using Caddy to secure a support contract through Ardan Labs before help is needed.
A sponsorship goes a long way! We can offer private help to sponsors. If Caddy is benefitting your company, please consider a sponsorship. This not only helps fund full-time work to ensure the longevity of the project, it provides your company the resources, support, and discounts you need; along with being a great look for your company to your customers and potential customers!
Individuals can exchange help for free on our community forum at https://caddy.community. Remember that people give help out of their spare time and good will. The best way to get help is to give it first!

Please use our issue tracker only for bug reports and feature requests, i.e. actionable development items (support questions will usually be referred to the forums).

About

Matthew Holt began developing Caddy in 2014 while studying computer science at Brigham Young University. (The name “Caddy” was chosen because this software helps with the tedious, mundane tasks of serving the Web, and is also a single place for multiple things to be organized together.) It soon became the first web server to use HTTPS automatically and by default, and now has hundreds of contributors and has served trillions of HTTPS requests.

The name “Caddy” is trademarked. The name of the software is “Caddy”, not “Caddy Server” or “CaddyServer”. Please call it “Caddy” or, if you wish to clarify, “the Caddy web server”. Caddy is a registered trademark of Stack Holdings GmbH.

Project on X: @caddyserver
Author on X: @mholt6

Caddy is a project of ZeroSSL, a Stack Holdings company.

Debian package repository hosting is graciously provided by Cloudsmith. Cloudsmith is the only fully hosted, cloud-native, universal package management solution, that enables your organization to create, store and share packages in any format, to any place, with total confidence.

terraform-provider-aws

Sun, 06 Apr 2025 15:26:34 +0800

hashicorp/terraform-provider-aws

Terraform AWS Provider

The AWS Provider enables Terraform to manage AWS resources.

Please note: We take Terraform’s security and our users’ trust very seriously. If you believe you have found a security issue in the Terraform AWS Provider, please responsibly disclose it by contacting us at security@hashicorp.com.

_{Vincent Koc}	_{Brian Curliss}	_{Anand Chowdhary}	_{Zach Biles}	_{Ulises Gascón}	_InDieTasten
_Araguaci	_{Brian McGonagill}	_Vlad	_HeliXZz	_{Göksel Yeşiller}	_Undefined
_{HamburgerJung}	_Frankdez93	_{Hudsonrock-partnerships}	_{Gl0bal01 💖 龴ↀ◡ↀ龴}

Configuration on Producthunt daily

eslint

eslint/eslint

ESLint

Table of Contents

Installation and Usage

pnpm Installation

Configuration

Version Support

Code of Conduct

Filing Issues

Frequently Asked Questions

Does ESLint support JSX?

Does Prettier replace ESLint?

What ECMAScript versions does ESLint support?

What about experimental features?

Which Node.js versions does ESLint support?

Where to ask for help?

Why doesn’t ESLint lock dependency versions?

Releases

Security Policy

Semantic Versioning Policy

License

Team

Technical Steering Committee (TSC)

Reviewers

Committers

Website Team

Sponsors

Platinum Sponsors

Gold Sponsors

Silver Sponsors

Bronze Sponsors

Technology Sponsors

youtube-dl

ytdl-org/youtube-dl

INSTALLATION

DESCRIPTION

OPTIONS

Network Options:

Geo Restriction:

Video Selection:

Download Options:

Filesystem Options:

Thumbnail Options:

Verbosity / Simulation Options:

Workarounds:

Video Format Options:

Subtitle Options:

Authentication Options:

Adobe Pass Options:

Post-processing Options:

CONFIGURATION

Authentication with .netrc file

OUTPUT TEMPLATE

Output template and Windows batch files

Output template examples

FORMAT SELECTION

Format selection examples

VIDEO SELECTION

FAQ

How do I update youtube-dl?

youtube-dl is extremely slow to start on Windows

I’m getting an error Unable to extract OpenGraph title on YouTube playlists

I’m getting an error when trying to use output template: error: using output template conflicts with using title, video ID or auto number

Do I always have to pass -citw?

Can you please put the -b option back?

I get HTTP error 402 when trying to download a video. What’s this?

Do I need any other programs?

I have downloaded a video but how can I play it?

I extracted a video URL with -g, but it does not play on another machine / in my web browser.

ERROR: no fmt_url_map or conn information found in video info

ERROR: unable to download video

Video URL contains an ampersand and I’m getting some strange output [1] 2839 or 'v' is not recognized as an internal or external command

ExtractorError: Could not find JS function u’OF'

HTTP Error 429: Too Many Requests or 402: Payment Required

SyntaxError: Non-ASCII character

What is this binary file? Where has the code gone?

The exe throws an error due to missing MSVCR100.dll

On Windows, how should I set up ffmpeg and youtube-dl? Where should I put the exe files?

Authentication with `.netrc` file

I’m getting an error `Unable to extract OpenGraph title` on YouTube playlists

I’m getting an error when trying to use output template: `error: using output template conflicts with using title, video ID or auto number`

Do I always have to pass `-citw`?

Can you please put the `-b` option back?

I extracted a video URL with `-g`, but it does not play on another machine / in my web browser.

Video URL contains an ampersand and I’m getting some strange output `[1] 2839` or `'v' is not recognized as an internal or external command`

The exe throws an error due to missing `MSVCR100.dll`

How do I download a video starting with a `-`?

Should I add `--hls-prefer-native` into my config?