random-bunny/package.json

78 lines
1.8 KiB
JSON
Raw Normal View History

2016-04-27 20:06:24 +01:00
{
2020-12-20 19:39:03 +00:00
"name": "random-bunny",
2024-08-07 17:13:56 +01:00
"version": "2.3.0",
2020-12-20 19:39:03 +00:00
"description": "Get a random subreddit image url",
2016-04-27 20:06:24 +01:00
"license": "MIT",
2020-12-20 19:39:03 +00:00
"author": "Vylpes",
"exports": "./dist/index.js",
2023-01-27 22:42:37 +00:00
"typings": "./dist/index.d.ts",
"bin": "./dist/cli.js",
"main": "./dist/index.js",
2016-04-27 20:06:24 +01:00
"keywords": [
2020-12-20 19:39:03 +00:00
"rabbit",
"bunny",
"bun",
"subreddit",
"reddit",
2016-04-28 16:31:41 +01:00
"random",
"placeholder"
2016-04-27 20:06:24 +01:00
],
"dependencies": {
Update dependency commander to v12 (#145) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [commander](https://github.com/tj/commander.js) | dependencies | major | [`^11.1.0` -> `^12.0.0`](https://renovatebot.com/diffs/npm/commander/11.1.0/12.0.0) | --- ### Release Notes <details> <summary>tj/commander.js (commander)</summary> ### [`v12.0.0`](https://github.com/tj/commander.js/blob/HEAD/CHANGELOG.md#1200-2024-02-03) [Compare Source](https://github.com/tj/commander.js/compare/v11.1.0...v12.0.0) ##### Added - `.addHelpOption()` as another way of configuring built-in help option (\[[#&#8203;2006](https://github.com/tj/commander.js/issues/2006)]) - `.helpCommand()` for configuring built-in help command (\[[#&#8203;2087](https://github.com/tj/commander.js/issues/2087)]) ##### Fixed - *Breaking:* use non-zero exit code when spawned executable subcommand terminates due to a signal (\[[#&#8203;2023](https://github.com/tj/commander.js/issues/2023)]) - *Breaking:* check `passThroughOptions` constraints when using `.addCommand` and throw if parent command does not have `.enablePositionalOptions()` enabled (\[[#&#8203;1937](https://github.com/tj/commander.js/issues/1937)]) ##### Changed - *Breaking:* Commander 12 requires Node.js v18 or higher (\[[#&#8203;2027](https://github.com/tj/commander.js/issues/2027)]) - *Breaking:* throw an error if add an option with a flag which is already in use (\[[#&#8203;2055](https://github.com/tj/commander.js/issues/2055)]) - *Breaking:* throw an error if add a command with name or alias which is already in use (\[[#&#8203;2059](https://github.com/tj/commander.js/issues/2059)]) - *Breaking:* throw error when calling `.storeOptionsAsProperties()` after setting an option value (\[[#&#8203;1928](https://github.com/tj/commander.js/issues/1928)]) - replace non-standard JSDoc of `@api private` with documented `@private` (\[[#&#8203;1949](https://github.com/tj/commander.js/issues/1949)]) - `.addHelpCommand()` now takes a Command (passing string or boolean still works as before but deprecated) (\[[#&#8203;2087](https://github.com/tj/commander.js/issues/2087)]) - refactor internal implementation of built-in help option (\[[#&#8203;2006](https://github.com/tj/commander.js/issues/2006)]) - refactor internal implementation of built-in help command (\[[#&#8203;2087](https://github.com/tj/commander.js/issues/2087)]) ##### Deprecated - `.addHelpCommand()` passing string or boolean (use `.helpCommand()` or pass a Command) (\[[#&#8203;2087](https://github.com/tj/commander.js/issues/2087)]) ##### Removed - *Breaking:* removed default export of a global Command instance from CommonJS (use the named `program` export instead) (\[[#&#8203;2017](https://github.com/tj/commander.js/issues/2017)]) ##### Migration Tips **global program** If you are using the [deprecated](./docs/deprecated.md#default-import-of-global-command-object) default import of the global Command object, you need to switch to using a named import (or create a new `Command`). ```js // const program = require('commander'); const { program } = require('commander'); ``` **option and command clashes** A couple of configuration problems now throw an error, which will pick up issues in existing programs: - adding an option which uses the same flag as a previous option - adding a command which uses the same name or alias as a previous command </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4wLjAiLCJ1cGRhdGVkSW5WZXIiOiIzNy4wLjAiLCJ0YXJnZXRCcmFuY2giOiJkZXZlbG9wIn0=--> Reviewed-on: https://gitea.vylpes.xyz/RabbitLabs/random-bunny/pulls/145 Reviewed-by: Vylpes <ethan@vylpes.com> Co-authored-by: Renovate Bot <renovate@vylpes.com> Co-committed-by: Renovate Bot <renovate@vylpes.com>
2024-02-19 14:34:11 +00:00
"commander": "^12.0.0",
2021-06-19 16:13:27 +01:00
"glob-parent": "^6.0.0",
"got-cjs": "^12.5.4",
"htmlparser2": "^9.1.0",
"linqts": "^1.14.4"
2016-04-27 20:06:24 +01:00
},
2020-12-20 19:39:03 +00:00
"scripts": {
2021-12-01 20:32:20 +00:00
"build": "tsc",
Fix not being able to execute the code via ts-node (#122) # Description Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. - Removed ts-node - Since we can execute the code via unit tests and the command line now, it doesn't make to have this anymore as we can test using a proper CLI - This also fixes the issue we have with ts-node, with it not working on the latest node version #75, #119 ## Type of change Please delete options that are not relevant. - [x] Bug fix (non-breaking change which fixes an issue) # How Has This Been Tested? Please describe the tests that you ran to verify the changes. Provide instructions so we can reproduce. Please also list any relevant details to your test configuration. - This has been tested by running `yarn start`, and it now runs the cli interface # Checklist - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that provde my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published in downstream modules Reviewed-on: https://gitea.vylpes.xyz/RabbitLabs/random-bunny/pulls/122 Reviewed-by: VylpesTester <tester@vylpes.com> Co-authored-by: Ethan Lane <ethan@vylpes.com> Co-committed-by: Ethan Lane <ethan@vylpes.com>
2023-12-08 17:07:51 +00:00
"start": "node dist/cli.js",
"test": "jest",
"lint": "eslint .",
"release": "np --no-publish",
2024-04-15 18:52:31 +01:00
"package": "pkg . --no-bytecode"
2016-04-27 20:06:24 +01:00
},
"bugs": {
"url": "https://gitea.vylpes.xyz/RabbitLabs/random-bunny/issues",
"email": "helpdesk@vylpes.com"
},
"homepage": "https://gitea.vylpes.xyz/RabbitLabs/random-bunny",
2021-12-01 13:36:29 +00:00
"funding": "https://ko-fi.com/vylpes",
2021-01-13 21:08:47 +00:00
"devDependencies": {
"@eslint/eslintrc": "^3.1.0",
"@eslint/js": "^9.8.0",
"@types/eslint": "^9.6.0",
Fix not being able to execute the code via ts-node (#122) # Description Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. - Removed ts-node - Since we can execute the code via unit tests and the command line now, it doesn't make to have this anymore as we can test using a proper CLI - This also fixes the issue we have with ts-node, with it not working on the latest node version #75, #119 ## Type of change Please delete options that are not relevant. - [x] Bug fix (non-breaking change which fixes an issue) # How Has This Been Tested? Please describe the tests that you ran to verify the changes. Provide instructions so we can reproduce. Please also list any relevant details to your test configuration. - This has been tested by running `yarn start`, and it now runs the cli interface # Checklist - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that provde my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published in downstream modules Reviewed-on: https://gitea.vylpes.xyz/RabbitLabs/random-bunny/pulls/122 Reviewed-by: VylpesTester <tester@vylpes.com> Co-authored-by: Ethan Lane <ethan@vylpes.com> Co-committed-by: Ethan Lane <ethan@vylpes.com>
2023-12-08 17:07:51 +00:00
"@types/jest": "^29.5.8",
"@types/node": "^20.0.0",
"@typescript-eslint/eslint-plugin": "^8.0.0",
"@typescript-eslint/parser": "^7.18.0",
"@yao-pkg/pkg": "^5.12.0",
"eslint": "^9.8.0",
"jest": "^29.7.0",
"jest-mock-extended": "^3.0.3",
Update dependency np to v10 (#159) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [np](https://github.com/sindresorhus/np) | devDependencies | major | [`^9.0.0` -> `^10.0.0`](https://renovatebot.com/diffs/npm/np/9.2.0/10.0.5) | --- ### Release Notes <details> <summary>sindresorhus/np (np)</summary> ### [`v10.0.5`](https://github.com/sindresorhus/np/releases/tag/v10.0.5) [Compare Source](https://github.com/sindresorhus/np/compare/v10.0.4...v10.0.5) - Fix npm 10 compatibility for real ([#&#8203;744](https://github.com/sindresorhus/np/issues/744)) [`34409be`](https://github.com/sindresorhus/np/commit/34409be) ### [`v10.0.4`](https://github.com/sindresorhus/np/releases/tag/v10.0.4) [Compare Source](https://github.com/sindresorhus/np/compare/v10.0.3...v10.0.4) - Fix compatibility with npm 10 ([#&#8203;743](https://github.com/sindresorhus/np/issues/743)) [`4caa295`](https://github.com/sindresorhus/np/commit/4caa295) ### [`v10.0.3`](https://github.com/sindresorhus/np/releases/tag/v10.0.3) [Compare Source](https://github.com/sindresorhus/np/compare/v10.0.2...v10.0.3) - Fix publish OTP for Yarn Berry ([#&#8203;741](https://github.com/sindresorhus/np/issues/741)) [`02f60c7`](https://github.com/sindresorhus/np/commit/02f60c7) ### [`v10.0.2`](https://github.com/sindresorhus/np/releases/tag/v10.0.2) [Compare Source](https://github.com/sindresorhus/np/compare/v10.0.1...v10.0.2) - Use npm for tagging versions when pnpm is the chosen package manager ([#&#8203;739](https://github.com/sindresorhus/np/issues/739)) [`770418f`](https://github.com/sindresorhus/np/commit/770418f) ### [`v10.0.1`](https://github.com/sindresorhus/np/releases/tag/v10.0.1) [Compare Source](https://github.com/sindresorhus/np/compare/v10.0.0...v10.0.1) - Fix compatibility with npm 10 ([#&#8203;737](https://github.com/sindresorhus/np/issues/737)) [`9fdebd5`](https://github.com/sindresorhus/np/commit/9fdebd5) ### [`v10.0.0`](https://github.com/sindresorhus/np/releases/tag/v10.0.0) [Compare Source](https://github.com/sindresorhus/np/compare/v9.2.0...v10.0.0) ##### Breaking - Remove the `--yarn` flag ([#&#8203;730](https://github.com/sindresorhus/np/issues/730)) [`4b3b599`](https://github.com/sindresorhus/np/commit/4b3b599) - The functionality is replaced by `--package-manager`. See below. ##### Improvements - Add `--package-manager` flag ([#&#8203;730](https://github.com/sindresorhus/np/issues/730)) [`4b3b599`](https://github.com/sindresorhus/np/commit/4b3b599) - This acts like the [`packageManager` field](https://nodejs.org/api/packages.html#packagemanager) in package.json. `np` will default to reading package.json, and look for lockfiles to determine the best package manager as a last resort. - Add pnpm support ([#&#8203;730](https://github.com/sindresorhus/np/issues/730)) [`4b3b599`](https://github.com/sindresorhus/np/commit/4b3b599) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4wLjAiLCJ1cGRhdGVkSW5WZXIiOiIzNy4wLjAiLCJ0YXJnZXRCcmFuY2giOiJkZXZlbG9wIn0=--> Reviewed-on: https://git.vylpes.xyz/RabbitLabs/random-bunny/pulls/159 Co-authored-by: Renovate Bot <renovate@vylpes.com> Co-committed-by: Renovate Bot <renovate@vylpes.com>
2024-06-10 17:22:24 +01:00
"np": "^10.0.0",
"ts-jest": "^29.1.1",
"ts-mockito": "^2.6.1",
"typescript": "^5.0.0",
"typescript-eslint": "^7.18.0"
2023-01-27 22:42:37 +00:00
},
2023-05-20 15:47:20 +01:00
"resolutions": {
Update dependency got to v14 (#134) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [got](https://github.com/sindresorhus/got) | resolutions | major | [`^13.0.0` -> `^14.0.0`](https://renovatebot.com/diffs/npm/got/13.0.0/14.0.0) | --- ### Release Notes <details> <summary>sindresorhus/got (got)</summary> ### [`v14.0.0`](https://github.com/sindresorhus/got/releases/tag/v14.0.0) [Compare Source](https://github.com/sindresorhus/got/compare/v13.0.0...v14.0.0) ##### Breaking - Require Node.js 20 ([#&#8203;2313](https://github.com/sindresorhus/got/issues/2313)) [`a004263`](https://github.com/sindresorhus/got/commit/a004263) - Why not target the oldest active Node.js LTS, which is Node.js 18? I usually strictly follow this convention in my packages. However, this package is the exception because the HTTP part of Node.js is consistently buggy, and I don't have time to work around issues in older Node.js releases. I you need to still support Node.js 18, I suggest staying on Got v13, which is quite stable. Node.js 18 will be out of active LTS in 5 months. ##### Improvements - Make `followRedirect` option accept a function ([#&#8203;2306](https://github.com/sindresorhus/got/issues/2306)) [`7c3f147`](https://github.com/sindresorhus/got/commit/7c3f147) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4wLjAiLCJ1cGRhdGVkSW5WZXIiOiIzNy4wLjAiLCJ0YXJnZXRCcmFuY2giOiJkZXZlbG9wIn0=--> Reviewed-on: https://gitea.vylpes.xyz/RabbitLabs/random-bunny/pulls/134 Co-authored-by: Renovate Bot <renovate@vylpes.com> Co-committed-by: Renovate Bot <renovate@vylpes.com>
2024-01-16 19:14:22 +00:00
"np/**/got": "^14.0.0",
"**/semver": "^7.5.2",
"@babel/traverse": "^7.23.2"
2023-05-20 15:47:20 +01:00
},
2023-01-27 22:42:37 +00:00
"files": [
"dist"
],
"pkg": {
"scripts": "dist/**/*.js",
"targets": [
"latest-linux-x64",
"latest-macos-x64",
"latest-macos-arm64",
"latest-win-x64"
],
"outputPath": "bin"
}
2016-04-27 20:06:24 +01:00
}