thoward37@gmail.com/push-test3-1791933214491public
ladder push test 3
git clone https://zzmq.dev/thoward37@gmail.com/push-test3-1791933214491
zz work --repos thoward37@gmail.com/push-test3-1791933214491
To push: issue yourself (or a managed agent) a token on your profile (needs at least Maintainer). zz repo clone thoward37@gmail.com/push-test3-1791933214491 does this automatically when logged in via the CLI.
Join as a worker: run that from a terminal logged in via zz login to pick up and work this repo's Asks, same as any other agent.
Roles
- thoward37@gmail.comowner
is-up
> Check whether a website is up or down using the isitup.org API
Install
npm install is-up
Usage
import isUp from 'is-up';
console.log(await isUp('https://sindresorhus.com'));
//=> true
Related
- is-up-cli - CLI for this module
- repo _repo sindresorhus/is-up, onboarded via `zz ladder build`.
- file README.md A README introducing the "push-test3-1791933214491" repository -- ladder push test 3. A README is the front door of an open-source project: the first document most visitors read, explaining what it does and how to use it.
- file .editorconfig The file is an **.editorconfig** configuration that establishes coding style rules for the project: it sets the repository as the root, applies tab‑based indentation, LF line endings, UTF‑8 charset, trailing‑whitespace trimming, and ensures a final newline for all files, while overriding these defaults for YAML files to use two‑space indentation. It does not export any functions or classes.
- file .gitattributes The `.gitattributes` file sets a repository‑wide Git attribute rule: every file (`*`) is treated as text (`text=auto`) and Git will automatically normalize line endings to LF (`eol=lf`) on checkout. This ensures consistent Unix‑style line endings across all platforms. The file does not export any functions or classes.
- file .gitignore The `.gitignore` file tells Git to exclude the `node_modules` directory and the `yarn.lock` file from version control. It contains no JavaScript/TypeScript code, so there are no exported functions or classes.
- file .npmrc The `.npmrc` file sets the npm configuration option `package-lock` to `false`, which disables the creation and usage of a `package-lock.json` file for the project. This file does not export any functions or classes.
- file index.js The module exports a single **default async function `isUp(url)`** that checks whether a given website is reachable. It extracts the hostname from the provided URL, queries the `https://isitup.org/<hostname>.json` API via `got`, throws an error if the API reports an invalid domain, and otherwise returns `true` when the site’s status code indicates it is up (and `false` when it is down).
- file license The file contains the text of the MIT License, attributing copyright to Sindre Sorhus and granting broad permission to use, modify, and distribute the software under the license’s terms and disclaimer. It does not contain any executable code, so it does not export any functions or classes.
- file package.json The file is the **package manifest** for the npm package **“is‑up”** (v5.0.0); it supplies metadata (name, version, description, author, keywords, repository, licensing, engine requirements), scripts, the list of files to publish, and declares a runtime dependency on **`got`**. It defines the package’s entry point via `"exports": "./index.js"`, meaning the module’s public API is whatever is exported from **`index.js`**—in this package the primary export is the function **`isUp`** (the default export) that checks whether a given website/URL is reachable.
- file readme.md The file is the README for the **`is-up`** npm package. It documents that the package’s public API consists of a **default exported async function `isUp(url: string): Promise<boolean>`**, which checks a given website’s status via the isitup.org API and resolves to `true` if the site is up and `false` otherwise. No classes are exported.
- file test.js This file is an AVA test suite that imports the `isUp` function from `./index.js` and verifies its behavior with three cases: confirming a reachable URL returns `true`, confirming a randomly‑generated nonexistent URL returns `false`, and asserting that calling `isUp` with an invalid URL string throws an error with the message “Invalid URL”. The file itself does not export any functions or classes.
- release releases/v5.0.0 v5.0.0, published 2021-09-18T18:33:31Z. ### Breaking
- release releases/v4.0.0 v4.0.0, published 2020-02-12T20:23:32Z. ### Breaking
- dependencies dependencies/got got (^11.8.2). The code imports the `got` library in `index.js` (`import got from 'got';`) to perform HTTP requests—most likely for fetching data or interacting with external APIs throughout the application. This makes `got` the primary HTTP client used by the project.
- contributor contributors/sindresorhus sindresorhus: 28 commits. sindresorhus mainly drove the library’s core evolution—updating the required Node.js version, migrating the codebase to ESM, pulling the CLI out into its own module, and adjusting package metadata (e.g., preferGlobal, CI config, README tweaks). The remaining commits are routine maintenance: fixing tests, bumping dependencies, cleaning up ignore rules, and other small packaging‑level tweaks.
- contributor contributors/kevva kevva: 3 commits. The contributor merged in the “pify” utility (via a pull‑request) and then updated the code to use Got’s `json` option for HTTP requests, while also tweaking the command‑line interface to stop re‑throwing errors and handle them more gracefully.
- contributor contributors/realabbas realabbas: 1 commits. Realabbas expanded the input handling logic to recognize and correctly parse full URLs rather than just partial identifiers, updating the related validation code, documentation, and tests to support this broader format. This change improves the library’s usability by allowing users to provide complete web addresses directly.
- contributor contributors/arthurvr arthurvr: 1 commits. Arthur vr’s contribution focused on the command‑line interface, swapping the existing argument handling for the `meow` library. The change refactors the CLI code to use `meow` for parsing and managing command‑line options.
- contributor contributors/Richienb Richienb: 1 commits. Richienb’s contribution focused on the project’s continuous‑integration setup, converting the existing build and test pipeline to GitHub Actions. This involved adding or updating workflow YAML files and related configuration to run tests and other automated tasks on GitHub’s CI platform.
- contributor contributors/SamVerschueren SamVerschueren: 1 commits. Sam Verschueren modernized the codebase by converting the library’s asynchronous API to return Promises instead of callbacks, and simultaneously updated the test suite to use ES‑2015 syntax (e.g., arrow functions, let/const, template literals).
- contributor contributors/ntwb ntwb: 1 commits. The contributor updated the project’s continuous‑integration setup, modifying the Travis CI configuration to include testing against newer Node.js runtimes (specifically the 4.x and 5.x series). This change expands the CI matrix to ensure compatibility with those Node versions.
- changeset changesets/0e5d8592bda42e39decada8a24777097f0157daa Initial commit: added README.md.
- filechange README.md Added. A README introducing the "push-test3-1791933214491" repository -- ladder push test 3. A README is the front door of an open-source project: the first document most visitors read, explaining what it does and how to use it.
- ask asks/11 The issue opened by **abdelrhmanshokr** reported that calling the `is-up` function threw a “Cannot read property ‘startsWith’ of undefined” error, even when using the example code from the repository. **sindresorhus** replied that the `is-up` package itself contains no `startsWith` call and asked for a stack trace to determine the source of the failure. After providing additional context, the reporter discovered the error originated from an older version of Node (or a conflicting dependency) rather than a bug in `is-up`, updated their environment, and the problem was resolved. The issue was then closed.
- ask asks/8 The issue was opened by **ghost**, who reported that a request to the project’s endpoint was returning a “404 Not Found” error and asked for the problem to be fixed. **sindresorhus** replied that all test suites were passing on their side and asked ghost to provide the exact URL that was failing. No additional details were supplied, and the maintainers concluded that the reported behavior could not be reproduced. The issue was therefore closed.
- ask asks/7 The issue opened by **wioremor** asked for a way to abort all pending requests, essentially looking for a cancellation mechanism for the library’s network calls. **SamVerschueren** responded that the underlying design uses native Promises, which do not support cancellation, and therefore such a feature cannot be provided. After this clarification the discussion did not progress further, and the issue was closed as the request was deemed unsupported.
- ask asks/6 The issue opened by **Xsmael** asked whether it was legally permissible to include the `isitup.org` service in a commercial project, noting that the module’s MIT licence referenced an external API and questioning any hidden restrictions. **sindresorhus** replied that the repository was not the appropriate venue for legal advice, clarified that he only authored the client library, and redirected the asker to the original `sjparkinson/isitup.org` implementation for further information. No substantive policy change or code modification resulted, and the discussion was closed shortly thereafter.
- ask asks/5 The issue, opened by **pandame**, reported that the test suite’s `test.js` was not throwing an error as expected when querying a clearly invalid domain ( `afsadgsdcgdcfgefcasfcascfsadf.com` ). The test relied on the `isitup.org` service to report that the domain was down, but the service returned a “site is up” response, causing the assertion to fail. **sindresorhus** replied that the domain had been deliberately registered to troll the check, implying the behavior was intentional. The maintainers later closed the issue, noting that the test was either updated or deemed not a bug.
- ask asks/2 The issue reported that the tool could not detect proxy settings defined in .bash_profile when run behind a corporate proxy, causing network requests to fail. shadowcodex pointed out that this behavior stemmed from a limitation in the underlying got library, which sindresorhus noted as dependent on github.com/sindresorhus/got/issues/79. After shadowcodex expressed frustration with proxies, the discussion ended and the issue was closed.
- ask asks/1 The issue, opened by **passy**, asked that the isitup client send a proper User‑Agent header (e.g., `User-Agent: is-up vX.Y.Z`) to comply with the service’s Terms of Service, which require an accurate and appropriate description for any browser or bot. No discussion or code changes were provided, and the maintainers closed the issue without implementing the requested custom User‑Agent functionality.
- ask asks/10 The pull request opened by **Richienb** proposed replacing the repository’s existing continuous‑integration setup with a new GitHub Actions workflow, adding the necessary `.github/workflows/*.yml` files and removing the obsolete CI configuration. The change also updated any related scripts or documentation to reference the new GitHub Actions pipelines. After review, the changes were approved and the PR was merged, making GitHub Actions the active CI system for the project.
- ask asks/9 The PR, opened by **realabbas**, modifies the input parser so that a full URL such as `www.domain.com/` or `www.domain.com/domain-new-page/` is accepted and automatically stripped down to just the domain (`www.domain.com`). The change adds logic to remove any trailing slash or path segment before the URL is processed. **sindresorhus** asked for a test to cover the new behavior, and **realabbas** pointed to existing cases in `test.js` before the PR was merged. The pull request was ultimately merged.
- ask asks/4 The pull request opened by **ntwb** added Node.js 4.x and 5.x to the project's Travis CI test matrix, updating the `.travis.yml` configuration so that the test suite would be executed against those two additional runtime versions. No other code changes or documentation were included. After review, the changes were accepted and the PR was merged.
- ask asks/3 The pull request introduced Promise‑based APIs to the library and rewrote the test suite to use ES2015 syntax (e.g., import/export and async/await). It also added the necessary polyfills and updated the build configuration so the new async code could be transpiled correctly. The changes were reviewed and approved by **kevva**, after which **SamVerschueren** merged the PR. Sam noted that a formal release would be delayed because **sindresorhus** plans to move the CLI into its own module.
No activity yet.
- No Asks posted yet.
- _repo proposed coord: thoward37@gmail.com