open-index/open-npm huggingface dataset:
npm package: @oresoftware/ncf
Description: Run 'node -c' quickly on multiple files in a project
Author: Olegzandr VD
Latest version: 0.0.1021


# @oresoftware/ncf (Node Check Fast)

[![Version](https://img.shields.io/npm/v/@oresoftware/ncf.svg?colorB=green)](https://www.npmjs.com/package/@oresoftware/ncf)


>
> Running `node -c` for all the files in your project can take a minute.
> This project does what it says - use the node.js interface, or the command line interface.
>

### Installation

>
> Local (for programmatic usage)
> ``` npm install -D '@oresoftware/ncf' ```
>
> Global (for command line tools, this makes more sense usually)
> ``` npm install -g '@oresoftware/ncf' ```
>

### In the beginning:

```bash
find -path "*.js" -type f -not -path "**/node_modules/**" | ncf --stdin
```

Yeah don't do that. We can use sane defaults instead.
Instead do this:

```bash
 ncf -c 9    # by default we search with the above settings
```

## Programmatic usage with Node.js:

```js

import ncf from '@oresoftware/ncf';  
// likewise: const {ncf} = require('@oresoftware/ncf');


ncf({
  
  root: process.cwd(),   // required: an absolute path representing where to start searching for .js files
  paths: [],             // optional: paths to match
  notPaths: [],          // optional: paths not to match
  concurrency: 8,        // optional: number of processes to run at a time
  maxDepth: 10,          // optional: max number of directories to drill into it
  verbosity: 1
  
}, function(err, results){
    
  // if err is present, a file failed the "node -c" check.
  // results will tell you specifically which files failed
  // if results is an empty array, no files were checked/matched.
  
})

```

Default values used for both command line and JS usage:

```
  root: process.cwd(),   
  paths: ['*.js'],             
  notPaths: ['**/node_modules/**'],        
  concurrency: os.cpus().length || 6,
  maxDepth: 12,          
  verbosity: 2

```


## Command line interface:

```bash
ncf --dir . --not-paths=**/test/** --not-paths=**/node_modules/** --verbosity 3 --concurrency=8
```

the terse version of the above is:

```bash
ncf -d . --np=**/test/** --np=**/node_modules/** --v 3 -c 8
```
npm package: @orest22/core
Description: ## Commands
Author: Orest Hazda
Latest version: 1.4.10-alpha.0

# Simple lib

## Commands

To run the package, use:

```bash
npm start # or yarn start
```

This builds to `/dist` and runs the project in watch mode so any edits you save inside `src` causes a rebuild to `/dist`.

To do a one-off build, use `npm run build` or `yarn build`.

To run tests, use `npm test` or `yarn test`.

## Configuration

Code quality is set up for you with `prettier`, `husky`, and `lint-staged`. Adjust the respective fields in `package.json` accordingly.

### Jest

Jest tests are set up to run with `npm test` or `yarn test`.

### Bundle Analysis

[`size-limit`](https://github.com/ai/size-limit) is set up to calculate the real cost of your library with `npm run size` and visualize the bundle with `npm run analyze`.

### Rollup

TSDX uses [Rollup](https://rollupjs.org) as a bundler and generates multiple rollup configs for various module formats and build settings. See [Optimizations](#optimizations) for details.

### TypeScript

`tsconfig.json` is set up to interpret `dom` and `esnext` types, as well as `react` for `jsx`. Adjust according to your needs.

## Optimizations

Please see the main `tsdx` [optimizations docs](https://github.com/palmerhq/tsdx#optimizations). In particular, know that you can take advantage of development-only optimizations:

```js
// ./types/index.d.ts
declare var __DEV__: boolean;

// inside your code...
if (__DEV__) {
  console.log('foo');
}
```

You can also choose to install and use [invariant](https://github.com/palmerhq/tsdx#invariant) and [warning](https://github.com/palmerhq/tsdx#warning) functions.

## Module Formats

CJS, ESModules, and UMD module formats are supported.

The appropriate paths are configured in `package.json` and `dist/index.js` accordingly. Please report if any issues are found.
npm package: @orestbida/link-prefetcher
Description: Eager link prefetcher
Author: Orest Bida
Latest version: 0.4.1

# link-prefetcher

![GitHub](https://img.shields.io/github/license/orestbida/link-prefetcher?label=License)
![GitHub file size in bytes](https://img.shields.io/github/size/orestbida/link-prefetcher/dist/index.esm.js?label=Size)
[![Build](https://github.com/orestbida/link-prefetcher/actions/workflows/build.yml/badge.svg)](https://github.com/orestbida/link-prefetcher/actions/workflows/build.yml)

A tiny link prefetcher (yet another one in the sea of prefetching tools). Uses `fetch`/`xhr` to prefetch links rather than the `link` tag.

### `prefetchHover()`
Start prefetching as soon as possible. Abort if the cursor leaves the anchor tag before the prefetch process is done.

### `prefetchVisible()`
Immediately prefetch all visible links (⚠️ use with caution, can eat up a lot of bandwidth).

## Installation

```bash
npm i @orestbida/link-prefetcher
```

## Usage
```javascript
import { prefetchHover } from 'link-prefetcher';

prefetchHover();
```

or

```html
<script defer src="dist/index.umd.js"></script>
<script>
    window.addEventListener('load', () => {
        LinkPrefetcher.prefetchHover()
    });
</script>
```

## License
Distributed under the MIT License. See [LICENSE](./LICENSE) for more information.