NOTE: Set include_hash to false, to disable including .hash as a postfix

import {format_url} from "svelte-commons/lib/util/shared";

const url = new URL("https://my.domain/path/to/application?x=2#header-id");

// Here, we're formating it with all three URL components
const format_hash = format_url(url);
console.log(format_hash); // logs: `/path/to/application?x=2#header-id`

// Optionally though. you can disable including the `.hash` component
const format_no_hash = format_url(url, false);
console.log(format_no_hash); // logs: `/path/to/application?x=2`

RULES:

• URLs with a protocol, e.g. https://my.domain/index.html, are considered external
• URLs that are protocol independent, e.g. //cdn-provider.com/some_stylesheet.css are considered external

import {is_internal_href} from "svelte-commons/lib/util/shared";

const href = "/path/to/application?x=1";
const url = "https://google.com";

console.log(is_internal_href(href)); // logs: `true`
console.log(is_internal_href(url)); // logs: `false`

RULES:

• Protocols, domains, ports are ignored for both URLs
• Hash string, and query parameters are ignored for a URL
• b URL's hash string and query parameters will be in the resulting URL
• The resulting URL pathname are normalized after being joined

import {join} from "svelte-commons/lib/util/shared";

// We're going to join `a` and `b` together, however the protocol and domain will be
// dropped from `a`, along with the query parameters
const a = "https://my.domain/path/to/application?x=1";
const b = "/sub-page?x=2";

const joined = join(a, b);

console.log(joined); // logs: `/path/to/application/sub-page?x=2`

import {make_router} from "svelte-commons/lib/util/shared";

import ComponentOne from "...";
import ComponentTwo from "...";

// Below, we're defining our route mappings, along with their assigned Svelte Components
const routes = {
    "/": ComponentOne,
    "/items/:id": ComponentTwo
};

// Now we feed our mappings into the factory function, which gives us a matcher function
const router = make_router(routes);

// First, let's try matching our first route
console.log(router("/")); // logs: `[{}, ComponentOne]`

// Next, let's try matching our second route
console.log(router("/items/blue-jeans")); // logs: `[{id: "blue-jeans"}, ComponentTwo]`

// Finally, we can see that if we pass an invalid route, `null` is returned. Which should
// be treated the same as a "404"
console.log(router("/some/invalid/route")); // logs: `null`

RULES:

• Backward slashes \ are converted to forward slashes /
• Consecutive forward slashes / are reduced to a single slash
• Forward slashes / are trimmed from the beginning and end of the string
• Up directory directives ../ are evaluated, removing it and the parent directory if exists
  • NOTE: Parent directories are currently matched to alphanumeric chatacters, periods, spaces, tildes, underscores and dashes
  • REGEX: [\w_.-\s~]+

import {normalize_pathname} from "svelte-commons/lib/util/shared";

// Below we have a pathname with Windows separators `\`, consecutive separators `//`, and up directory directives `../`
const malformed_pathname = "\\path/to//application/src/../assets"; // NOTE: `\\` renders as `\`, since `\` normally escapes in strings

const normalized = normalize_pathname(malformed_pathname);

console.log(normalized); // logs: `/path/to/application/assets`

import {parse_query} from "svelte-commons/lib/util/shared";

const query_string = "?sorting=ASCENDING&remove-inactive";

const mapping = parse_query(query_string);

console.log(mapping); logs: `{"sorting": "ASCENDING", "remove-inactive": true}`