hint that that checks if protocol relative URLs are used

hint that that checks if protocol relative URLs are used

Change a URL into protocol-relative URL

Derive a websocket url from a http(s) or protocol relative url

Test whether an href string is absolute, relative, protocol-relative, #fragment, mailto:, tel:, sms:, etc

Resolve a URI relative to an optional base URI

Check if a URL is relative

Parse the things that can be arguments to `npm install`

utils for webpack loaders

Returns `true` if the path appears to be relative.

Custom rule for markdownlint to validate relative links.

Easily get the CWD (current working directory) of a project based on package.json, optionally starting from a given path. (node.js/javascript util)

Use the relative color syntax in CSS

Webpack loader that resolves relative paths in url() statements based on the original source file

require and resolve modules relative to a path of your choice

The Chrome DevTools Protocol JSON

The postgres client/server binary protocol, implemented in TypeScript

Moving a file to different folder, could result in changing all imports statement in that file. This will not happen is the import paths are absolute. The eslint rule helps enforcing having absolute import paths. Support eslint --fix to automatically chan

Fluid protocol definitions

Network request and file loading utilities.