immosquare-cleaner 0.1.43 → 0.1.44

data/node_modules/jscodeshift/website/src/content/docs/index.mdx

@@ -0,0 +1,15 @@
+---
+title: Docs
+description: Get started with building and running jscodeshift codemods.
+template: doc
+hero:
+  tagline: Get started with building and running jscodeshift codemods.
+  actions:
+    - text: Get started
+      link: /overview/introduction/
+      icon: right-arrow
+      variant: primary
+    - text: GitHub
+      link: https://github.com/facebook/jscodeshift
+      icon: external
+---

data/node_modules/jscodeshift/website/src/content/docs/overview/introduction.mdx

@@ -0,0 +1,45 @@
+---
+title: Introduction
+---
+
+import { Steps, LinkCard, Card, CardGrid } from '@astrojs/starlight/components';
+
+`jscodeshift` is a toolkit for building and running codemods over multiple JavaScript or TypeScript files. It provides:
+
+- A runner, which executes the provided transform for each file passed to it. It also outputs a summary of how many files have **not** been transformed.
+- A wrapper around [recast](https://github.com/benjamn/recast), providing a different API.  Recast is an AST-to-AST transform tool and also tries to preserve the style of original code
+as much as possible.
+
+## How does jscodeshift work?
+
+<Steps>
+  1. **Parsing Code into AST**
+
+      First, jscodeshift takes your JavaScript code and converts it into an Abstract Syntax Tree (AST). An AST is a tree representation of your code where each node represents a different part of the code, like variables, functions, and expressions.
+  
+  2. **Transforming the AST**
+      
+      Using jscodeshift, you can navigate through the AST and apply transformations. For example, you can find all instances of a certain function and rename it or change its parameters.
+  
+  3. **Generating Code from AST**
+      
+      After transforming the AST, jscodeshift converts it back into JavaScript code. The result is your original code with the specified changes applied.
+</Steps>
+
+## Installation
+
+Get jscodeshift from [npm](https://www.npmjs.com/package/jscodeshift):
+
+```
+$ npm install -g jscodeshift
+```
+
+This will install the runner as `jscodeshift`.
+
+
+## Getting started
+
+<CardGrid>
+  <LinkCard title="Build jscodeshift codemods" href="/build/api-reference/" />
+  <LinkCard title="Run jscodeshift codemods" href="/run/cli/" />
+</CardGrid>

data/node_modules/jscodeshift/website/src/content/docs/run/cli.mdx

@@ -0,0 +1,161 @@
+---
+title: CLI Reference
+---
+
+import { Aside } from '@astrojs/starlight/components';
+
+The `jscodeshift` command-line interface (CLI) allows you to run jscodeshift codemods using a terminal or through an automated system.
+
+## Usage
+
+You can use the `jscodeshift` command to run codemods in 4 different ways
+
+**Option 1: Run from `transform.js` file in current working directory:**
+
+```bash
+jscodeshift [OPTION]... PATH...
+```
+
+This automatically looks for a `transform.js` file in the current working directory and attempts to run the transform over the specified `PATH`.
+
+**Option 2: Run from specific transform file:**
+
+```bash
+jscodeshift [OPTION]... -t TRANSFORM_PATH PATH...
+```
+
+This allows you to specify a path to a transform file and run the transform over the specified `PATH`.
+
+**Option 3: Run from specific transform URL:**
+
+```bash
+jscodeshift [OPTION]... -t URL PATH...
+```
+
+This allows you to specify a URL to a transform file and run the transform over the specified `PATH`.
+
+**Option 4: Apply transform to standard input:**
+
+```bash
+jscodeshift [OPTION]... --stdin < file_list.txt
+```
+
+Using `--stdin` allows you to run the transform over every line of standard input provided in `file_list.txt`.
+
+
+## Options
+
+### `--(no-)babel`
+
+`default: true`
+
+This allows you to apply babeljs to the transform file.
+
+### `--cpus=N`
+
+`aliases: -c`
+
+`default: max(all - 1, 1)`
+
+This allows you to start at most N child processes to process source files.
+
+### `--(no-)dry`
+
+`aliases: -d`
+
+`default: false`
+
+This allows you to dry run the codemod. Dry running is useful when you need to see how a codemod will affect your project without making changes to your files.
+
+### `--extensions=[EXT]`
+
+`default: js`
+
+Allows you to specify the extension of the files to be transformed.
+
+
+### `--help`
+
+`aliases: -h`
+
+Allows you to print the help menu.
+
+### `--ignore-config=[FILE] ...`
+
+Allows you to ignore files if they match patterns sourced from a configuration file (e.g. a .gitignore).
+
+### `--ignore-pattern=[GLOB] ...`
+
+Allows you to ignore files that match a provided glob expression.
+
+### `--(no-)gitignore`
+
+`default: false`
+
+Allows you to add entries to the current directory's .gitignore file.
+
+### `--parser=[PARSER]`
+
+`default: babel`
+
+`available options: babel|babylon|flow|ts|tsx`
+
+Allows you to specify the parser to use for parsing the source files.
+
+### `--parser-config=[FILE]`
+
+Allows you to specify path to a JSON file containing a custom parser configuration for flow or babylon.
+
+### `--(no-)print`
+
+`aliases: -p`
+
+`default: false`
+
+Allows you to print transformed files to stdout, useful for development.
+
+### `--(no-)run-in-band`
+
+`default: false`
+
+Allows `jscodeshift` to run serially in the current process.
+
+### `--(no-)silent`
+
+`aliases: -s`
+
+`default: false`
+
+Allows you to run silently (prevent writing to stdout or stderr).
+
+### `--(no-)stdin`
+
+`default: false`
+
+Allows you to run the transform over every line of standard input.
+
+### `--transform=[FILE]`
+
+`aliases: -t`
+
+`default: ./transform.js`
+
+Allows you to specify a path to the transform file. Can be either a local path or url.
+
+### `--verbose=[MODE]`
+
+`aliases: -v`
+
+`available options: 0|1|2`
+
+`default: 0`
+
+Allows you to show more information about the transform process.
+
+### `--version`
+
+Allows you to print your `jscodeshift` version.
+
+### `--fail-on-error`
+
+Allows you to return a 1 exit code when errors were found during execution of codemods.

data/node_modules/jscodeshift/website/src/env.d.ts

@@ -0,0 +1,2 @@
+/// <reference path="../.astro/types.d.ts" />
+/// <reference types="astro/client" />

data/node_modules/jscodeshift/website/tsconfig.json

@@ -0,0 +1,3 @@
+{
+  "extends": "astro/tsconfigs/strict"
+}

data/node_modules/npm-check-updates/README.md

@@ -5,27 +5,27 @@
 
 **npm-check-updates upgrades your package.json dependencies to the _latest_ versions, ignoring specified versions.**
 
-- maintains existing semantic versioning _policies_, i.e. `"react": "^16.0.4"` to `"react": "^18.2.0"`.
+- maintains existing semantic versioning _policies_, i.e. `"react": "^17.0.2"` to `"react": "^18.3.1"`.
 - _only_ modifies package.json file. Run `npm install` to update your installed packages and package-lock.json.
 - sensible defaults, but highly customizable
+- compatible with npm, yarn, pnpm, deno, and bun
 - CLI and module usage
-- compatible with: `npm`, `yarn`, `pnpm`, `deno`, `bun`
 
-![npm-check-updates-screenshot](https://github.com/raineorshine/npm-check-updates/blob/main/.github/screenshot.png?raw=true)
+<img width="500" alt="example output" src="https://github.com/user-attachments/assets/4808618b-ac20-4fc0-92e0-a777de70a2b6">
 
-- Red = major upgrade (and all [major version zero](https://semver.org/#spec-item-4))
-- Cyan = minor upgrade
-- Green = patch upgrade
+$${\color{red}Red}$$ major upgrade (and all [major version zero](https://semver.org/#spec-item-4))<br/>
+$${\color{cyan}Cyan}$$ minor upgrade<br/>
+$${\color{green}Green}$$ patch upgrade<br/>
 
 ## Installation
 
-Install globally:
+Install globally to use `npm-check-updates` or the shorter `ncu`:
 
 ```sh
 npm install -g npm-check-updates
 ```
 
-Or run with [npx](https://docs.npmjs.com/cli/v7/commands/npx):
+Or run with [npx](https://docs.npmjs.com/cli/v7/commands/npx) (only the long form is supported):
 
 ```sh
 npx npm-check-updates
@@ -89,7 +89,7 @@ Combine with `--format group` for a truly _luxe_ experience:
 
 ## Filter packages
 
-Filter packages using the `--filter` option or adding additional cli arguments. You can exclude specific packages with the `--reject` option or prefixing a filter with `!`. Supports strings, wildcards, globs, comma-or-space-delimited lists, and regular expressions:
+Filter packages using the `--filter` option or adding additional cli arguments:
 
 ```sh
 # upgrade only mocha
@@ -97,26 +97,36 @@ ncu mocha
 ncu -f mocha
 ncu --filter mocha
 
+# upgrade only chalk, mocha, and react
+ncu chalk mocha react
+ncu chalk, mocha, react
+ncu -f "chalk mocha react"
+```
+
+Filter with wildcards or regex:
+
+```sh
 # upgrade packages that start with "react-"
 ncu react-*
 ncu "/^react-.*$/"
+```
 
+Exclude specific packages with the `--reject` option or prefixing a filter with `!`. Supports strings, wildcards, globs, comma-or-space-delimited lists, and regex:
+
+```sh
 # upgrade everything except nodemon
 ncu \!nodemon
 ncu -x nodemon
 ncu --reject nodemon
 
-# upgrade only chalk, mocha, and react
-ncu chalk mocha react
-ncu chalk, mocha, react
-ncu -f "chalk mocha react"
-
 # upgrade packages that do not start with "react-".
 ncu \!react-*
 ncu '/^(?!react-).*$/' # mac/linux
 ncu "/^(?!react-).*$/" # windows
 ```
 
+Advanced filters: [filter](https://github.com/raineorshine/npm-check-updates#filter), [filterResults](https://github.com/raineorshine/npm-check-updates#filterresults), [filterVersion](https://github.com/raineorshine/npm-check-updates#filterversion)
+
 ## How dependency updates are determined
 
 - Direct dependencies are updated to the latest stable version:
@@ -134,18 +144,21 @@ ncu "/^(?!react-).*$/" # windows
   - `*` → `*`
 - Prerelease versions are ignored by default.
   - Use `--pre` to include prerelease versions (e.g. `alpha`, `beta`, `build1235`)
-- With `--target minor`, only update patch and minor:
-  - `0.1.0` → `0.2.1`
-- With `--target patch`, only update patch:
-  - `0.1.0` → `0.1.2`
-- With `--target @next`, update to the version published on the `next` tag:
-  - `0.1.0` -> `0.1.1-next.1`
+- Choose what level to upgrade to:
+  - With `--target semver`, update according to your specified [semver](https://semver.org/) version ranges:
+    - `^1.1.0` → `^1.9.99`
+  - With `--target minor`, strictly update the patch and minor versions (including major version zero):
+    - `0.1.0` → `0.2.1`
+  - With `--target patch`, strictly update the patch version (including major version zero):
+    - `0.1.0` → `0.1.2`
+  - With `--target @next`, update to the version published on the `next` tag:
+    - `0.1.0` -> `0.1.1-next.1`
 
 ## Options
 
 Options are merged with the following precedence:
 
-1. CLI
+1. Command line options
 2. Local [Config File](#config-file)
 3. Project Config File
 4. User Config File