OpenNeo/impress
OpenNeo/impress
1
0
Fork 1
Code Pull requests Activity
impress/yarn.lock

5599 lines
195 KiB
Text
Raw Permalink Normal View History

Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
# This file is generated by running "yarn install" inside your project.
# Manual changes might be lost - proceed with caution!
__metadata:
version: 8
cacheKey: 10c0
"@apollo/client@npm:^3.6.9":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 3.10.1
resolution: "@apollo/client@npm:3.10.1"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
"@graphql-typed-document-node/core": "npm:^3.1.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@wry/caches": "npm:^1.0.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"@wry/equality": "npm:^0.5.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@wry/trie": "npm:^0.5.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
graphql-tag: "npm:^2.12.6"
hoist-non-react-statics: "npm:^3.3.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
optimism: "npm:^0.18.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
prop-types: "npm:^15.7.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
rehackt: "npm:^0.1.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
response-iterator: "npm:^0.2.6"
symbol-observable: "npm:^4.0.0"
ts-invariant: "npm:^0.10.3"
tslib: "npm:^2.3.0"
zen-observable-ts: "npm:^1.2.5"
peerDependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
graphql: ^15.0.0 || ^16.0.0
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
graphql-ws: ^5.5.5
react: ^16.8.0 || ^17.0.0 || ^18.0.0
react-dom: ^16.8.0 || ^17.0.0 || ^18.0.0
subscriptions-transport-ws: ^0.9.0 || ^0.11.0
peerDependenciesMeta:
graphql-ws:
optional: true
react:
optional: true
react-dom:
optional: true
subscriptions-transport-ws:
optional: true
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/966ff0f3f6cfa172fe77498a6a376158046606378f5439f1c5e39ff7afa13be01b6414e0c49082777aca5a6d05de491edc22083f2c4d5801faf88b8e7a886e99
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@babel/code-frame@npm:^7.0.0":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 7.24.2
resolution: "@babel/code-frame@npm:7.24.2"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@babel/highlight": "npm:^7.24.2"
picocolors: "npm:^1.0.0"
checksum: 10c0/d1d4cba89475ab6aab7a88242e1fd73b15ecb9f30c109b69752956434d10a26a52cbd37727c4eca104b6d45227bd1dfce39a6a6f4a14c9b2f07f871e968cf406
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@babel/helper-module-imports@npm:^7.16.7":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 7.24.3
resolution: "@babel/helper-module-imports@npm:7.24.3"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@babel/types": "npm:^7.24.0"
checksum: 10c0/052c188adcd100f5e8b6ff0c9643ddaabc58b6700d3bbbc26804141ad68375a9f97d9d173658d373d31853019e65f62610239e3295cdd58e573bdcb2fded188d
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@babel/helper-string-parser@npm:^7.24.1":
version: 7.24.1
resolution: "@babel/helper-string-parser@npm:7.24.1"
checksum: 10c0/2f9bfcf8d2f9f083785df0501dbab92770111ece2f90d120352fda6dd2a7d47db11b807d111e6f32aa1ba6d763fe2dc6603d153068d672a5d0ad33ca802632b2
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@babel/helper-validator-identifier@npm:^7.24.5":
version: 7.24.5
resolution: "@babel/helper-validator-identifier@npm:7.24.5"
checksum: 10c0/05f957229d89ce95a137d04e27f7d0680d84ae48b6ad830e399db0779341f7d30290f863a93351b4b3bde2166737f73a286ea42856bb07c8ddaa95600d38645c
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@babel/highlight@npm:^7.24.2":
version: 7.24.5
resolution: "@babel/highlight@npm:7.24.5"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@babel/helper-validator-identifier": "npm:^7.24.5"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
chalk: "npm:^2.4.2"
js-tokens: "npm:^4.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
picocolors: "npm:^1.0.0"
checksum: 10c0/e98047d3ad24608bfa596d000c861a2cc875af897427f2833b91a4e0d4cead07301a7ec15fa26093dcd61e036e2eed2db338ae54f93016fe0dc785fadc4159db
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@babel/runtime@npm:^7.0.0, @babel/runtime@npm:^7.12.13, @babel/runtime@npm:^7.12.18, @babel/runtime@npm:^7.12.5, @babel/runtime@npm:^7.18.3, @babel/runtime@npm:^7.23.2, @babel/runtime@npm:^7.5.5, @babel/runtime@npm:^7.8.7":
version: 7.24.5
resolution: "@babel/runtime@npm:7.24.5"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
regenerator-runtime: "npm:^0.14.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/05730e43e8ba6550eae9fd4fb5e7d9d3cb91140379425abcb2a1ff9cebad518a280d82c4c4b0f57ada26a863106ac54a748d90c775790c0e2cd0ddd85ccdf346
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@babel/types@npm:^7.24.0":
version: 7.24.5
resolution: "@babel/types@npm:7.24.5"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@babel/helper-string-parser": "npm:^7.24.1"
"@babel/helper-validator-identifier": "npm:^7.24.5"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
to-fast-properties: "npm:^2.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/e1284eb046c5e0451b80220d1200e2327e0a8544a2fe45bb62c952e5fdef7099c603d2336b17b6eac3cc046b7a69bfbce67fe56e1c0ea48cd37c65cb88638f2a
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/accordion@npm:1.4.12":
version: 1.4.12
resolution: "@chakra-ui/accordion@npm:1.4.12"
dependencies:
"@chakra-ui/descendant": "npm:2.1.4"
"@chakra-ui/hooks": "npm:1.9.1"
"@chakra-ui/icon": "npm:2.0.5"
"@chakra-ui/react-utils": "npm:1.2.3"
"@chakra-ui/transition": "npm:1.4.8"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
framer-motion: 3.x || 4.x || 5.x || 6.x
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/21c2245f89c32a460759c9f07a3dd82c2a512aceb406ab5f9cf28adcced6034ceb0b9d6ad66ece4474bea64eb4e6faa74aacfdd38190c91277b4e1981d83d7f9
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/alert@npm:1.3.7":
version: 1.3.7
resolution: "@chakra-ui/alert@npm:1.3.7"
dependencies:
"@chakra-ui/icon": "npm:2.0.5"
"@chakra-ui/react-utils": "npm:1.2.3"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/5fb7128ea1175c7275bf52eaabf08c6f6e6ae770a5822d3da77f1c84f0c7f43b7293647f7c5b73cd05e65eadfa2cc927714f4c69b9f81eff51b5a77d8a7b5cbb
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/anatomy@npm:1.3.0":
version: 1.3.0
resolution: "@chakra-ui/anatomy@npm:1.3.0"
dependencies:
"@chakra-ui/theme-tools": "npm:^1.3.6"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/9a06e4b09a4d55747028c3ca9adb4176f6d5a85573255a565e9d94c877c369e91b98e47db4b796875edda569d83ccb678c0d7802caee97ed9670d2fac85006f2
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/avatar@npm:1.3.11":
version: 1.3.11
resolution: "@chakra-ui/avatar@npm:1.3.11"
dependencies:
"@chakra-ui/image": "npm:1.1.10"
"@chakra-ui/react-utils": "npm:1.2.3"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/10bd2dd87d6082ad33ae678f1cd4d73a17730d2d6cebcf12e32ded4a24ea83a593b61c0d2126d559f385c256f58168ba4a47f4c6586c8a9c1c3471711246683e
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/breadcrumb@npm:1.3.6":
version: 1.3.6
resolution: "@chakra-ui/breadcrumb@npm:1.3.6"
dependencies:
"@chakra-ui/react-utils": "npm:1.2.3"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/67eff5f2d059f182ae0636e3bc264bf41867193a1f23b7a445950de28515c02efb50aa42bb1d4a778c82112072cb4624522140441e9f7c0820d6675f46b9453d
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/button@npm:1.5.10":
version: 1.5.10
resolution: "@chakra-ui/button@npm:1.5.10"
dependencies:
"@chakra-ui/hooks": "npm:1.9.1"
"@chakra-ui/react-utils": "npm:1.2.3"
"@chakra-ui/spinner": "npm:1.2.6"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/70b1f3de2befe15a21db566dbd48b361d59114f724694de29191221f4f3e766613fcd6642606b4df3b873b8ad7586b63626d2ae28fc82d9ac9638ad1846c7c2d
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/checkbox@npm:1.7.1":
version: 1.7.1
resolution: "@chakra-ui/checkbox@npm:1.7.1"
dependencies:
"@chakra-ui/form-control": "npm:1.6.0"
"@chakra-ui/hooks": "npm:1.9.1"
"@chakra-ui/react-utils": "npm:1.2.3"
"@chakra-ui/utils": "npm:1.10.4"
"@chakra-ui/visually-hidden": "npm:1.1.6"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
framer-motion: 3.x || 4.x || 5.x || 6.x
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/99f12b4035ec223c9a0ff74b9a35272cca33a3d5b094f9a30f67959894c7382db4ef5d91094b39c679f44d0ed973fa53e0dc98ce9d72775725a59afaf46df87a
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/clickable@npm:1.2.6":
version: 1.2.6
resolution: "@chakra-ui/clickable@npm:1.2.6"
dependencies:
"@chakra-ui/react-utils": "npm:1.2.3"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/21cd361b837d09e4379c73b841c63f7041055c16f186b0e532381d2036e1adc676cb2cbbeb3f0df828c0bddee08855d3e3ac0c623090830ccade1f0c6abfab9f
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/close-button@npm:1.2.7":
version: 1.2.7
resolution: "@chakra-ui/close-button@npm:1.2.7"
dependencies:
"@chakra-ui/icon": "npm:2.0.5"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/2abd371f3729c3d30c5c6669a78f2485ec44dd7dc4693aedffceb7a02d1bc60a06df16237c91c90aa0a73e5a56a48d4914f08f8fe8e0192449f7cccfec3aa627
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/color-mode@npm:1.4.8":
version: 1.4.8
resolution: "@chakra-ui/color-mode@npm:1.4.8"
dependencies:
"@chakra-ui/hooks": "npm:1.9.1"
"@chakra-ui/react-env": "npm:1.1.6"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/14a9b4e0ecd1254d6c836360c134b6084031e19e98be4a7e91d17d1e425e550d4063f57bda23c7a312307e10ddbee06d130b29e2e99767d83c29eb17aaee1f75
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/control-box@npm:1.1.6":
version: 1.1.6
resolution: "@chakra-ui/control-box@npm:1.1.6"
dependencies:
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/469cfd63bec85186ddce0ffe62637f5ecdef1eae4be0885f19145fb1ce2ffced343e8683804034598c7bf931253e367d020c0aef16d46f199ed4940001773e9f
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/counter@npm:1.2.10":
version: 1.2.10
resolution: "@chakra-ui/counter@npm:1.2.10"
dependencies:
"@chakra-ui/hooks": "npm:1.9.1"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/37ed13c45206d5571d25b22373c04658c5e22c1a32be5b71b6741278d1170dfa90ae1c37f41a17c7a37b2e7d2731358a829d58c90998b46beab91e3ca9fbd993
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/css-reset@npm:1.1.3":
version: 1.1.3
resolution: "@chakra-ui/css-reset@npm:1.1.3"
peerDependencies:
"@emotion/react": ">=10.0.35"
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/8a613c82bb83c35e95f81ed3063d9ed8debbc4dabdbf08d7c676c537cd1f690e0a8a7809f390899f996380a0c14afe8f0433a0bf498fef3b3e76042c29b49fd3
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/descendant@npm:2.1.4":
version: 2.1.4
resolution: "@chakra-ui/descendant@npm:2.1.4"
dependencies:
"@chakra-ui/react-utils": "npm:^1.2.3"
peerDependencies:
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/496b6781c1dbad8e2b1443400ecd340b4f428b1b9a548e31972abcd99b47ad918d2baa5f98e1784b1ee0824686af380bcbba98a8520e95fcb05d4605ce5defb7
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/editable@npm:1.4.2":
version: 1.4.2
resolution: "@chakra-ui/editable@npm:1.4.2"
dependencies:
"@chakra-ui/hooks": "npm:1.9.1"
"@chakra-ui/react-utils": "npm:1.2.3"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/d7622f8adf90643a59763067f8e50a54280188902a02531a85d4669afb7e08a6c2eb3fabef4f90259a379e3f4a054d0e662da4d401f3c7b3881f62421af4154e
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/focus-lock@npm:1.2.6":
version: 1.2.6
resolution: "@chakra-ui/focus-lock@npm:1.2.6"
dependencies:
"@chakra-ui/utils": "npm:1.10.4"
react-focus-lock: "npm:2.5.2"
peerDependencies:
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/a97a1d0b785e2862561c6cc835cc60c300da1c0d198e4547c66df66f6e2aff4b5c46b3a1f3cfd9a7a08eb1e3c415dddac32075cdca39791a5fab3dac1193217a
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/form-control@npm:1.6.0":
version: 1.6.0
resolution: "@chakra-ui/form-control@npm:1.6.0"
dependencies:
"@chakra-ui/hooks": "npm:1.9.1"
"@chakra-ui/icon": "npm:2.0.5"
"@chakra-ui/react-utils": "npm:1.2.3"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/febea996c1ef340fc2efe37495b9e678e50c942d53c117c39b56497d85b70b0dc13235f8c0aed13a3285873e3f8ea5ab513531699a1a65abdb4cd60c9a41c178
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/hooks@npm:1.9.1":
version: 1.9.1
resolution: "@chakra-ui/hooks@npm:1.9.1"
dependencies:
"@chakra-ui/react-utils": "npm:1.2.3"
"@chakra-ui/utils": "npm:1.10.4"
compute-scroll-into-view: "npm:1.0.14"
copy-to-clipboard: "npm:3.3.1"
peerDependencies:
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/bdba31fd0c1e8912797b55d03a8655e416c198eb2672098b65359599678d8a91d5b7535a28f7d0fa9fa430bbcf0abc9f4ec83d93f143a317694d15af37d954cb
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/icon@npm:2.0.5":
version: 2.0.5
resolution: "@chakra-ui/icon@npm:2.0.5"
dependencies:
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/3d18729727a6e2eb2c9829680b955e35078234a6a8c33e991013d65f2125f2234817a854ea8197d457de109be0e59ffbae7eaea04a3cd8169c484f984b6212d8
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/icons@npm:^1.0.4":
version: 1.1.7
resolution: "@chakra-ui/icons@npm:1.1.7"
dependencies:
"@chakra-ui/icon": "npm:2.0.5"
"@types/react": "npm:^17.0.15"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/68707c7512f8f5e39e7e8bfa3d2faa1be39733d6513732855ec5e48a058b05e3fbc2755f05f85f2f90e0e0579cc24abf20ac86b53aba14a405596eb06aca7e31
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/image@npm:1.1.10":
version: 1.1.10
resolution: "@chakra-ui/image@npm:1.1.10"
dependencies:
"@chakra-ui/hooks": "npm:1.9.1"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/55b5d85f86abbafe9dfd8df4b87b8bee0c54d41c36818bc8d123dced75036ef651fd70506b51f9f70c70006c4b907cb8bf4af639fef545b087ff946e6d41f838
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/input@npm:1.4.6":
version: 1.4.6
resolution: "@chakra-ui/input@npm:1.4.6"
dependencies:
"@chakra-ui/form-control": "npm:1.6.0"
"@chakra-ui/react-utils": "npm:1.2.3"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/adaf0acb9d18cca216a2a8ec796ccec3d4771b238b6de9f9fb881481d375c7361c342541f50d010939c15657bc22a156d38918537a908ca3e36e4f58ac6e6b8e
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/layout@npm:1.8.0":
version: 1.8.0
resolution: "@chakra-ui/layout@npm:1.8.0"
dependencies:
"@chakra-ui/icon": "npm:2.0.5"
"@chakra-ui/react-utils": "npm:1.2.3"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/ad7c9448bc6e0889a58ac9b3196c480550dabdda11f4a5a8db83490cf328ede544e6717fc80973113bfc54c019c300481337f05fda54bc021b90ddfbf3f2e49a
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/live-region@npm:1.1.6":
version: 1.1.6
resolution: "@chakra-ui/live-region@npm:1.1.6"
dependencies:
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/f082209390a1f30d9ce5f32e8ba5caf015762357764f123faeb4e16190014f2259db33e2a7313233e50dfe2c8573aa8875eaaedb1fd451f766df9bc801a46bda
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/media-query@npm:2.0.4":
version: 2.0.4
resolution: "@chakra-ui/media-query@npm:2.0.4"
dependencies:
"@chakra-ui/react-env": "npm:1.1.6"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
"@chakra-ui/theme": ">=1.0.0"
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/fd7843332024ba268490c1aca8a9eab6112835d28b7ab5d5478b760bf7df5fdbcff45a5145202b98b56ea0c211f14b169990d706b44e451947f326a5cf625277
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/menu@npm:1.8.12":
version: 1.8.12
resolution: "@chakra-ui/menu@npm:1.8.12"
dependencies:
"@chakra-ui/clickable": "npm:1.2.6"
"@chakra-ui/descendant": "npm:2.1.4"
"@chakra-ui/hooks": "npm:1.9.1"
"@chakra-ui/popper": "npm:2.4.3"
"@chakra-ui/react-utils": "npm:1.2.3"
"@chakra-ui/transition": "npm:1.4.8"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
framer-motion: 3.x || 4.x || 5.x || 6.x
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/5c0f6fb88049d3a9f1e7724f440b10db9eb0587ee7f67a8d0df03743748ff2ed9e2822eecbed85c7249e2d445e56bb34f0146e6e59fe45f551b8d8ce844886f1
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/modal@npm:1.11.1":
version: 1.11.1
resolution: "@chakra-ui/modal@npm:1.11.1"
dependencies:
"@chakra-ui/close-button": "npm:1.2.7"
"@chakra-ui/focus-lock": "npm:1.2.6"
"@chakra-ui/hooks": "npm:1.9.1"
"@chakra-ui/portal": "npm:1.3.10"
"@chakra-ui/react-utils": "npm:1.2.3"
"@chakra-ui/transition": "npm:1.4.8"
"@chakra-ui/utils": "npm:1.10.4"
aria-hidden: "npm:^1.1.1"
react-remove-scroll: "npm:2.4.1"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
framer-motion: 3.x || 4.x || 5.x || 6.x
react: ">=16.8.6"
react-dom: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/a6ce0c7c00776f2b3bb60fc970c662c0fc9891ff8ddaec8f183f9ab3712ea779c66c40da1a4d6fbaf4bfbc9e34f55e5d24ddc922e39a46136f5789394502f622
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/number-input@npm:1.4.7":
version: 1.4.7
resolution: "@chakra-ui/number-input@npm:1.4.7"
dependencies:
"@chakra-ui/counter": "npm:1.2.10"
"@chakra-ui/form-control": "npm:1.6.0"
"@chakra-ui/hooks": "npm:1.9.1"
"@chakra-ui/icon": "npm:2.0.5"
"@chakra-ui/react-utils": "npm:1.2.3"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/3d5b8fa3557322ee18fedb9d59962c93e4b15f297fabdb5d9857f0f1f0bb2087085c4046f3452a7ec485aee07485236b985c7cc30dab6bf7c8b7a784bfd7ef48
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/pin-input@npm:1.7.11":
version: 1.7.11
resolution: "@chakra-ui/pin-input@npm:1.7.11"
dependencies:
"@chakra-ui/descendant": "npm:2.1.4"
"@chakra-ui/hooks": "npm:1.9.1"
"@chakra-ui/react-utils": "npm:1.2.3"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/d06ce707c2bb1956289174f5cd14071b04b7b793da71daf3e7cd062234f75770c419e59c8e1f0e2965d6b03f23a8f28d303bd24aeecfe3509963abe6587be90c
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/popover@npm:1.11.9":
version: 1.11.9
resolution: "@chakra-ui/popover@npm:1.11.9"
dependencies:
"@chakra-ui/close-button": "npm:1.2.7"
"@chakra-ui/hooks": "npm:1.9.1"
"@chakra-ui/popper": "npm:2.4.3"
"@chakra-ui/react-utils": "npm:1.2.3"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
framer-motion: 3.x || 4.x || 5.x || 6.x
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/eee551c7ef48b2288592ae11248c4537324942a94cb0b0b07622b5a457c11ae22f8d797fcf6ac2189ac04f98c76e598ea49437696279f9ecac5fb1ddfa3e0558
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/popper@npm:2.4.3":
version: 2.4.3
resolution: "@chakra-ui/popper@npm:2.4.3"
dependencies:
"@chakra-ui/react-utils": "npm:1.2.3"
"@popperjs/core": "npm:^2.9.3"
peerDependencies:
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/96fa8db13098ef2be5e5e6a75a10c02e054d595133d9b40f07978acd04c198cdf3978db39c782dde68cb673417d786930454cdd8cdea6fd914496f73c95eba4d
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/portal@npm:1.3.10":
version: 1.3.10
resolution: "@chakra-ui/portal@npm:1.3.10"
dependencies:
"@chakra-ui/hooks": "npm:1.9.1"
"@chakra-ui/react-utils": "npm:1.2.3"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
react: ">=16.8.6"
react-dom: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/34a98241bd1fe3f83960bf5c51920667491c03aee7d89e702b72d3c3741b9bf802851f992decdfb5fcfb17efb7b9c2605e899e4cb4aa9093af6e5497f6b0513f
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/progress@npm:1.2.6":
version: 1.2.6
resolution: "@chakra-ui/progress@npm:1.2.6"
dependencies:
"@chakra-ui/theme-tools": "npm:1.3.6"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/96cbc1cd840507006d512068ec95b99ac6c744d66c68a0ba619d2baee4b41ecbc5c24ce5666e1acfaf17fa50517ab16ac55cbad48e299afc44f6c97425dda44f
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/provider@npm:1.7.14":
version: 1.7.14
resolution: "@chakra-ui/provider@npm:1.7.14"
dependencies:
"@chakra-ui/css-reset": "npm:1.1.3"
"@chakra-ui/hooks": "npm:1.9.1"
"@chakra-ui/portal": "npm:1.3.10"
"@chakra-ui/react-env": "npm:1.1.6"
"@chakra-ui/system": "npm:1.12.1"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@emotion/react": ^11.0.0
"@emotion/styled": ^11.0.0
react: ">=16.8.6"
react-dom: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/67799c74f130c71771193a137e243e4e04c670112550fd7f259a4399fcb6a20b13f0b1eeb05094c2854a76b88a02120bf70fbc003f943ba2bc1ba5820de8238b
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/radio@npm:1.5.1":
version: 1.5.1
resolution: "@chakra-ui/radio@npm:1.5.1"
dependencies:
"@chakra-ui/form-control": "npm:1.6.0"
"@chakra-ui/hooks": "npm:1.9.1"
"@chakra-ui/react-utils": "npm:1.2.3"
"@chakra-ui/utils": "npm:1.10.4"
"@chakra-ui/visually-hidden": "npm:1.1.6"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/11b61c55ae186b70ff3c55aaac98af7eb1680869a60c3d507c12e2744fa0d3f955f59eb867d5169474f33e28b22b0ea2a420d553a4e050872b1f4505a18fe058
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/react-env@npm:1.1.6":
version: 1.1.6
resolution: "@chakra-ui/react-env@npm:1.1.6"
dependencies:
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/a5a119f3f659bf9a1c51943662c17a4de2bcf5edc8b99fe2434d60dce3c3b6d8fbdd819cee0b14c24b1e363f58522ea2ff4469e73cb2d87a92ae6ad4ff4c9635
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/react-utils@npm:1.2.3, @chakra-ui/react-utils@npm:^1.2.3":
version: 1.2.3
resolution: "@chakra-ui/react-utils@npm:1.2.3"
dependencies:
"@chakra-ui/utils": "npm:^1.10.4"
peerDependencies:
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/8171654bcaa06923566ccb5eea091de91e875743ab60f08b1db57d9640ef2580b26a565cb8b97ad83a08cfada0d042e7c1d18ee605e0050be66e45b1388071df
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/react@npm:^1.6.0":
version: 1.8.9
resolution: "@chakra-ui/react@npm:1.8.9"
dependencies:
"@chakra-ui/accordion": "npm:1.4.12"
"@chakra-ui/alert": "npm:1.3.7"
"@chakra-ui/avatar": "npm:1.3.11"
"@chakra-ui/breadcrumb": "npm:1.3.6"
"@chakra-ui/button": "npm:1.5.10"
"@chakra-ui/checkbox": "npm:1.7.1"
"@chakra-ui/close-button": "npm:1.2.7"
"@chakra-ui/control-box": "npm:1.1.6"
"@chakra-ui/counter": "npm:1.2.10"
"@chakra-ui/css-reset": "npm:1.1.3"
"@chakra-ui/editable": "npm:1.4.2"
"@chakra-ui/form-control": "npm:1.6.0"
"@chakra-ui/hooks": "npm:1.9.1"
"@chakra-ui/icon": "npm:2.0.5"
"@chakra-ui/image": "npm:1.1.10"
"@chakra-ui/input": "npm:1.4.6"
"@chakra-ui/layout": "npm:1.8.0"
"@chakra-ui/live-region": "npm:1.1.6"
"@chakra-ui/media-query": "npm:2.0.4"
"@chakra-ui/menu": "npm:1.8.12"
"@chakra-ui/modal": "npm:1.11.1"
"@chakra-ui/number-input": "npm:1.4.7"
"@chakra-ui/pin-input": "npm:1.7.11"
"@chakra-ui/popover": "npm:1.11.9"
"@chakra-ui/popper": "npm:2.4.3"
"@chakra-ui/portal": "npm:1.3.10"
"@chakra-ui/progress": "npm:1.2.6"
"@chakra-ui/provider": "npm:1.7.14"
"@chakra-ui/radio": "npm:1.5.1"
"@chakra-ui/react-env": "npm:1.1.6"
"@chakra-ui/select": "npm:1.2.11"
"@chakra-ui/skeleton": "npm:1.2.14"
"@chakra-ui/slider": "npm:1.5.11"
"@chakra-ui/spinner": "npm:1.2.6"
"@chakra-ui/stat": "npm:1.2.7"
"@chakra-ui/switch": "npm:1.3.10"
"@chakra-ui/system": "npm:1.12.1"
"@chakra-ui/table": "npm:1.3.6"
"@chakra-ui/tabs": "npm:1.6.11"
"@chakra-ui/tag": "npm:1.2.7"
"@chakra-ui/textarea": "npm:1.2.11"
"@chakra-ui/theme": "npm:1.14.1"
"@chakra-ui/toast": "npm:1.5.9"
"@chakra-ui/tooltip": "npm:1.5.1"
"@chakra-ui/transition": "npm:1.4.8"
"@chakra-ui/utils": "npm:1.10.4"
"@chakra-ui/visually-hidden": "npm:1.1.6"
peerDependencies:
"@emotion/react": ^11.0.0
"@emotion/styled": ^11.0.0
framer-motion: 3.x || 4.x || 5.x || 6.x
react: ">=16.8.6"
react-dom: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/1910748f863e615d21d9d548852389120f6737c99cfa6518d899deddc98db4167c7316e3858dd3547bdfc60a4a060c1be0ca18e49a5ea4f1b1f4cdbce3c961f1
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/select@npm:1.2.11":
version: 1.2.11
resolution: "@chakra-ui/select@npm:1.2.11"
dependencies:
"@chakra-ui/form-control": "npm:1.6.0"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/6af7f647a5a6038f3b439fb0eb57715d25ba84992ff00c22e48e3ee87ded2d48548618ed852ba8d36c28c5ea2dc2636d9c3d8774999b120290abf00415d7752f
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/skeleton@npm:1.2.14":
version: 1.2.14
resolution: "@chakra-ui/skeleton@npm:1.2.14"
dependencies:
"@chakra-ui/hooks": "npm:1.9.1"
"@chakra-ui/media-query": "npm:2.0.4"
"@chakra-ui/system": "npm:1.12.1"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@chakra-ui/theme": ">=1.0.0"
"@emotion/react": ^11.0.0
"@emotion/styled": ^11.0.0
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/0777f804ef929d48297bd8e1035ee5aa8ca234ba3c4b348a80c11a314786ed542b82003d72c8fa56803d69b0b84b182b2da6dabdca6bec29e7a66b2d31016b2e
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/slider@npm:1.5.11":
version: 1.5.11
resolution: "@chakra-ui/slider@npm:1.5.11"
dependencies:
"@chakra-ui/hooks": "npm:1.9.1"
"@chakra-ui/react-utils": "npm:1.2.3"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/760d21fa3cd1465163e571c5b46588c914bfe129719711e268e976a54707e19363e0ce686f207f0b204b8259879a0fc726c62865d33dd6d3068c6275577ef200
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/spinner@npm:1.2.6":
version: 1.2.6
resolution: "@chakra-ui/spinner@npm:1.2.6"
dependencies:
"@chakra-ui/utils": "npm:1.10.4"
"@chakra-ui/visually-hidden": "npm:1.1.6"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/e8419a9d57328bdfd021a40496ee03d99eb24b8afd8b22e83f34022e079499ebacb3262e16d5b60e55fe13933807c62d29919e8de5435206085e1113c7413dcd
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/stat@npm:1.2.7":
version: 1.2.7
resolution: "@chakra-ui/stat@npm:1.2.7"
dependencies:
"@chakra-ui/icon": "npm:2.0.5"
"@chakra-ui/utils": "npm:1.10.4"
"@chakra-ui/visually-hidden": "npm:1.1.6"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/94ba5dfe712b4fd018eb49c94b1fc0aaf7a03a33933d22416f77c6cdcb0ab5f1c993802452c96854bedb7644b68aa49a29916cd8c4e59219f8a7e4df99d8c30c
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/styled-system@npm:1.19.0":
version: 1.19.0
resolution: "@chakra-ui/styled-system@npm:1.19.0"
dependencies:
"@chakra-ui/utils": "npm:1.10.4"
csstype: "npm:3.0.9"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/95e0f651c15e99269ac00476a0f23dbc8d091aacaedb25b05e86abdab52b9e967f400b041e862afa0a46ffad71a184888eeba7354e4e81a9e600942f371a4400
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/switch@npm:1.3.10":
version: 1.3.10
resolution: "@chakra-ui/switch@npm:1.3.10"
dependencies:
"@chakra-ui/checkbox": "npm:1.7.1"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
framer-motion: 3.x || 4.x || 5.x || 6.x
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/852b31635cb23621375a29c739b10955a711daeadef247620adae93bc1236965e510605446a3c0edeb705460ac0ca8c6009f9f5d52f407c9d4dc55a216410885
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/system@npm:1.12.1":
version: 1.12.1
resolution: "@chakra-ui/system@npm:1.12.1"
dependencies:
"@chakra-ui/color-mode": "npm:1.4.8"
"@chakra-ui/react-utils": "npm:1.2.3"
"@chakra-ui/styled-system": "npm:1.19.0"
"@chakra-ui/utils": "npm:1.10.4"
react-fast-compare: "npm:3.2.0"
peerDependencies:
"@emotion/react": ^11.0.0
"@emotion/styled": ^11.0.0
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/2ad7644fa39b40ff34b635792f26bc39d498f925168e9df5b71f754c2e90bcbfacea403c8f35dc2956c8985f7e84a28a5043bf486464268fb96794464fb4f2a1
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/table@npm:1.3.6":
version: 1.3.6
resolution: "@chakra-ui/table@npm:1.3.6"
dependencies:
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/cf6f1b2fdab891d163ad87b17d8da31bd5b35df8b6b99eebc4ccd006e6c41363562574af830df8bbd78fcdc7e1c50991edaa1dab6319440738baffc8eee9775e
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/tabs@npm:1.6.11":
version: 1.6.11
resolution: "@chakra-ui/tabs@npm:1.6.11"
dependencies:
"@chakra-ui/clickable": "npm:1.2.6"
"@chakra-ui/descendant": "npm:2.1.4"
"@chakra-ui/hooks": "npm:1.9.1"
"@chakra-ui/react-utils": "npm:1.2.3"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/8b0cdb142bd31dd22afd3a517fd8d8fbfc06dc04cbb53abcb0d93a52cf5768de7f15b48656f424f226c4a0088e5b934b21bf8b5935442045a4f5bbe40e098897
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/tag@npm:1.2.7":
version: 1.2.7
resolution: "@chakra-ui/tag@npm:1.2.7"
dependencies:
"@chakra-ui/icon": "npm:2.0.5"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/2d60585f8f6785f1b97d6ed248dcfe5a52ad3ea255b4ba62ee4c109d004b2118f1470345585ca05b030e9d12627091b5c647fc75e129fd8f3353a3696d9acac4
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/textarea@npm:1.2.11":
version: 1.2.11
resolution: "@chakra-ui/textarea@npm:1.2.11"
dependencies:
"@chakra-ui/form-control": "npm:1.6.0"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/ae271ca747088bda00b90e611d1fe17a4ab084b914fca5924285b15bdc78acb9c1c05c2502911185aa5664ac073c869f1d0b85809485a1e982f8672fbd62c527
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/theme-tools@npm:1.3.6, @chakra-ui/theme-tools@npm:^1.3.6":
version: 1.3.6
resolution: "@chakra-ui/theme-tools@npm:1.3.6"
dependencies:
"@chakra-ui/utils": "npm:1.10.4"
"@ctrl/tinycolor": "npm:^3.4.0"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/4ca8146ed6bec51e86e235bfad4269ebf345ace862ea31668b9df11c6b6b1303abd715d656f670a408a14ccb3cf3e773d77043b3232c20dcb88a799661349c9e
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/theme@npm:1.14.1":
version: 1.14.1
resolution: "@chakra-ui/theme@npm:1.14.1"
dependencies:
"@chakra-ui/anatomy": "npm:1.3.0"
"@chakra-ui/theme-tools": "npm:1.3.6"
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/4ca9b687463a274c1323352f6ecf2ae9bc0dfcb620da467d72c7ed2f660f4b173580d575aaf95fa6ed486710a136e1f464d78b45a0f9a23a6e24541df4ec71e6
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/toast@npm:1.5.9":
version: 1.5.9
resolution: "@chakra-ui/toast@npm:1.5.9"
dependencies:
"@chakra-ui/alert": "npm:1.3.7"
"@chakra-ui/close-button": "npm:1.2.7"
"@chakra-ui/hooks": "npm:1.9.1"
"@chakra-ui/theme": "npm:1.14.1"
"@chakra-ui/transition": "npm:1.4.8"
"@chakra-ui/utils": "npm:1.10.4"
"@reach/alert": "npm:0.13.2"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
framer-motion: 3.x || 4.x || 5.x || 6.x
react: ">=16.8.6"
react-dom: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/c83c01df60a11930153035102117c34e7d3eddcc668c41a67e8a24f93a64db466af12c534cd02ff17b05a9c99b6d5279f5239a134665c6bbad0328c846404b97
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/tooltip@npm:1.5.1":
version: 1.5.1
resolution: "@chakra-ui/tooltip@npm:1.5.1"
dependencies:
"@chakra-ui/hooks": "npm:1.9.1"
"@chakra-ui/popper": "npm:2.4.3"
"@chakra-ui/portal": "npm:1.3.10"
"@chakra-ui/react-utils": "npm:1.2.3"
"@chakra-ui/utils": "npm:1.10.4"
"@chakra-ui/visually-hidden": "npm:1.1.6"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
framer-motion: 3.x || 4.x || 5.x || 6.x
react: ">=16.8.6"
react-dom: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/07d1d3a59de2eaf78bfa67e0f11b642a1db4582d9b6f7b1216cb53d151941ec69f31326ac20f4b072c881b01a21db5a7ae11cdca026b4dda218249420e7a632d
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/transition@npm:1.4.8":
version: 1.4.8
resolution: "@chakra-ui/transition@npm:1.4.8"
dependencies:
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
framer-motion: 3.x || 4.x || 5.x || 6.x
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/0dc3487f1740c6844dc76b6a4ed631c482b9b6f0258432d02bc2be226ef78242715a5340b6f4321f876132670ae14aec766a2d76a4bdb49ba8cbbbafa1a87ea1
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/utils@npm:1.10.4, @chakra-ui/utils@npm:^1.10.4":
version: 1.10.4
resolution: "@chakra-ui/utils@npm:1.10.4"
dependencies:
"@types/lodash.mergewith": "npm:4.6.6"
css-box-model: "npm:1.2.1"
framesync: "npm:5.3.0"
lodash.mergewith: "npm:4.6.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/16d830bac30dceee2845cdd264eb86d4a4348da2d88a309187c8856409c7ba9f691d0fad00f7fe8b8b49553ac77611cce6786a4c127c5949afc2e1b04b1629ed
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@chakra-ui/visually-hidden@npm:1.1.6":
version: 1.1.6
resolution: "@chakra-ui/visually-hidden@npm:1.1.6"
dependencies:
"@chakra-ui/utils": "npm:1.10.4"
peerDependencies:
"@chakra-ui/system": ">=1.0.0"
react: ">=16.8.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/19a447ab6c46675745927113303c0fd33fd69d3ec44fa058c0a121f27bd546cedc088e7cc207d2327c8975f2475ce8e2003db335926c9da1df66fd788774a853
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@ctrl/tinycolor@npm:^3.4.0":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 3.6.1
resolution: "@ctrl/tinycolor@npm:3.6.1"
checksum: 10c0/444d81612cd8c5c802a3d1253df83d5f77d3db87f351861655683a4743990e6b38976bf2e4129591c5a258607b63574b3c7bed702cf6a0eb7912222edf4570e9
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@emotion/babel-plugin@npm:^11.11.0":
version: 11.11.0
resolution: "@emotion/babel-plugin@npm:11.11.0"
dependencies:
"@babel/helper-module-imports": "npm:^7.16.7"
"@babel/runtime": "npm:^7.18.3"
"@emotion/hash": "npm:^0.9.1"
"@emotion/memoize": "npm:^0.8.1"
"@emotion/serialize": "npm:^1.1.2"
babel-plugin-macros: "npm:^3.1.0"
convert-source-map: "npm:^1.5.0"
escape-string-regexp: "npm:^4.0.0"
find-root: "npm:^1.1.0"
source-map: "npm:^0.5.7"
stylis: "npm:4.2.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/89cbb6ec0e52c8ee9c2a4b9889ccd4fc3a75d28091d835bfac6d7c4565d3338621e23af0a85f3bcd133e1cae795c692e1dadada015784d4b0554aa5bb111df43
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@emotion/cache@npm:^11.11.0":
version: 11.11.0
resolution: "@emotion/cache@npm:11.11.0"
dependencies:
"@emotion/memoize": "npm:^0.8.1"
"@emotion/sheet": "npm:^1.2.2"
"@emotion/utils": "npm:^1.2.1"
"@emotion/weak-memoize": "npm:^0.3.1"
stylis: "npm:4.2.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/a23ab5ab2fd08e904698106d58ad3536fed51cc1aa0ef228e95bb640eaf11f560dbd91a395477b0d84e1e3c20150263764b4558517cf6576a89d2d6cc5253688
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@emotion/hash@npm:^0.9.1":
version: 0.9.1
resolution: "@emotion/hash@npm:0.9.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/cdafe5da63fc1137f3db6e232fdcde9188b2b47ee66c56c29137199642a4086f42382d866911cfb4833cae2cc00271ab45cad3946b024f67b527bb7fac7f4c9d
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@emotion/is-prop-valid@npm:^0.8.2":
version: 0.8.8
resolution: "@emotion/is-prop-valid@npm:0.8.8"
dependencies:
"@emotion/memoize": "npm:0.7.4"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/f6be625f067c7fa56a12a4edaf090715616dc4fc7803c87212831f38c969350107b9709b1be54100e53153b18d9fa068eb4bf4f9ac66a37a8edf1bac9b64e279
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@emotion/is-prop-valid@npm:^1.2.2":
version: 1.2.2
resolution: "@emotion/is-prop-valid@npm:1.2.2"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
"@emotion/memoize": "npm:^0.8.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/bb1530dcb4e0e5a4fabb219279f2d0bc35796baf66f6241f98b0d03db1985c890a8cafbea268e0edefd5eeda143dbd5c09a54b5fba74cee8c69b98b13194af50
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@emotion/memoize@npm:0.7.4":
version: 0.7.4
resolution: "@emotion/memoize@npm:0.7.4"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/b2376548fc147b43afd1ff005a80a1a025bd7eb4fb759fdb23e96e5ff290ee8ba16628a332848d600fb91c3cdc319eee5395fa33d8875e5d5a8c4ce18cddc18e
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@emotion/memoize@npm:^0.8.1":
version: 0.8.1
resolution: "@emotion/memoize@npm:0.8.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/dffed372fc3b9fa2ba411e76af22b6bb686fb0cb07694fdfaa6dd2baeb0d5e4968c1a7caa472bfcf06a5997d5e7c7d16b90e993f9a6ffae79a2c3dbdc76dfe78
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@emotion/react@npm:^11.1.4":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 11.11.4
resolution: "@emotion/react@npm:11.11.4"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
"@babel/runtime": "npm:^7.18.3"
"@emotion/babel-plugin": "npm:^11.11.0"
"@emotion/cache": "npm:^11.11.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@emotion/serialize": "npm:^1.1.3"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"@emotion/use-insertion-effect-with-fallbacks": "npm:^1.0.1"
"@emotion/utils": "npm:^1.2.1"
"@emotion/weak-memoize": "npm:^0.3.1"
hoist-non-react-statics: "npm:^3.3.1"
peerDependencies:
react: ">=16.8.0"
peerDependenciesMeta:
"@types/react":
optional: true
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/6df892fd9e04b5c8c37aacfd7f461631e04e00e845edc3c5b2955ab8ad681abf5cd49584101f579427e08b82f2f88369c78d37ae2fe9360a8f68fd4e51b8e448
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@emotion/serialize@npm:^1.1.2, @emotion/serialize@npm:^1.1.3, @emotion/serialize@npm:^1.1.4":
version: 1.1.4
resolution: "@emotion/serialize@npm:1.1.4"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
"@emotion/hash": "npm:^0.9.1"
"@emotion/memoize": "npm:^0.8.1"
"@emotion/unitless": "npm:^0.8.1"
"@emotion/utils": "npm:^1.2.1"
csstype: "npm:^3.0.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/164d936f72382594c47b9c24e67a51c7fc16b83d9a36b84eec5e4cb9bf7be029218a490ef4b44233a1b53423bdb3905d65b597cde3ebba759d40dab7a4c99121
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@emotion/sheet@npm:^1.2.2":
version: 1.2.2
resolution: "@emotion/sheet@npm:1.2.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/69827a1bfa43d7b188f1d8cea42163143a36312543fdade5257c459a2b3efd7ce386aac84ba152bc2517a4f7e54384c04800b26adb382bb284ac7e4ad40e584b
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@emotion/styled@npm:^11.0.0":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 11.11.5
resolution: "@emotion/styled@npm:11.11.5"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
"@babel/runtime": "npm:^7.18.3"
"@emotion/babel-plugin": "npm:^11.11.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@emotion/is-prop-valid": "npm:^1.2.2"
"@emotion/serialize": "npm:^1.1.4"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"@emotion/use-insertion-effect-with-fallbacks": "npm:^1.0.1"
"@emotion/utils": "npm:^1.2.1"
peerDependencies:
"@emotion/react": ^11.0.0-rc.0
react: ">=16.8.0"
peerDependenciesMeta:
"@types/react":
optional: true
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/27da6ad7f5b374d61cfe6647cc2f93ee3ceb1139a51907050576ee30da0a50a27b0bbed45f76889d560d2a8ccf8bc4a4f7126cad3f00127e107c11093dc0a801
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@emotion/unitless@npm:^0.8.1":
version: 0.8.1
resolution: "@emotion/unitless@npm:0.8.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/a1ed508628288f40bfe6dd17d431ed899c067a899fa293a13afe3aed1d70fac0412b8a215fafab0b42829360db687fecd763e5f01a64ddc4a4b58ec3112ff548
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@emotion/use-insertion-effect-with-fallbacks@npm:^1.0.1":
version: 1.0.1
resolution: "@emotion/use-insertion-effect-with-fallbacks@npm:1.0.1"
peerDependencies:
react: ">=16.8.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/a15b2167940e3a908160687b73fc4fcd81e59ab45136b6967f02c7c419d9a149acd22a416b325c389642d4f1c3d33cf4196cad6b618128b55b7c74f6807a240b
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@emotion/utils@npm:^1.2.1":
version: 1.2.1
resolution: "@emotion/utils@npm:1.2.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/db43ca803361740c14dfb1cca1464d10d27f4c8b40d3e8864e6932ccf375d1450778ff4e4eadee03fb97f2aeb18de9fae98294905596a12ff7d4cd1910414d8d
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@emotion/weak-memoize@npm:^0.3.1":
version: 0.3.1
resolution: "@emotion/weak-memoize@npm:0.3.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/ed514b3cb94bbacece4ac2450d98898066c0a0698bdeda256e312405ca53634cb83c75889b25cd8bbbe185c80f4c05a1f0a0091e1875460ba6be61d0334f0b8a
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@esbuild/aix-ppc64@npm:0.19.12":
version: 0.19.12
resolution: "@esbuild/aix-ppc64@npm:0.19.12"
conditions: os=aix & cpu=ppc64
languageName: node
linkType: hard
"@esbuild/android-arm64@npm:0.19.12":
version: 0.19.12
resolution: "@esbuild/android-arm64@npm:0.19.12"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
conditions: os=android & cpu=arm64
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@esbuild/android-arm@npm:0.19.12":
version: 0.19.12
resolution: "@esbuild/android-arm@npm:0.19.12"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
conditions: os=android & cpu=arm
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@esbuild/android-x64@npm:0.19.12":
version: 0.19.12
resolution: "@esbuild/android-x64@npm:0.19.12"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
conditions: os=android & cpu=x64
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@esbuild/darwin-arm64@npm:0.19.12":
version: 0.19.12
resolution: "@esbuild/darwin-arm64@npm:0.19.12"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
conditions: os=darwin & cpu=arm64
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@esbuild/darwin-x64@npm:0.19.12":
version: 0.19.12
resolution: "@esbuild/darwin-x64@npm:0.19.12"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
conditions: os=darwin & cpu=x64
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@esbuild/freebsd-arm64@npm:0.19.12":
version: 0.19.12
resolution: "@esbuild/freebsd-arm64@npm:0.19.12"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
conditions: os=freebsd & cpu=arm64
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@esbuild/freebsd-x64@npm:0.19.12":
version: 0.19.12
resolution: "@esbuild/freebsd-x64@npm:0.19.12"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
conditions: os=freebsd & cpu=x64
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@esbuild/linux-arm64@npm:0.19.12":
version: 0.19.12
resolution: "@esbuild/linux-arm64@npm:0.19.12"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
conditions: os=linux & cpu=arm64
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@esbuild/linux-arm@npm:0.19.12":
version: 0.19.12
resolution: "@esbuild/linux-arm@npm:0.19.12"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
conditions: os=linux & cpu=arm
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@esbuild/linux-ia32@npm:0.19.12":
version: 0.19.12
resolution: "@esbuild/linux-ia32@npm:0.19.12"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
conditions: os=linux & cpu=ia32
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@esbuild/linux-loong64@npm:0.19.12":
version: 0.19.12
resolution: "@esbuild/linux-loong64@npm:0.19.12"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
conditions: os=linux & cpu=loong64
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@esbuild/linux-mips64el@npm:0.19.12":
version: 0.19.12
resolution: "@esbuild/linux-mips64el@npm:0.19.12"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
conditions: os=linux & cpu=mips64el
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@esbuild/linux-ppc64@npm:0.19.12":
version: 0.19.12
resolution: "@esbuild/linux-ppc64@npm:0.19.12"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
conditions: os=linux & cpu=ppc64
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@esbuild/linux-riscv64@npm:0.19.12":
version: 0.19.12
resolution: "@esbuild/linux-riscv64@npm:0.19.12"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
conditions: os=linux & cpu=riscv64
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@esbuild/linux-s390x@npm:0.19.12":
version: 0.19.12
resolution: "@esbuild/linux-s390x@npm:0.19.12"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
conditions: os=linux & cpu=s390x
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@esbuild/linux-x64@npm:0.19.12":
version: 0.19.12
resolution: "@esbuild/linux-x64@npm:0.19.12"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
conditions: os=linux & cpu=x64
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@esbuild/netbsd-x64@npm:0.19.12":
version: 0.19.12
resolution: "@esbuild/netbsd-x64@npm:0.19.12"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
conditions: os=netbsd & cpu=x64
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@esbuild/openbsd-x64@npm:0.19.12":
version: 0.19.12
resolution: "@esbuild/openbsd-x64@npm:0.19.12"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
conditions: os=openbsd & cpu=x64
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@esbuild/sunos-x64@npm:0.19.12":
version: 0.19.12
resolution: "@esbuild/sunos-x64@npm:0.19.12"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
conditions: os=sunos & cpu=x64
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@esbuild/win32-arm64@npm:0.19.12":
version: 0.19.12
resolution: "@esbuild/win32-arm64@npm:0.19.12"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
conditions: os=win32 & cpu=arm64
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@esbuild/win32-ia32@npm:0.19.12":
version: 0.19.12
resolution: "@esbuild/win32-ia32@npm:0.19.12"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
conditions: os=win32 & cpu=ia32
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@esbuild/win32-x64@npm:0.19.12":
version: 0.19.12
resolution: "@esbuild/win32-x64@npm:0.19.12"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
conditions: os=win32 & cpu=x64
languageName: node
linkType: hard
"@eslint-community/eslint-utils@npm:^4.2.0, @eslint-community/eslint-utils@npm:^4.4.0":
version: 4.4.0
resolution: "@eslint-community/eslint-utils@npm:4.4.0"
dependencies:
eslint-visitor-keys: "npm:^3.3.0"
peerDependencies:
eslint: ^6.0.0 || ^7.0.0 || >=8.0.0
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/7e559c4ce59cd3a06b1b5a517b593912e680a7f981ae7affab0d01d709e99cd5647019be8fafa38c350305bc32f1f7d42c7073edde2ab536c745e365f37b607e
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
"@eslint-community/regexpp@npm:^4.10.0, @eslint-community/regexpp@npm:^4.6.1":
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
version: 4.10.0
resolution: "@eslint-community/regexpp@npm:4.10.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/c5f60ef1f1ea7649fa7af0e80a5a79f64b55a8a8fa5086de4727eb4c86c652aedee407a9c143b8995d2c0b2d75c1222bec9ba5d73dbfc1f314550554f0979ef4
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@eslint/eslintrc@npm:^2.1.4":
version: 2.1.4
resolution: "@eslint/eslintrc@npm:2.1.4"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
ajv: "npm:^6.12.4"
debug: "npm:^4.3.2"
espree: "npm:^9.6.0"
globals: "npm:^13.19.0"
ignore: "npm:^5.2.0"
import-fresh: "npm:^3.2.1"
js-yaml: "npm:^4.1.0"
minimatch: "npm:^3.1.2"
strip-json-comments: "npm:^3.1.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/32f67052b81768ae876c84569ffd562491ec5a5091b0c1e1ca1e0f3c24fb42f804952fdd0a137873bc64303ba368a71ba079a6f691cee25beee9722d94cc8573
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@eslint/js@npm:8.57.0":
version: 8.57.0
resolution: "@eslint/js@npm:8.57.0"
checksum: 10c0/9a518bb8625ba3350613903a6d8c622352ab0c6557a59fe6ff6178bf882bf57123f9d92aa826ee8ac3ee74b9c6203fe630e9ee00efb03d753962dcf65ee4bd94
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@graphql-typed-document-node/core@npm:^3.1.1":
version: 3.2.0
resolution: "@graphql-typed-document-node/core@npm:3.2.0"
peerDependencies:
graphql: ^0.8.0 || ^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/94e9d75c1f178bbae8d874f5a9361708a3350c8def7eaeb6920f2c820e82403b7d4f55b3735856d68e145e86c85cbfe2adc444fdc25519cd51f108697e99346c
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Add Turbo to speed up the app, and set up for missing UJS features Oh right, we don't have Rails UJS going on anymore, which is what handled the confirmation prompts for deleting lists. Turbo is the more standard modern solution to that, and should speed up certain pageloads, so let's do it! Here I install the `turbo-rails` gem, then run `rails turbo:install` to install the `@hotwired/turbo-rails` npm package. Then I move `application.js` that's run all on pages but the outfit editor into our section of JS that gets run through the bundler, and add Turbo to it. I had to fix a couple tricky things: 1. The outfit editor page doesn't play nice with being swapped into the document, so I make it require a full page reload instead. 2. Prefetching the Sign In link can cause the wrong `return_to` address to be written to the `session`. (It's a GET request that does, ever so slightly, take its own actions, oops!) As a simple hacky answer, we disallow prefetching on that link. Haven't fixed up the UJS stuff for confirm prompts to use Turbo yet, that's next!
2024-03-13 13:43:48 -07:00
"@hotwired/turbo-rails@npm:^8.0.4":
version: 8.0.4
resolution: "@hotwired/turbo-rails@npm:8.0.4"
dependencies:
"@hotwired/turbo": "npm:^8.0.4"
"@rails/actioncable": "npm:^7.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/c35fdcc79876f3ceaed7100f2e6965bcf9aa647309dce7a6ed685e880ffc1ac475299e00538ecc926addfa4023704c9bd1ea37e70fbef3a77697f7f01d4e344f
Add Turbo to speed up the app, and set up for missing UJS features Oh right, we don't have Rails UJS going on anymore, which is what handled the confirmation prompts for deleting lists. Turbo is the more standard modern solution to that, and should speed up certain pageloads, so let's do it! Here I install the `turbo-rails` gem, then run `rails turbo:install` to install the `@hotwired/turbo-rails` npm package. Then I move `application.js` that's run all on pages but the outfit editor into our section of JS that gets run through the bundler, and add Turbo to it. I had to fix a couple tricky things: 1. The outfit editor page doesn't play nice with being swapped into the document, so I make it require a full page reload instead. 2. Prefetching the Sign In link can cause the wrong `return_to` address to be written to the `session`. (It's a GET request that does, ever so slightly, take its own actions, oops!) As a simple hacky answer, we disallow prefetching on that link. Haven't fixed up the UJS stuff for confirm prompts to use Turbo yet, that's next!
2024-03-13 13:43:48 -07:00
languageName: node
linkType: hard
"@hotwired/turbo@npm:^8.0.4":
version: 8.0.4
resolution: "@hotwired/turbo@npm:8.0.4"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/3e7174d550adf3b9a0a4c45ff5d1b71d47c20de6ae01f646fbbaf8ed447677bd1a5fb6dbd46e95b14645a663fe58a6187c1c6d2a688b0981b5cf437379c5e00a
Add Turbo to speed up the app, and set up for missing UJS features Oh right, we don't have Rails UJS going on anymore, which is what handled the confirmation prompts for deleting lists. Turbo is the more standard modern solution to that, and should speed up certain pageloads, so let's do it! Here I install the `turbo-rails` gem, then run `rails turbo:install` to install the `@hotwired/turbo-rails` npm package. Then I move `application.js` that's run all on pages but the outfit editor into our section of JS that gets run through the bundler, and add Turbo to it. I had to fix a couple tricky things: 1. The outfit editor page doesn't play nice with being swapped into the document, so I make it require a full page reload instead. 2. Prefetching the Sign In link can cause the wrong `return_to` address to be written to the `session`. (It's a GET request that does, ever so slightly, take its own actions, oops!) As a simple hacky answer, we disallow prefetching on that link. Haven't fixed up the UJS stuff for confirm prompts to use Turbo yet, that's next!
2024-03-13 13:43:48 -07:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@humanwhocodes/config-array@npm:^0.11.14":
version: 0.11.14
resolution: "@humanwhocodes/config-array@npm:0.11.14"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@humanwhocodes/object-schema": "npm:^2.0.2"
debug: "npm:^4.3.1"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
minimatch: "npm:^3.0.5"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/66f725b4ee5fdd8322c737cb5013e19fac72d4d69c8bf4b7feb192fcb83442b035b92186f8e9497c220e58b2d51a080f28a73f7899bc1ab288c3be172c467541
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@humanwhocodes/module-importer@npm:^1.0.1":
version: 1.0.1
resolution: "@humanwhocodes/module-importer@npm:1.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/909b69c3b86d482c26b3359db16e46a32e0fb30bd306a3c176b8313b9e7313dba0f37f519de6aa8b0a1921349e505f259d19475e123182416a506d7f87e7f529
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@humanwhocodes/object-schema@npm:^2.0.2":
version: 2.0.3
resolution: "@humanwhocodes/object-schema@npm:2.0.3"
checksum: 10c0/80520eabbfc2d32fe195a93557cef50dfe8c8905de447f022675aaf66abc33ae54098f5ea78548d925aa671cd4ab7c7daa5ad704fe42358c9b5e7db60f80696c
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@loadable/component@npm:^5.12.0":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 5.16.4
resolution: "@loadable/component@npm:5.16.4"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@babel/runtime": "npm:^7.12.18"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
hoist-non-react-statics: "npm:^3.3.1"
react-is: "npm:^16.12.0"
peerDependencies:
react: ^16.3.0 || ^17.0.0 || ^18.0.0
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/5d12056178232773e5fdd9ef218858991b97ff6cfece5902a0fa7243580f964545c9c013053c61bcdb8aaab0b54ac0075e55a900d976671679d76872c559f4a4
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@nodelib/fs.scandir@npm:2.1.5":
version: 2.1.5
resolution: "@nodelib/fs.scandir@npm:2.1.5"
dependencies:
"@nodelib/fs.stat": "npm:2.0.5"
run-parallel: "npm:^1.1.9"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/732c3b6d1b1e967440e65f284bd06e5821fedf10a1bea9ed2bb75956ea1f30e08c44d3def9d6a230666574edbaf136f8cfd319c14fd1f87c66e6a44449afb2eb
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@nodelib/fs.stat@npm:2.0.5, @nodelib/fs.stat@npm:^2.0.2":
version: 2.0.5
resolution: "@nodelib/fs.stat@npm:2.0.5"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/88dafe5e3e29a388b07264680dc996c17f4bda48d163a9d4f5c1112979f0ce8ec72aa7116122c350b4e7976bc5566dc3ddb579be1ceaacc727872eb4ed93926d
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@nodelib/fs.walk@npm:^1.2.3, @nodelib/fs.walk@npm:^1.2.8":
version: 1.2.8
resolution: "@nodelib/fs.walk@npm:1.2.8"
dependencies:
"@nodelib/fs.scandir": "npm:2.1.5"
fastq: "npm:^1.6.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/db9de047c3bb9b51f9335a7bb46f4fcfb6829fb628318c12115fbaf7d369bfce71c15b103d1fc3b464812d936220ee9bc1c8f762d032c9f6be9acc99249095b1
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@popperjs/core@npm:^2.9.3":
version: 2.11.8
resolution: "@popperjs/core@npm:2.11.8"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/4681e682abc006d25eb380d0cf3efc7557043f53b6aea7a5057d0d1e7df849a00e281cd8ea79c902a35a414d7919621fc2ba293ecec05f413598e0b23d5a1e63
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Add Turbo to speed up the app, and set up for missing UJS features Oh right, we don't have Rails UJS going on anymore, which is what handled the confirmation prompts for deleting lists. Turbo is the more standard modern solution to that, and should speed up certain pageloads, so let's do it! Here I install the `turbo-rails` gem, then run `rails turbo:install` to install the `@hotwired/turbo-rails` npm package. Then I move `application.js` that's run all on pages but the outfit editor into our section of JS that gets run through the bundler, and add Turbo to it. I had to fix a couple tricky things: 1. The outfit editor page doesn't play nice with being swapped into the document, so I make it require a full page reload instead. 2. Prefetching the Sign In link can cause the wrong `return_to` address to be written to the `session`. (It's a GET request that does, ever so slightly, take its own actions, oops!) As a simple hacky answer, we disallow prefetching on that link. Haven't fixed up the UJS stuff for confirm prompts to use Turbo yet, that's next!
2024-03-13 13:43:48 -07:00
"@rails/actioncable@npm:^7.0":
version: 7.1.3
resolution: "@rails/actioncable@npm:7.1.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/6019097498387a9c0684df0be380182820a0480173e05a5c5a830cef6cf3e40c9ec75b834af0396b0f57b4e658891c820163e84b9f2bd1ac293c90f5a12ce488
Add Turbo to speed up the app, and set up for missing UJS features Oh right, we don't have Rails UJS going on anymore, which is what handled the confirmation prompts for deleting lists. Turbo is the more standard modern solution to that, and should speed up certain pageloads, so let's do it! Here I install the `turbo-rails` gem, then run `rails turbo:install` to install the `@hotwired/turbo-rails` npm package. Then I move `application.js` that's run all on pages but the outfit editor into our section of JS that gets run through the bundler, and add Turbo to it. I had to fix a couple tricky things: 1. The outfit editor page doesn't play nice with being swapped into the document, so I make it require a full page reload instead. 2. Prefetching the Sign In link can cause the wrong `return_to` address to be written to the `session`. (It's a GET request that does, ever so slightly, take its own actions, oops!) As a simple hacky answer, we disallow prefetching on that link. Haven't fixed up the UJS stuff for confirm prompts to use Turbo yet, that's next!
2024-03-13 13:43:48 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"@reach/alert@npm:0.13.2":
version: 0.13.2
resolution: "@reach/alert@npm:0.13.2"
dependencies:
"@reach/utils": "npm:0.13.2"
"@reach/visually-hidden": "npm:0.13.2"
prop-types: "npm:^15.7.2"
tslib: "npm:^2.1.0"
peerDependencies:
react: ^16.8.0 || 17.x
react-dom: ^16.8.0 || 17.x
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/b7511c635cabfa0de66370a43ad0de2f3cf21c3f1c8ecdf6242a29b3cecd6e0a61caf427d1dcd2e0f9ad839e91f511bac663d05f1b88eb1f1a476074ff081606
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@reach/utils@npm:0.13.2":
version: 0.13.2
resolution: "@reach/utils@npm:0.13.2"
dependencies:
"@types/warning": "npm:^3.0.0"
tslib: "npm:^2.1.0"
warning: "npm:^4.0.3"
peerDependencies:
react: ^16.8.0 || 17.x
react-dom: ^16.8.0 || 17.x
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/b8d187b87b45fc908051c16b6ee13ee2df5b85c364f461057b7dccfceb51159bb61159d031ebfa43b841f6e23f6321d3a73f772b2d795ec197ac0b4556dbbe4f
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@reach/visually-hidden@npm:0.13.2":
version: 0.13.2
resolution: "@reach/visually-hidden@npm:0.13.2"
dependencies:
prop-types: "npm:^15.7.2"
tslib: "npm:^2.1.0"
peerDependencies:
react: ^16.8.0 || 17.x
react-dom: ^16.8.0 || 17.x
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/60a01b441dea6e7e99629a56f2c12ee48c8bd3a7d1c67b6218d41f4543c2ed49267e8552a17d163475bc1092fcbc08e16249a958b35ebd29ead4c1c5abb3a73a
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@remix-run/router@npm:1.16.0":
version: 1.16.0
resolution: "@remix-run/router@npm:1.16.0"
checksum: 10c0/234e66b4d7266aff6d111a43f5560f00ffdc91de0b5cd447f1fdf1de1a8b3a6ac326eb52302356e23b095e71a8f4da914e40239af5f121de2ec2994f101b8db0
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@sentry/browser@npm:5.30.0":
version: 5.30.0
resolution: "@sentry/browser@npm:5.30.0"
dependencies:
"@sentry/core": "npm:5.30.0"
"@sentry/types": "npm:5.30.0"
"@sentry/utils": "npm:5.30.0"
tslib: "npm:^1.9.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/6793e1b49a8cdb1f025115bcc591bf67c97b6515f62a33ffcbb7b1ab66e459ebc471797d02e471be1ebf14092b56eb25ed914f043962388cc224bc961e334a17
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@sentry/core@npm:5.30.0":
version: 5.30.0
resolution: "@sentry/core@npm:5.30.0"
dependencies:
"@sentry/hub": "npm:5.30.0"
"@sentry/minimal": "npm:5.30.0"
"@sentry/types": "npm:5.30.0"
"@sentry/utils": "npm:5.30.0"
tslib: "npm:^1.9.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/6407b9c2a6a56f90c198f5714b3257df24d89d1b4ca6726bd44760d0adabc25798b69fef2c88ccea461c7e79e3c78861aaebfd51fd3cb892aee656c3f7e11801
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@sentry/hub@npm:5.30.0":
version: 5.30.0
resolution: "@sentry/hub@npm:5.30.0"
dependencies:
"@sentry/types": "npm:5.30.0"
"@sentry/utils": "npm:5.30.0"
tslib: "npm:^1.9.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/386c91d06aa44be0465fc11330d748a113e464d41cd562a9e1d222a682cbcb14e697a3e640953e7a0239997ad8a02b223a0df3d9e1d8816cb823fd3613be3e2f
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@sentry/minimal@npm:5.30.0":
version: 5.30.0
resolution: "@sentry/minimal@npm:5.30.0"
dependencies:
"@sentry/hub": "npm:5.30.0"
"@sentry/types": "npm:5.30.0"
tslib: "npm:^1.9.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/34ec05503de46d01f98c94701475d5d89cc044892c86ccce30e01f62f28344eb23b718e7cf573815e46f30a4ac9da3129bed9b3d20c822938acfb40cbe72437b
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@sentry/react@npm:^5.30.0":
version: 5.30.0
resolution: "@sentry/react@npm:5.30.0"
dependencies:
"@sentry/browser": "npm:5.30.0"
"@sentry/minimal": "npm:5.30.0"
"@sentry/types": "npm:5.30.0"
"@sentry/utils": "npm:5.30.0"
hoist-non-react-statics: "npm:^3.3.2"
tslib: "npm:^1.9.3"
peerDependencies:
react: 15.x || 16.x || 17.x
react-dom: 15.x || 16.x || 17.x
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/2a80eb40038ac3d9b2ff9346cfecb39a248a14fedfc45ca5f32a4194620ea6dccf9f53ccc43c6d151687178e4741f80e4218c5e0ac66e174c341088a30517abf
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@sentry/tracing@npm:^5.30.0":
version: 5.30.0
resolution: "@sentry/tracing@npm:5.30.0"
dependencies:
"@sentry/hub": "npm:5.30.0"
"@sentry/minimal": "npm:5.30.0"
"@sentry/types": "npm:5.30.0"
"@sentry/utils": "npm:5.30.0"
tslib: "npm:^1.9.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/46830265bc54a3203d7d9f0d8d9f2f7d9d2c6a977e07ccdae317fa3ea29c388b904b3bef28f7a0ba9c074845d67feab63c6d3c0ddce9aeb275b6c966253fb415
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@sentry/types@npm:5.30.0":
version: 5.30.0
resolution: "@sentry/types@npm:5.30.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/99c6e55c0a82c8ca95be2e9dbb35f581b29e4ff7af74b23bc62b690de4e35febfa15868184a2303480ef86babd4fea5273cf3b5ddf4a27685b841a72f13a0c88
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@sentry/utils@npm:5.30.0":
version: 5.30.0
resolution: "@sentry/utils@npm:5.30.0"
dependencies:
"@sentry/types": "npm:5.30.0"
tslib: "npm:^1.9.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/ca8eebfea7ac7db6d16f6c0b8a66ac62587df12a79ce9d0d8393f4d69880bb8d40d438f9810f7fb107a9880fe0d68bbf797b89cbafd113e89a0829eb06b205f8
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@tanstack/query-core@npm:5.32.1":
version: 5.32.1
resolution: "@tanstack/query-core@npm:5.32.1"
checksum: 10c0/2ae228c6bc6e5415c7345785c9b2680811e42aaf5b0183612546127ba67ccfe26adda5271845a6d40137c642f73e23909feb357e1e2c2423b4caf3a2d82868dc
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@tanstack/react-query@npm:^5.4.3":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 5.32.1
resolution: "@tanstack/react-query@npm:5.32.1"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@tanstack/query-core": "npm:5.32.1"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
peerDependencies:
react: ^18.0.0
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/fdf5fb746a8e6b4954c4f7e83709bb871d6ff4d936d0b5adfc4b6b18953e0250179a8e39e7df9cdfc0915362a24f3d1309f01ef2c31128d5ff4272666f77461a
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
"@types/json-schema@npm:^7.0.15":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 7.0.15
resolution: "@types/json-schema@npm:7.0.15"
checksum: 10c0/a996a745e6c5d60292f36731dd41341339d4eeed8180bb09226e5c8d23759067692b1d88e5d91d72ee83dfc00d3aca8e7bd43ea120516c17922cbcb7c3e252db
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@types/lodash.mergewith@npm:4.6.6":
version: 4.6.6
resolution: "@types/lodash.mergewith@npm:4.6.6"
dependencies:
"@types/lodash": "npm:*"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/d8ab2d6cb0754e37240492fca1f245ebafc9f9c1342de323bff0a08006445021821b7050c6eb83582454d2ec0424459d8d28886ad30656dd04d8df34121184d0
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@types/lodash@npm:*":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 4.17.0
resolution: "@types/lodash@npm:4.17.0"
checksum: 10c0/4c5b41c9a6c41e2c05d08499e96f7940bcf194dcfa84356235b630da920c2a5e05f193618cea76006719bec61c76617dff02defa9d29934f9f6a76a49291bd8f
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@types/parse-json@npm:^4.0.0":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 4.0.2
resolution: "@types/parse-json@npm:4.0.2"
checksum: 10c0/b1b863ac34a2c2172fbe0807a1ec4d5cb684e48d422d15ec95980b81475fac4fdb3768a8b13eef39130203a7c04340fc167bae057c7ebcafd7dec9fe6c36aeb1
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@types/prop-types@npm:*":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 15.7.12
resolution: "@types/prop-types@npm:15.7.12"
checksum: 10c0/1babcc7db6a1177779f8fde0ccc78d64d459906e6ef69a4ed4dd6339c920c2e05b074ee5a92120fe4e9d9f1a01c952f843ebd550bee2332fc2ef81d1706878f8
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@types/react@npm:^17.0.15":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 17.0.80
resolution: "@types/react@npm:17.0.80"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
"@types/prop-types": "npm:*"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@types/scheduler": "npm:^0.16"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
csstype: "npm:^3.0.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/c5d2862564212a41a327ea9c7e70b9d3996d9b0f67971d39519d42d1f3ae6ddf76b183457b7b0be9d7b5d6ff0aaeed5711448423406d20018f082077c984eec4
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@types/scheduler@npm:^0.16":
version: 0.16.8
resolution: "@types/scheduler@npm:0.16.8"
checksum: 10c0/f86de504945b8fc41b1f391f847444d542e2e4067cf7e5d9bfeb5d2d2393d3203b1161bc0ef3b1e104d828dabfb60baf06e8d2c27e27ff7e8258e6e618d8c4ec
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
"@types/semver@npm:^7.5.8":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 7.5.8
resolution: "@types/semver@npm:7.5.8"
checksum: 10c0/8663ff927234d1c5fcc04b33062cb2b9fcfbe0f5f351ed26c4d1e1581657deebd506b41ff7fdf89e787e3d33ce05854bc01686379b89e9c49b564c4cfa988efa
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@types/warning@npm:^3.0.0":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 3.0.3
resolution: "@types/warning@npm:3.0.3"
checksum: 10c0/82c1235bd05d7f6940f80012404844e225d589ad338aa4585b231a2c8deacc695b683f4168757c82c10047b81854cbeaaeefd60536dd67bb48f8a65e20410652
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
"@typescript-eslint/eslint-plugin@npm:^7.8.0":
version: 7.8.0
resolution: "@typescript-eslint/eslint-plugin@npm:7.8.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
"@eslint-community/regexpp": "npm:^4.10.0"
"@typescript-eslint/scope-manager": "npm:7.8.0"
"@typescript-eslint/type-utils": "npm:7.8.0"
"@typescript-eslint/utils": "npm:7.8.0"
"@typescript-eslint/visitor-keys": "npm:7.8.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
debug: "npm:^4.3.4"
graphemer: "npm:^1.4.0"
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
ignore: "npm:^5.3.1"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
natural-compare: "npm:^1.4.0"
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
semver: "npm:^7.6.0"
ts-api-utils: "npm:^1.3.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
peerDependencies:
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
"@typescript-eslint/parser": ^7.0.0
eslint: ^8.56.0
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
peerDependenciesMeta:
typescript:
optional: true
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
checksum: 10c0/37ca22620d1834ff0baa28fa4b8fd92039a3903cb95748353de32d56bae2a81ce50d1bbaed27487eebc884e0a0f9387fcb0f1647593e4e6df5111ef674afa9f0
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
"@typescript-eslint/parser@npm:^7.8.0":
version: 7.8.0
resolution: "@typescript-eslint/parser@npm:7.8.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
"@typescript-eslint/scope-manager": "npm:7.8.0"
"@typescript-eslint/types": "npm:7.8.0"
"@typescript-eslint/typescript-estree": "npm:7.8.0"
"@typescript-eslint/visitor-keys": "npm:7.8.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
debug: "npm:^4.3.4"
peerDependencies:
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
eslint: ^8.56.0
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
peerDependenciesMeta:
typescript:
optional: true
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
checksum: 10c0/0dd994c1b31b810c25e1b755b8d352debb7bf21a31f9a91acaec34acf4e471320bcceaa67cf64c110c0b8f5fac10a037dbabac6ec423e17adf037e59a7bce9c1
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
"@typescript-eslint/scope-manager@npm:7.8.0":
version: 7.8.0
resolution: "@typescript-eslint/scope-manager@npm:7.8.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
"@typescript-eslint/types": "npm:7.8.0"
"@typescript-eslint/visitor-keys": "npm:7.8.0"
checksum: 10c0/c253b98e96d4bf0375f473ca2c4d081726f1fd926cdfa65ee14c9ee99cca8eddb763b2d238ac365daa7246bef21b0af38180d04e56e9df7443c0e6f8474d097c
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
"@typescript-eslint/type-utils@npm:7.8.0":
version: 7.8.0
resolution: "@typescript-eslint/type-utils@npm:7.8.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
"@typescript-eslint/typescript-estree": "npm:7.8.0"
"@typescript-eslint/utils": "npm:7.8.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
debug: "npm:^4.3.4"
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
ts-api-utils: "npm:^1.3.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
peerDependencies:
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
eslint: ^8.56.0
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
peerDependenciesMeta:
typescript:
optional: true
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
checksum: 10c0/00f6315626b64f7dbc1f7fba6f365321bb8d34141ed77545b2a07970e59a81dbdf768c1e024225ea00953750d74409ddd8a16782fc4a39261e507c04192dacab
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
"@typescript-eslint/types@npm:7.8.0":
version: 7.8.0
resolution: "@typescript-eslint/types@npm:7.8.0"
checksum: 10c0/b2fdbfc21957bfa46f7d8809b607ad8c8b67c51821d899064d09392edc12f28b2318a044f0cd5d523d782e84e8f0558778877944964cf38e139f88790cf9d466
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
"@typescript-eslint/typescript-estree@npm:7.8.0":
version: 7.8.0
resolution: "@typescript-eslint/typescript-estree@npm:7.8.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
"@typescript-eslint/types": "npm:7.8.0"
"@typescript-eslint/visitor-keys": "npm:7.8.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
debug: "npm:^4.3.4"
globby: "npm:^11.1.0"
is-glob: "npm:^4.0.3"
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
minimatch: "npm:^9.0.4"
semver: "npm:^7.6.0"
ts-api-utils: "npm:^1.3.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
peerDependenciesMeta:
typescript:
optional: true
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
checksum: 10c0/1690b62679685073dcb0f62499f0b52b445b37ae6e12d02aa4acbafe3fb023cf999b01f714b6282e88f84fd934fe3e2eefb21a64455d19c348d22bbc68ca8e47
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
"@typescript-eslint/utils@npm:7.8.0":
version: 7.8.0
resolution: "@typescript-eslint/utils@npm:7.8.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
"@eslint-community/eslint-utils": "npm:^4.4.0"
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
"@types/json-schema": "npm:^7.0.15"
"@types/semver": "npm:^7.5.8"
"@typescript-eslint/scope-manager": "npm:7.8.0"
"@typescript-eslint/types": "npm:7.8.0"
"@typescript-eslint/typescript-estree": "npm:7.8.0"
semver: "npm:^7.6.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
peerDependencies:
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
eslint: ^8.56.0
checksum: 10c0/31fb58388d15b082eb7bd5bce889cc11617aa1131dfc6950471541b3df64c82d1c052e2cccc230ca4ae80456d4f63a3e5dccb79899a8f3211ce36c089b7d7640
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
"@typescript-eslint/visitor-keys@npm:7.8.0":
version: 7.8.0
resolution: "@typescript-eslint/visitor-keys@npm:7.8.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
"@typescript-eslint/types": "npm:7.8.0"
eslint-visitor-keys: "npm:^3.4.3"
checksum: 10c0/5892fb5d9c58efaf89adb225f7dbbb77f9363961f2ff420b6b130bdd102dddd7aa8a16c46a5a71c19889d27b781e966119a89270555ea2cb5653a04d8994123d
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@ungap/structured-clone@npm:^1.2.0":
version: 1.2.0
resolution: "@ungap/structured-clone@npm:1.2.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/8209c937cb39119f44eb63cf90c0b73e7c754209a6411c707be08e50e29ee81356dca1a848a405c8bdeebfe2f5e4f831ad310ae1689eeef65e7445c090c6657d
languageName: node
linkType: hard
"@wry/caches@npm:^1.0.0":
version: 1.0.1
resolution: "@wry/caches@npm:1.0.1"
dependencies:
tslib: "npm:^2.3.0"
checksum: 10c0/a7bca3377f1131d3f1080f2e39d0692c9d1ca86bfd55734786f167f46aad28a4c8e772107324e8319843fb8068fdf98abcdea376d8a589316b1f0cdadf81f8b1
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@wry/context@npm:^0.7.0":
version: 0.7.4
resolution: "@wry/context@npm:0.7.4"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
tslib: "npm:^2.3.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/6cc8249b8ba195cda7643bffb30969e33d54a99f118a29dd12f1c34064ee0adf04253cfa0ba5b9893afde0a9588745828962877b9585106f7488e8299757638b
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@wry/equality@npm:^0.1.2":
version: 0.1.11
resolution: "@wry/equality@npm:0.1.11"
dependencies:
tslib: "npm:^1.9.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/a740b9d449eeb2d3cd251d5a8a1b739af4142a505e66eefc30a648ef2752b411220db40a0f78b97ecf3c2d8f8a2e9450ce0d1ff8e7679c8d89124fb696aea8fe
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@wry/equality@npm:^0.5.6":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 0.5.7
resolution: "@wry/equality@npm:0.5.7"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
tslib: "npm:^2.3.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/8503ff6d4eb80f303d1387e71e51da59ccfc2160fa6d464618be80946fe43a654ea73f0c5b90d659fc4dfc3e38cbbdd6650d595fe5865be476636e444470853e
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"@wry/trie@npm:^0.4.3":
version: 0.4.3
resolution: "@wry/trie@npm:0.4.3"
dependencies:
tslib: "npm:^2.3.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/1a14edba595b1967d0cf38208c2660b2952a8e8a649bb669b67907df48f602c7f2acbe16c1e1b115afa7d7effb9f1a4dbde38eef16ee92e7521a511262a53281
languageName: node
linkType: hard
"@wry/trie@npm:^0.5.0":
version: 0.5.0
resolution: "@wry/trie@npm:0.5.0"
dependencies:
tslib: "npm:^2.3.0"
checksum: 10c0/8c8cfcac96ba4bc69dabf02740e19e613f501b398e80bacc32cd95e87228f75ecb41cd1a76a65abae9756c0f61ab3536e0da52de28857456f9381ffdf5995d3e
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"accepts@npm:~1.3.8":
version: 1.3.8
resolution: "accepts@npm:1.3.8"
dependencies:
mime-types: "npm:~2.1.34"
negotiator: "npm:0.6.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/3a35c5f5586cfb9a21163ca47a5f77ac34fa8ceb5d17d2fa2c0d81f41cbd7f8c6fa52c77e2c039acc0f4d09e71abdc51144246900f6bef5e3c4b333f77d89362
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"acorn-jsx@npm:^5.3.2":
version: 5.3.2
resolution: "acorn-jsx@npm:5.3.2"
peerDependencies:
acorn: ^6.0.0 || ^7.0.0 || ^8.0.0
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/4c54868fbef3b8d58927d5e33f0a4de35f59012fe7b12cf9dfbb345fb8f46607709e1c4431be869a23fb63c151033d84c4198fa9f79385cec34fcb1dd53974c1
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"acorn@npm:^8.9.0":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 8.11.3
resolution: "acorn@npm:8.11.3"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
bin:
acorn: bin/acorn
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/3ff155f8812e4a746fee8ecff1f227d527c4c45655bb1fad6347c3cb58e46190598217551b1500f18542d2bbe5c87120cb6927f5a074a59166fbdd9468f0a299
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"ajv@npm:^6.12.4":
version: 6.12.6
resolution: "ajv@npm:6.12.6"
dependencies:
fast-deep-equal: "npm:^3.1.1"
fast-json-stable-stringify: "npm:^2.0.0"
json-schema-traverse: "npm:^0.4.1"
uri-js: "npm:^4.2.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/41e23642cbe545889245b9d2a45854ebba51cda6c778ebced9649420d9205f2efb39cb43dbc41e358409223b1ea43303ae4839db682c848b891e4811da1a5a71
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"ansi-regex@npm:^5.0.1":
version: 5.0.1
resolution: "ansi-regex@npm:5.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/9a64bb8627b434ba9327b60c027742e5d17ac69277960d041898596271d992d4d52ba7267a63ca10232e29f6107fc8a835f6ce8d719b88c5f8493f8254813737
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"ansi-styles@npm:^3.2.1":
version: 3.2.1
resolution: "ansi-styles@npm:3.2.1"
dependencies:
color-convert: "npm:^1.9.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/ece5a8ef069fcc5298f67e3f4771a663129abd174ea2dfa87923a2be2abf6cd367ef72ac87942da00ce85bd1d651d4cd8595aebdb1b385889b89b205860e977b
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"ansi-styles@npm:^4.1.0":
version: 4.3.0
resolution: "ansi-styles@npm:4.3.0"
dependencies:
color-convert: "npm:^2.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/895a23929da416f2bd3de7e9cb4eabd340949328ab85ddd6e484a637d8f6820d485f53933446f5291c3b760cbc488beb8e88573dd0f9c7daf83dccc8fe81b041
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"apollo-link-persisted-queries@npm:^0.2.2":
version: 0.2.5
resolution: "apollo-link-persisted-queries@npm:0.2.5"
dependencies:
apollo-link: "npm:^1.2.1"
hash.js: "npm:^1.1.7"
peerDependencies:
graphql: ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0 || ^16.0.0
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/36fb755585b870d25468ca6f698ad755c557ef0157cb5a6f7fbb7560bd89e45cc470e2de04240a386dd1e2e8949738f83a4418eee8ee3dc54dcf69648a63601b
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"apollo-link@npm:^1.2.1":
version: 1.2.14
resolution: "apollo-link@npm:1.2.14"
dependencies:
apollo-utilities: "npm:^1.3.0"
ts-invariant: "npm:^0.4.0"
tslib: "npm:^1.9.3"
zen-observable-ts: "npm:^0.8.21"
peerDependencies:
graphql: ^0.11.3 || ^0.12.3 || ^0.13.0 || ^14.0.0 || ^15.0.0
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/6a43ed4bb8491c8ff47450a817e59195bff6b8ebc0c415b5caa177dae96e7dd30112323a32176a14a31cc3b3edd8c4be619325cdecb5fad4bccbd255143927c3
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"apollo-utilities@npm:^1.3.0":
version: 1.3.4
resolution: "apollo-utilities@npm:1.3.4"
dependencies:
"@wry/equality": "npm:^0.1.2"
fast-json-stable-stringify: "npm:^2.0.0"
ts-invariant: "npm:^0.4.0"
tslib: "npm:^1.10.0"
peerDependencies:
graphql: ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/071f2bfd3b62457c688aec8f7c92e3831e05ace5a65699608cbdda5b03bd287f407654fbd526639efaa4dc2db4d39763cccefb1786f4cd14dfa48f4ab79f3b8b
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"argparse@npm:^2.0.1":
version: 2.0.1
resolution: "argparse@npm:2.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/c5640c2d89045371c7cedd6a70212a04e360fd34d6edeae32f6952c63949e3525ea77dbec0289d8213a99bbaeab5abfa860b5c12cf88a2e6cf8106e90dd27a7e
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"aria-hidden@npm:^1.1.1":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 1.2.4
resolution: "aria-hidden@npm:1.2.4"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
tslib: "npm:^2.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/8abcab2e1432efc4db415e97cb3959649ddf52c8fc815d7384f43f3d3abf56f1c12852575d00df9a8927f421d7e0712652dd5f8db244ea57634344e29ecfc74a
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"aria-query@npm:^5.3.0":
version: 5.3.0
resolution: "aria-query@npm:5.3.0"
dependencies:
dequal: "npm:^2.0.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/2bff0d4eba5852a9dd578ecf47eaef0e82cc52569b48469b0aac2db5145db0b17b7a58d9e01237706d1e14b7a1b0ac9b78e9c97027ad97679dd8f91b85da1469
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"array-buffer-byte-length@npm:^1.0.1":
version: 1.0.1
resolution: "array-buffer-byte-length@npm:1.0.1"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
call-bind: "npm:^1.0.5"
is-array-buffer: "npm:^3.0.4"
checksum: 10c0/f5cdf54527cd18a3d2852ddf73df79efec03829e7373a8322ef5df2b4ef546fb365c19c71d6b42d641cb6bfe0f1a2f19bc0ece5b533295f86d7c3d522f228917
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"array-flatten@npm:1.1.1":
version: 1.1.1
resolution: "array-flatten@npm:1.1.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/806966c8abb2f858b08f5324d9d18d7737480610f3bd5d3498aaae6eb5efdc501a884ba019c9b4a8f02ff67002058749d05548fd42fa8643f02c9c7f22198b91
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"array-includes@npm:^3.1.6, array-includes@npm:^3.1.7":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 3.1.8
resolution: "array-includes@npm:3.1.8"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
call-bind: "npm:^1.0.7"
define-properties: "npm:^1.2.1"
es-abstract: "npm:^1.23.2"
es-object-atoms: "npm:^1.0.0"
get-intrinsic: "npm:^1.2.4"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
is-string: "npm:^1.0.7"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/5b1004d203e85873b96ddc493f090c9672fd6c80d7a60b798da8a14bff8a670ff95db5aafc9abc14a211943f05220dacf8ea17638ae0af1a6a47b8c0b48ce370
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"array-union@npm:^2.1.0":
version: 2.1.0
resolution: "array-union@npm:2.1.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/429897e68110374f39b771ec47a7161fc6a8fc33e196857c0a396dc75df0b5f65e4d046674db764330b6bb66b39ef48dd7c53b6a2ee75cfb0681e0c1a7033962
languageName: node
linkType: hard
"array.prototype.findlast@npm:^1.2.4":
version: 1.2.5
resolution: "array.prototype.findlast@npm:1.2.5"
dependencies:
call-bind: "npm:^1.0.7"
define-properties: "npm:^1.2.1"
es-abstract: "npm:^1.23.2"
es-errors: "npm:^1.3.0"
es-object-atoms: "npm:^1.0.0"
es-shim-unscopables: "npm:^1.0.2"
checksum: 10c0/ddc952b829145ab45411b9d6adcb51a8c17c76bf89c9dd64b52d5dffa65d033da8c076ed2e17091779e83bc892b9848188d7b4b33453c5565e65a92863cb2775
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"array.prototype.flat@npm:^1.3.1":
version: 1.3.2
resolution: "array.prototype.flat@npm:1.3.2"
dependencies:
call-bind: "npm:^1.0.2"
define-properties: "npm:^1.2.0"
es-abstract: "npm:^1.22.1"
es-shim-unscopables: "npm:^1.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/a578ed836a786efbb6c2db0899ae80781b476200617f65a44846cb1ed8bd8b24c8821b83703375d8af639c689497b7b07277060024b9919db94ac3e10dc8a49b
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"array.prototype.flatmap@npm:^1.3.2":
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
version: 1.3.2
resolution: "array.prototype.flatmap@npm:1.3.2"
dependencies:
call-bind: "npm:^1.0.2"
define-properties: "npm:^1.2.0"
es-abstract: "npm:^1.22.1"
es-shim-unscopables: "npm:^1.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/67b3f1d602bb73713265145853128b1ad77cc0f9b833c7e1e056b323fbeac41a4ff1c9c99c7b9445903caea924d9ca2450578d9011913191aa88cc3c3a4b54f4
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"array.prototype.toreversed@npm:^1.1.2":
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
version: 1.1.2
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
resolution: "array.prototype.toreversed@npm:1.1.2"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
call-bind: "npm:^1.0.2"
define-properties: "npm:^1.2.0"
es-abstract: "npm:^1.22.1"
es-shim-unscopables: "npm:^1.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/2b7627ea85eae1e80ecce665a500cc0f3355ac83ee4a1a727562c7c2a1d5f1c0b4dd7b65c468ec6867207e452ba01256910a2c0b41486bfdd11acf875a7a3435
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"array.prototype.tosorted@npm:^1.1.3":
version: 1.1.3
resolution: "array.prototype.tosorted@npm:1.1.3"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
call-bind: "npm:^1.0.5"
define-properties: "npm:^1.2.1"
es-abstract: "npm:^1.22.3"
es-errors: "npm:^1.1.0"
es-shim-unscopables: "npm:^1.0.2"
checksum: 10c0/a27e1ca51168ecacf6042901f5ef021e43c8fa04b6c6b6f2a30bac3645cd2b519cecbe0bc45db1b85b843f64dc3207f0268f700b4b9fbdec076d12d432cf0865
languageName: node
linkType: hard
"arraybuffer.prototype.slice@npm:^1.0.3":
version: 1.0.3
resolution: "arraybuffer.prototype.slice@npm:1.0.3"
dependencies:
array-buffer-byte-length: "npm:^1.0.1"
call-bind: "npm:^1.0.5"
define-properties: "npm:^1.2.1"
es-abstract: "npm:^1.22.3"
es-errors: "npm:^1.2.1"
get-intrinsic: "npm:^1.2.3"
is-array-buffer: "npm:^3.0.4"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
is-shared-array-buffer: "npm:^1.0.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/d32754045bcb2294ade881d45140a5e52bda2321b9e98fa514797b7f0d252c4c5ab0d1edb34112652c62fa6a9398def568da63a4d7544672229afea283358c36
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"ast-types-flow@npm:^0.0.8":
version: 0.0.8
resolution: "ast-types-flow@npm:0.0.8"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/f2a0ba8055353b743c41431974521e5e852a9824870cd6fce2db0e538ac7bf4da406bbd018d109af29ff3f8f0993f6a730c9eddbd0abd031fbcb29ca75c1014e
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"available-typed-arrays@npm:^1.0.7":
version: 1.0.7
resolution: "available-typed-arrays@npm:1.0.7"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
possible-typed-array-names: "npm:^1.0.0"
checksum: 10c0/d07226ef4f87daa01bd0fe80f8f310982e345f372926da2e5296aecc25c41cab440916bbaa4c5e1034b453af3392f67df5961124e4b586df1e99793a1374bdb2
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"axe-core@npm:=4.7.0":
version: 4.7.0
resolution: "axe-core@npm:4.7.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/89ac5712b5932ac7d23398b4cb5ba081c394a086e343acc68ba49c83472706e18e0799804e8388c779dcdacc465377deb29f2714241d3fbb389cf3a6b275c9ba
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"axobject-query@npm:^3.2.1":
version: 3.2.1
resolution: "axobject-query@npm:3.2.1"
dependencies:
dequal: "npm:^2.0.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/f7debc2012e456139b57d888c223f6d3cb4b61eb104164a85e3d346273dd6ef0bc9a04b6660ca9407704a14a8e05fa6b6eb9d55f44f348c7210de7ffb350c3a7
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"babel-plugin-macros@npm:^3.1.0":
version: 3.1.0
resolution: "babel-plugin-macros@npm:3.1.0"
dependencies:
"@babel/runtime": "npm:^7.12.5"
cosmiconfig: "npm:^7.0.0"
resolve: "npm:^1.19.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/c6dfb15de96f67871d95bd2e8c58b0c81edc08b9b087dc16755e7157f357dc1090a8dc60ebab955e92587a9101f02eba07e730adc253a1e4cf593ca3ebd3839c
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"balanced-match@npm:^1.0.0":
version: 1.0.2
resolution: "balanced-match@npm:1.0.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/9308baf0a7e4838a82bbfd11e01b1cb0f0cf2893bc1676c27c2a8c0e70cbae1c59120c3268517a8ae7fb6376b4639ef81ca22582611dbee4ed28df945134aaee
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"basic-auth@npm:^2.0.1":
version: 2.0.1
resolution: "basic-auth@npm:2.0.1"
dependencies:
safe-buffer: "npm:5.1.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/05f56db3a0fc31c89c86b605231e32ee143fb6ae38dc60616bc0970ae6a0f034172def99e69d3aed0e2c9e7cac84e2d63bc51a0b5ff6ab5fc8808cc8b29923c1
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
"body-parser@npm:1.20.2":
version: 1.20.2
resolution: "body-parser@npm:1.20.2"
dependencies:
bytes: "npm:3.1.2"
content-type: "npm:~1.0.5"
debug: "npm:2.6.9"
depd: "npm:2.0.0"
destroy: "npm:1.2.0"
http-errors: "npm:2.0.0"
iconv-lite: "npm:0.4.24"
on-finished: "npm:2.4.1"
qs: "npm:6.11.0"
raw-body: "npm:2.5.2"
type-is: "npm:~1.6.18"
unpipe: "npm:1.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/06f1438fff388a2e2354c96aa3ea8147b79bfcb1262dfcc2aae68ec13723d01d5781680657b74e9f83c808266d5baf52804032fbde2b7382b89bd8cdb273ace9
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"brace-expansion@npm:^1.1.7":
version: 1.1.11
resolution: "brace-expansion@npm:1.1.11"
dependencies:
balanced-match: "npm:^1.0.0"
concat-map: "npm:0.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/695a56cd058096a7cb71fb09d9d6a7070113c7be516699ed361317aca2ec169f618e28b8af352e02ab4233fb54eb0168460a40dc320bab0034b36ab59aaad668
languageName: node
linkType: hard
"brace-expansion@npm:^2.0.1":
version: 2.0.1
resolution: "brace-expansion@npm:2.0.1"
dependencies:
balanced-match: "npm:^1.0.0"
checksum: 10c0/b358f2fe060e2d7a87aa015979ecea07f3c37d4018f8d6deb5bd4c229ad3a0384fe6029bb76cd8be63c81e516ee52d1a0673edbe2023d53a5191732ae3c3e49f
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"braces@npm:^3.0.2":
version: 3.0.2
resolution: "braces@npm:3.0.2"
dependencies:
fill-range: "npm:^7.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/321b4d675791479293264019156ca322163f02dc06e3c4cab33bb15cd43d80b51efef69b0930cfde3acd63d126ebca24cd0544fa6f261e093a0fb41ab9dda381
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"bytes@npm:3.1.2":
version: 3.1.2
resolution: "bytes@npm:3.1.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/76d1c43cbd602794ad8ad2ae94095cddeb1de78c5dddaa7005c51af10b0176c69971a6d88e805a90c2b6550d76636e43c40d8427a808b8645ede885de4a0358e
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"call-bind@npm:^1.0.2, call-bind@npm:^1.0.5, call-bind@npm:^1.0.6, call-bind@npm:^1.0.7":
version: 1.0.7
resolution: "call-bind@npm:1.0.7"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
es-define-property: "npm:^1.0.0"
es-errors: "npm:^1.3.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
function-bind: "npm:^1.1.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
get-intrinsic: "npm:^1.2.4"
set-function-length: "npm:^1.2.1"
checksum: 10c0/a3ded2e423b8e2a265983dba81c27e125b48eefb2655e7dfab6be597088da3d47c47976c24bc51b8fd9af1061f8f87b4ab78a314f3c77784b2ae2ba535ad8b8d
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"callsites@npm:^3.0.0":
version: 3.1.0
resolution: "callsites@npm:3.1.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/fff92277400eb06c3079f9e74f3af120db9f8ea03bad0e84d9aede54bbe2d44a56cccb5f6cf12211f93f52306df87077ecec5b712794c5a9b5dac6d615a3f301
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"chalk@npm:^2.4.2":
version: 2.4.2
resolution: "chalk@npm:2.4.2"
dependencies:
ansi-styles: "npm:^3.2.1"
escape-string-regexp: "npm:^1.0.5"
supports-color: "npm:^5.3.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/e6543f02ec877732e3a2d1c3c3323ddb4d39fbab687c23f526e25bd4c6a9bf3b83a696e8c769d078e04e5754921648f7821b2a2acfd16c550435fd630026e073
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"chalk@npm:^4.0.0":
version: 4.1.2
resolution: "chalk@npm:4.1.2"
dependencies:
ansi-styles: "npm:^4.1.0"
supports-color: "npm:^7.1.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/4a3fef5cc34975c898ffe77141450f679721df9dde00f6c304353fa9c8b571929123b26a0e4617bde5018977eb655b31970c297b91b63ee83bb82aeb04666880
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"color-convert@npm:^1.9.0":
version: 1.9.3
resolution: "color-convert@npm:1.9.3"
dependencies:
color-name: "npm:1.1.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/5ad3c534949a8c68fca8fbc6f09068f435f0ad290ab8b2f76841b9e6af7e0bb57b98cb05b0e19fe33f5d91e5a8611ad457e5f69e0a484caad1f7487fd0e8253c
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"color-convert@npm:^2.0.1":
version: 2.0.1
resolution: "color-convert@npm:2.0.1"
dependencies:
color-name: "npm:~1.1.4"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/37e1150172f2e311fe1b2df62c6293a342ee7380da7b9cfdba67ea539909afbd74da27033208d01d6d5cfc65ee7868a22e18d7e7648e004425441c0f8a15a7d7
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"color-name@npm:1.1.3":
version: 1.1.3
resolution: "color-name@npm:1.1.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/566a3d42cca25b9b3cd5528cd7754b8e89c0eb646b7f214e8e2eaddb69994ac5f0557d9c175eb5d8f0ad73531140d9c47525085ee752a91a2ab15ab459caf6d6
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"color-name@npm:~1.1.4":
version: 1.1.4
resolution: "color-name@npm:1.1.4"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/a1a3f914156960902f46f7f56bc62effc6c94e84b2cae157a526b1c1f74b677a47ec602bf68a61abfa2b42d15b7c5651c6dbe72a43af720bc588dff885b10f95
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"compute-scroll-into-view@npm:1.0.14":
version: 1.0.14
resolution: "compute-scroll-into-view@npm:1.0.14"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/f2f2463b397d9ba512df4edf9b6d2c24692cbe63c0d212d2b60bddcd94cc11a4531e82bca584fbfdf284966ef2527bfb2be7b9cdc6263735d2f949f0cce77e6a
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"concat-map@npm:0.0.1":
version: 0.0.1
resolution: "concat-map@npm:0.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/c996b1cfdf95b6c90fee4dae37e332c8b6eb7d106430c17d538034c0ad9a1630cb194d2ab37293b1bdd4d779494beee7786d586a50bd9376fd6f7bcc2bd4c98f
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"content-disposition@npm:0.5.4":
version: 0.5.4
resolution: "content-disposition@npm:0.5.4"
dependencies:
safe-buffer: "npm:5.2.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/bac0316ebfeacb8f381b38285dc691c9939bf0a78b0b7c2d5758acadad242d04783cee5337ba7d12a565a19075af1b3c11c728e1e4946de73c6ff7ce45f3f1bb
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
"content-type@npm:~1.0.4, content-type@npm:~1.0.5":
version: 1.0.5
resolution: "content-type@npm:1.0.5"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/b76ebed15c000aee4678c3707e0860cb6abd4e680a598c0a26e17f0bfae723ec9cc2802f0ff1bc6e4d80603719010431d2231018373d4dde10f9ccff9dadf5af
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"convert-source-map@npm:^1.5.0":
version: 1.9.0
resolution: "convert-source-map@npm:1.9.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/281da55454bf8126cbc6625385928c43479f2060984180c42f3a86c8b8c12720a24eac260624a7d1e090004028d2dee78602330578ceec1a08e27cb8bb0a8a5b
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"cookie-signature@npm:1.0.6":
version: 1.0.6
resolution: "cookie-signature@npm:1.0.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/b36fd0d4e3fef8456915fcf7742e58fbfcc12a17a018e0eb9501c9d5ef6893b596466f03b0564b81af29ff2538fd0aa4b9d54fe5ccbfb4c90ea50ad29fe2d221
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"cookie@npm:0.6.0":
version: 0.6.0
resolution: "cookie@npm:0.6.0"
checksum: 10c0/f2318b31af7a31b4ddb4a678d024514df5e705f9be5909a192d7f116cfb6d45cbacf96a473fa733faa95050e7cff26e7832bb3ef94751592f1387b71c8956686
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"copy-to-clipboard@npm:3.3.1":
version: 3.3.1
resolution: "copy-to-clipboard@npm:3.3.1"
dependencies:
toggle-selection: "npm:^1.0.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/cc38a2a07ec22b1b60c6bd1648a21178fade4d972b43e4c2570f36f8df59ca2b7e9f8a6125d271cf2927367d3ec4012c92deaf244c12cd79509244d5c7f0f4dd
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"cors@npm:^2.8.5":
version: 2.8.5
resolution: "cors@npm:2.8.5"
dependencies:
object-assign: "npm:^4"
vary: "npm:^1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/373702b7999409922da80de4a61938aabba6929aea5b6fd9096fefb9e8342f626c0ebd7507b0e8b0b311380744cc985f27edebc0a26e0ddb784b54e1085de761
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"cosmiconfig@npm:^7.0.0":
version: 7.1.0
resolution: "cosmiconfig@npm:7.1.0"
dependencies:
"@types/parse-json": "npm:^4.0.0"
import-fresh: "npm:^3.2.1"
parse-json: "npm:^5.0.0"
path-type: "npm:^4.0.0"
yaml: "npm:^1.10.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/b923ff6af581638128e5f074a5450ba12c0300b71302398ea38dbeabd33bbcaa0245ca9adbedfcf284a07da50f99ede5658c80bb3e39e2ce770a99d28a21ef03
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"cross-spawn@npm:^7.0.2":
version: 7.0.3
resolution: "cross-spawn@npm:7.0.3"
dependencies:
path-key: "npm:^3.1.0"
shebang-command: "npm:^2.0.0"
which: "npm:^2.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/5738c312387081c98d69c98e105b6327b069197f864a60593245d64c8089c8a0a744e16349281210d56835bb9274130d825a78b2ad6853ca13cfbeffc0c31750
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"css-box-model@npm:1.2.1":
version: 1.2.1
resolution: "css-box-model@npm:1.2.1"
dependencies:
tiny-invariant: "npm:^1.0.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/611e56d76b16e4e21956ed9fa53f1936fbbfaccd378659587e9c929f342037fc6c062f8af9447226e11fe7c95e31e6c007a37e592f9bff4c2d40e6915553104a
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"csstype@npm:3.0.9":
version: 3.0.9
resolution: "csstype@npm:3.0.9"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/bca0719a6248445cbad0ba9a45911a0bdcf1ab3b08ae8ce1d7766f9d82d7ce3c5cbb1a542926d52958368c1db290baed50d6c9672a7e5fcca37eba37a28f33a3
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"csstype@npm:^3.0.2":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 3.1.3
resolution: "csstype@npm:3.1.3"
checksum: 10c0/80c089d6f7e0c5b2bd83cf0539ab41474198579584fa10d86d0cafe0642202343cbc119e076a0b1aece191989477081415d66c9fefbf3c957fc2fc4b7009f248
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"damerau-levenshtein@npm:^1.0.8":
version: 1.0.8
resolution: "damerau-levenshtein@npm:1.0.8"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/4c2647e0f42acaee7d068756c1d396e296c3556f9c8314bac1ac63ffb236217ef0e7e58602b18bb2173deec7ec8e0cac8e27cccf8f5526666b4ff11a13ad54a3
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Split NeoPass dev server into main/backing servers
2024-03-13 13:00:27 -07:00
"data-uri-to-buffer@npm:^4.0.0":
version: 4.0.1
resolution: "data-uri-to-buffer@npm:4.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/20a6b93107597530d71d4cb285acee17f66bcdfc03fd81040921a81252f19db27588d87fc8fc69e1950c55cfb0bf8ae40d0e5e21d907230813eb5d5a7f9eb45b
languageName: node
linkType: hard
"data-view-buffer@npm:^1.0.1":
version: 1.0.1
resolution: "data-view-buffer@npm:1.0.1"
dependencies:
call-bind: "npm:^1.0.6"
es-errors: "npm:^1.3.0"
is-data-view: "npm:^1.0.1"
checksum: 10c0/8984119e59dbed906a11fcfb417d7d861936f16697a0e7216fe2c6c810f6b5e8f4a5281e73f2c28e8e9259027190ac4a33e2a65fdd7fa86ac06b76e838918583
languageName: node
linkType: hard
"data-view-byte-length@npm:^1.0.1":
version: 1.0.1
resolution: "data-view-byte-length@npm:1.0.1"
dependencies:
call-bind: "npm:^1.0.7"
es-errors: "npm:^1.3.0"
is-data-view: "npm:^1.0.1"
checksum: 10c0/b7d9e48a0cf5aefed9ab7d123559917b2d7e0d65531f43b2fd95b9d3a6b46042dd3fca597c42bba384e66b70d7ad66ff23932f8367b241f53d93af42cfe04ec2
languageName: node
linkType: hard
"data-view-byte-offset@npm:^1.0.0":
version: 1.0.0
resolution: "data-view-byte-offset@npm:1.0.0"
dependencies:
call-bind: "npm:^1.0.6"
es-errors: "npm:^1.3.0"
is-data-view: "npm:^1.0.1"
checksum: 10c0/21b0d2e53fd6e20cc4257c873bf6d36d77bd6185624b84076c0a1ddaa757b49aaf076254006341d35568e89f52eecd1ccb1a502cfb620f2beca04f48a6a62a8f
Split NeoPass dev server into main/backing servers
2024-03-13 13:00:27 -07:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"debug@npm:2.6.9":
version: 2.6.9
resolution: "debug@npm:2.6.9"
dependencies:
ms: "npm:2.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/121908fb839f7801180b69a7e218a40b5a0b718813b886b7d6bdb82001b931c938e2941d1e4450f33a1b1df1da653f5f7a0440c197f29fbf8a6e9d45ff6ef589
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"debug@npm:^4.3.1, debug@npm:^4.3.2, debug@npm:^4.3.4":
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
version: 4.3.4
resolution: "debug@npm:4.3.4"
dependencies:
ms: "npm:2.1.2"
peerDependenciesMeta:
supports-color:
optional: true
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/cedbec45298dd5c501d01b92b119cd3faebe5438c3917ff11ae1bff86a6c722930ac9c8659792824013168ba6db7c4668225d845c633fbdafbbf902a6389f736
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"deep-is@npm:^0.1.3":
version: 0.1.4
resolution: "deep-is@npm:0.1.4"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/7f0ee496e0dff14a573dc6127f14c95061b448b87b995fc96c017ce0a1e66af1675e73f1d6064407975bc4ea6ab679497a29fff7b5b9c4e99cb10797c1ad0b4c
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"define-data-property@npm:^1.0.1, define-data-property@npm:^1.1.4":
version: 1.1.4
resolution: "define-data-property@npm:1.1.4"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
es-define-property: "npm:^1.0.0"
es-errors: "npm:^1.3.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
gopd: "npm:^1.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/dea0606d1483eb9db8d930d4eac62ca0fa16738b0b3e07046cddfacf7d8c868bbe13fa0cb263eb91c7d0d527960dc3f2f2471a69ed7816210307f6744fe62e37
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"define-properties@npm:^1.2.0, define-properties@npm:^1.2.1":
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
version: 1.2.1
resolution: "define-properties@npm:1.2.1"
dependencies:
define-data-property: "npm:^1.0.1"
has-property-descriptors: "npm:^1.0.0"
object-keys: "npm:^1.1.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/88a152319ffe1396ccc6ded510a3896e77efac7a1bfbaa174a7b00414a1747377e0bb525d303794a47cf30e805c2ec84e575758512c6e44a993076d29fd4e6c3
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"depd@npm:2.0.0":
version: 2.0.0
resolution: "depd@npm:2.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/58bd06ec20e19529b06f7ad07ddab60e504d9e0faca4bd23079fac2d279c3594334d736508dc350e06e510aba5e22e4594483b3a6562ce7c17dd797f4cc4ad2c
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"dequal@npm:^2.0.3":
version: 2.0.3
resolution: "dequal@npm:2.0.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/f98860cdf58b64991ae10205137c0e97d384c3a4edc7f807603887b7c4b850af1224a33d88012009f150861cbee4fa2d322c4cc04b9313bee312e47f6ecaa888
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"destroy@npm:1.2.0":
version: 1.2.0
resolution: "destroy@npm:1.2.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/bd7633942f57418f5a3b80d5cb53898127bcf53e24cdf5d5f4396be471417671f0fee48a4ebe9a1e9defbde2a31280011af58a57e090ff822f589b443ed4e643
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"detect-node-es@npm:^1.1.0":
version: 1.1.0
resolution: "detect-node-es@npm:1.1.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/e562f00de23f10c27d7119e1af0e7388407eb4b06596a25f6d79a360094a109ff285de317f02b090faae093d314cf6e73ac3214f8a5bb3a0def5bece94557fbe
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"dir-glob@npm:^3.0.1":
version: 3.0.1
resolution: "dir-glob@npm:3.0.1"
dependencies:
path-type: "npm:^4.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/dcac00920a4d503e38bb64001acb19df4efc14536ada475725e12f52c16777afdee4db827f55f13a908ee7efc0cb282e2e3dbaeeb98c0993dd93d1802d3bf00c
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"doctrine@npm:^2.1.0":
version: 2.1.0
resolution: "doctrine@npm:2.1.0"
dependencies:
esutils: "npm:^2.0.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/b6416aaff1f380bf56c3b552f31fdf7a69b45689368deca72d28636f41c16bb28ec3ebc40ace97db4c1afc0ceeb8120e8492fe0046841c94c2933b2e30a7d5ac
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"doctrine@npm:^3.0.0":
version: 3.0.0
resolution: "doctrine@npm:3.0.0"
dependencies:
esutils: "npm:^2.0.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/c96bdccabe9d62ab6fea9399fdff04a66e6563c1d6fb3a3a063e8d53c3bb136ba63e84250bbf63d00086a769ad53aef92d2bd483f03f837fc97b71cbee6b2520
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"dom-helpers@npm:^5.0.1":
version: 5.2.1
resolution: "dom-helpers@npm:5.2.1"
dependencies:
"@babel/runtime": "npm:^7.8.7"
csstype: "npm:^3.0.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/f735074d66dd759b36b158fa26e9d00c9388ee0e8c9b16af941c38f014a37fc80782de83afefd621681b19ac0501034b4f1c4a3bff5caa1b8667f0212b5e124c
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"easeljs@npm:^1.0.2":
version: 1.0.2
resolution: "easeljs@npm:1.0.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/8d20c36fe8d57b19d4c47f4c3d348d5bc503bfec6f352b27ddd13dcb3b8687bdb0b70ccf374fcd2eb60d8cac54bd2dbde45c5c68f66e5954163f710aa39c384f
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"ee-first@npm:1.1.1":
version: 1.1.1
resolution: "ee-first@npm:1.1.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/b5bb125ee93161bc16bfe6e56c6b04de5ad2aa44234d8f644813cc95d861a6910903132b05093706de2b706599367c4130eb6d170f6b46895686b95f87d017b7
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"emoji-regex@npm:^9.2.2":
version: 9.2.2
resolution: "emoji-regex@npm:9.2.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/af014e759a72064cf66e6e694a7fc6b0ed3d8db680427b021a89727689671cefe9d04151b2cad51dbaf85d5ba790d061cd167f1cf32eb7b281f6368b3c181639
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"encodeurl@npm:~1.0.2":
version: 1.0.2
resolution: "encodeurl@npm:1.0.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/f6c2387379a9e7c1156c1c3d4f9cb7bb11cf16dd4c1682e1f6746512564b053df5781029b6061296832b59fb22f459dbe250386d217c2f6e203601abb2ee0bec
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"error-ex@npm:^1.3.1":
version: 1.3.2
resolution: "error-ex@npm:1.3.2"
dependencies:
is-arrayish: "npm:^0.2.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/ba827f89369b4c93382cfca5a264d059dfefdaa56ecc5e338ffa58a6471f5ed93b71a20add1d52290a4873d92381174382658c885ac1a2305f7baca363ce9cce
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"es-abstract@npm:^1.22.1, es-abstract@npm:^1.22.3, es-abstract@npm:^1.23.0, es-abstract@npm:^1.23.1, es-abstract@npm:^1.23.2, es-abstract@npm:^1.23.3":
version: 1.23.3
resolution: "es-abstract@npm:1.23.3"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
array-buffer-byte-length: "npm:^1.0.1"
arraybuffer.prototype.slice: "npm:^1.0.3"
available-typed-arrays: "npm:^1.0.7"
call-bind: "npm:^1.0.7"
data-view-buffer: "npm:^1.0.1"
data-view-byte-length: "npm:^1.0.1"
data-view-byte-offset: "npm:^1.0.0"
es-define-property: "npm:^1.0.0"
es-errors: "npm:^1.3.0"
es-object-atoms: "npm:^1.0.0"
es-set-tostringtag: "npm:^2.0.3"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
es-to-primitive: "npm:^1.2.1"
function.prototype.name: "npm:^1.1.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
get-intrinsic: "npm:^1.2.4"
get-symbol-description: "npm:^1.0.2"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
globalthis: "npm:^1.0.3"
gopd: "npm:^1.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
has-property-descriptors: "npm:^1.0.2"
has-proto: "npm:^1.0.3"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
has-symbols: "npm:^1.0.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
hasown: "npm:^2.0.2"
internal-slot: "npm:^1.0.7"
is-array-buffer: "npm:^3.0.4"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
is-callable: "npm:^1.2.7"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
is-data-view: "npm:^1.0.1"
is-negative-zero: "npm:^2.0.3"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
is-regex: "npm:^1.1.4"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
is-shared-array-buffer: "npm:^1.0.3"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
is-string: "npm:^1.0.7"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
is-typed-array: "npm:^1.1.13"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
is-weakref: "npm:^1.0.2"
object-inspect: "npm:^1.13.1"
object-keys: "npm:^1.1.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
object.assign: "npm:^4.1.5"
regexp.prototype.flags: "npm:^1.5.2"
safe-array-concat: "npm:^1.1.2"
safe-regex-test: "npm:^1.0.3"
string.prototype.trim: "npm:^1.2.9"
string.prototype.trimend: "npm:^1.0.8"
string.prototype.trimstart: "npm:^1.0.8"
typed-array-buffer: "npm:^1.0.2"
typed-array-byte-length: "npm:^1.0.1"
typed-array-byte-offset: "npm:^1.0.2"
typed-array-length: "npm:^1.0.6"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
unbox-primitive: "npm:^1.0.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
which-typed-array: "npm:^1.1.15"
checksum: 10c0/d27e9afafb225c6924bee9971a7f25f20c314f2d6cb93a63cada4ac11dcf42040896a6c22e5fb8f2a10767055ed4ddf400be3b1eb12297d281726de470b75666
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"es-define-property@npm:^1.0.0":
version: 1.0.0
resolution: "es-define-property@npm:1.0.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
get-intrinsic: "npm:^1.2.4"
checksum: 10c0/6bf3191feb7ea2ebda48b577f69bdfac7a2b3c9bcf97307f55fd6ef1bbca0b49f0c219a935aca506c993d8c5d8bddd937766cb760cd5e5a1071351f2df9f9aa4
languageName: node
linkType: hard
"es-errors@npm:^1.1.0, es-errors@npm:^1.2.1, es-errors@npm:^1.3.0":
version: 1.3.0
resolution: "es-errors@npm:1.3.0"
checksum: 10c0/0a61325670072f98d8ae3b914edab3559b6caa980f08054a3b872052640d91da01d38df55df797fcc916389d77fc92b8d5906cf028f4db46d7e3003abecbca85
languageName: node
linkType: hard
"es-iterator-helpers@npm:^1.0.15, es-iterator-helpers@npm:^1.0.17":
version: 1.0.19
resolution: "es-iterator-helpers@npm:1.0.19"
dependencies:
call-bind: "npm:^1.0.7"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
define-properties: "npm:^1.2.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
es-abstract: "npm:^1.23.3"
es-errors: "npm:^1.3.0"
es-set-tostringtag: "npm:^2.0.3"
function-bind: "npm:^1.1.2"
get-intrinsic: "npm:^1.2.4"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
globalthis: "npm:^1.0.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
has-property-descriptors: "npm:^1.0.2"
has-proto: "npm:^1.0.3"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
has-symbols: "npm:^1.0.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
internal-slot: "npm:^1.0.7"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
iterator.prototype: "npm:^1.1.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
safe-array-concat: "npm:^1.1.2"
checksum: 10c0/ae8f0241e383b3d197383b9842c48def7fce0255fb6ed049311b686ce295595d9e389b466f6a1b7d4e7bb92d82f5e716d6fae55e20c1040249bf976743b038c5
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"es-object-atoms@npm:^1.0.0":
version: 1.0.0
resolution: "es-object-atoms@npm:1.0.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
es-errors: "npm:^1.3.0"
checksum: 10c0/1fed3d102eb27ab8d983337bb7c8b159dd2a1e63ff833ec54eea1311c96d5b08223b433060ba240541ca8adba9eee6b0a60cdbf2f80634b784febc9cc8b687b4
languageName: node
linkType: hard
"es-set-tostringtag@npm:^2.0.3":
version: 2.0.3
resolution: "es-set-tostringtag@npm:2.0.3"
dependencies:
get-intrinsic: "npm:^1.2.4"
has-tostringtag: "npm:^1.0.2"
hasown: "npm:^2.0.1"
checksum: 10c0/f22aff1585eb33569c326323f0b0d175844a1f11618b86e193b386f8be0ea9474cfbe46df39c45d959f7aa8f6c06985dc51dd6bce5401645ec5a74c4ceaa836a
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"es-shim-unscopables@npm:^1.0.0, es-shim-unscopables@npm:^1.0.2":
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
version: 1.0.2
resolution: "es-shim-unscopables@npm:1.0.2"
dependencies:
hasown: "npm:^2.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/f495af7b4b7601a4c0cfb893581c352636e5c08654d129590386a33a0432cf13a7bdc7b6493801cadd990d838e2839b9013d1de3b880440cb537825e834fe783
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"es-to-primitive@npm:^1.2.1":
version: 1.2.1
resolution: "es-to-primitive@npm:1.2.1"
dependencies:
is-callable: "npm:^1.1.4"
is-date-object: "npm:^1.0.1"
is-symbol: "npm:^1.0.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/0886572b8dc075cb10e50c0af62a03d03a68e1e69c388bd4f10c0649ee41b1fbb24840a1b7e590b393011b5cdbe0144b776da316762653685432df37d6de60f1
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"es6-promise@npm:^4.2.8":
version: 4.2.8
resolution: "es6-promise@npm:4.2.8"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/2373d9c5e9a93bdd9f9ed32ff5cb6dd3dd785368d1c21e9bbbfd07d16345b3774ae260f2bd24c8f836a6903f432b4151e7816a7fa8891ccb4e1a55a028ec42c3
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"esbuild@npm:^0.19.0":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 0.19.12
resolution: "esbuild@npm:0.19.12"
dependencies:
"@esbuild/aix-ppc64": "npm:0.19.12"
"@esbuild/android-arm": "npm:0.19.12"
"@esbuild/android-arm64": "npm:0.19.12"
"@esbuild/android-x64": "npm:0.19.12"
"@esbuild/darwin-arm64": "npm:0.19.12"
"@esbuild/darwin-x64": "npm:0.19.12"
"@esbuild/freebsd-arm64": "npm:0.19.12"
"@esbuild/freebsd-x64": "npm:0.19.12"
"@esbuild/linux-arm": "npm:0.19.12"
"@esbuild/linux-arm64": "npm:0.19.12"
"@esbuild/linux-ia32": "npm:0.19.12"
"@esbuild/linux-loong64": "npm:0.19.12"
"@esbuild/linux-mips64el": "npm:0.19.12"
"@esbuild/linux-ppc64": "npm:0.19.12"
"@esbuild/linux-riscv64": "npm:0.19.12"
"@esbuild/linux-s390x": "npm:0.19.12"
"@esbuild/linux-x64": "npm:0.19.12"
"@esbuild/netbsd-x64": "npm:0.19.12"
"@esbuild/openbsd-x64": "npm:0.19.12"
"@esbuild/sunos-x64": "npm:0.19.12"
"@esbuild/win32-arm64": "npm:0.19.12"
"@esbuild/win32-ia32": "npm:0.19.12"
"@esbuild/win32-x64": "npm:0.19.12"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependenciesMeta:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@esbuild/aix-ppc64":
optional: true
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"@esbuild/android-arm":
optional: true
"@esbuild/android-arm64":
optional: true
"@esbuild/android-x64":
optional: true
"@esbuild/darwin-arm64":
optional: true
"@esbuild/darwin-x64":
optional: true
"@esbuild/freebsd-arm64":
optional: true
"@esbuild/freebsd-x64":
optional: true
"@esbuild/linux-arm":
optional: true
"@esbuild/linux-arm64":
optional: true
"@esbuild/linux-ia32":
optional: true
"@esbuild/linux-loong64":
optional: true
"@esbuild/linux-mips64el":
optional: true
"@esbuild/linux-ppc64":
optional: true
"@esbuild/linux-riscv64":
optional: true
"@esbuild/linux-s390x":
optional: true
"@esbuild/linux-x64":
optional: true
"@esbuild/netbsd-x64":
optional: true
"@esbuild/openbsd-x64":
optional: true
"@esbuild/sunos-x64":
optional: true
"@esbuild/win32-arm64":
optional: true
"@esbuild/win32-ia32":
optional: true
"@esbuild/win32-x64":
optional: true
bin:
esbuild: bin/esbuild
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/0f2d21ffe24ebead64843f87c3aebe2e703a5ed9feb086a0728b24907fac2eb9923e4a79857d3df9059c915739bd7a870dd667972eae325c67f478b592b8582d
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"escape-html@npm:~1.0.3":
version: 1.0.3
resolution: "escape-html@npm:1.0.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/524c739d776b36c3d29fa08a22e03e8824e3b2fd57500e5e44ecf3cc4707c34c60f9ca0781c0e33d191f2991161504c295e98f68c78fe7baa6e57081ec6ac0a3
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"escape-string-regexp@npm:^1.0.5":
version: 1.0.5
resolution: "escape-string-regexp@npm:1.0.5"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/a968ad453dd0c2724e14a4f20e177aaf32bb384ab41b674a8454afe9a41c5e6fe8903323e0a1052f56289d04bd600f81278edf140b0fcc02f5cac98d0f5b5371
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"escape-string-regexp@npm:^4.0.0":
version: 4.0.0
resolution: "escape-string-regexp@npm:4.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/9497d4dd307d845bd7f75180d8188bb17ea8c151c1edbf6b6717c100e104d629dc2dfb687686181b0f4b7d732c7dfdc4d5e7a8ff72de1b0ca283a75bbb3a9cd9
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"eslint-plugin-jsx-a11y@npm:^6.8.0":
version: 6.8.0
resolution: "eslint-plugin-jsx-a11y@npm:6.8.0"
dependencies:
"@babel/runtime": "npm:^7.23.2"
aria-query: "npm:^5.3.0"
array-includes: "npm:^3.1.7"
array.prototype.flatmap: "npm:^1.3.2"
ast-types-flow: "npm:^0.0.8"
axe-core: "npm:=4.7.0"
axobject-query: "npm:^3.2.1"
damerau-levenshtein: "npm:^1.0.8"
emoji-regex: "npm:^9.2.2"
es-iterator-helpers: "npm:^1.0.15"
hasown: "npm:^2.0.0"
jsx-ast-utils: "npm:^3.3.5"
language-tags: "npm:^1.0.9"
minimatch: "npm:^3.1.2"
object.entries: "npm:^1.1.7"
object.fromentries: "npm:^2.0.7"
peerDependencies:
eslint: ^3 || ^4 || ^5 || ^6 || ^7 || ^8
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/199b883e526e6f9d7c54cb3f094abc54f11a1ec816db5fb6cae3b938eb0e503acc10ccba91ca7451633a9d0b9abc0ea03601844a8aba5fe88c5e8897c9ac8f49
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"eslint-plugin-react-hooks@npm:^4.6.0":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 4.6.2
resolution: "eslint-plugin-react-hooks@npm:4.6.2"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
peerDependencies:
eslint: ^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0 || ^8.0.0-0
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/4844e58c929bc05157fb70ba1e462e34f1f4abcbc8dd5bbe5b04513d33e2699effb8bca668297976ceea8e7ebee4e8fc29b9af9d131bcef52886feaa2308b2cc
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"eslint-plugin-react@npm:^7.33.2":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 7.34.1
resolution: "eslint-plugin-react@npm:7.34.1"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
array-includes: "npm:^3.1.7"
array.prototype.findlast: "npm:^1.2.4"
array.prototype.flatmap: "npm:^1.3.2"
array.prototype.toreversed: "npm:^1.1.2"
array.prototype.tosorted: "npm:^1.1.3"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
doctrine: "npm:^2.1.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
es-iterator-helpers: "npm:^1.0.17"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
estraverse: "npm:^5.3.0"
jsx-ast-utils: "npm:^2.4.1 || ^3.0.0"
minimatch: "npm:^3.1.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
object.entries: "npm:^1.1.7"
object.fromentries: "npm:^2.0.7"
object.hasown: "npm:^1.1.3"
object.values: "npm:^1.1.7"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
prop-types: "npm:^15.8.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
resolve: "npm:^2.0.0-next.5"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
semver: "npm:^6.3.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
string.prototype.matchall: "npm:^4.0.10"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
peerDependencies:
eslint: ^3 || ^4 || ^5 || ^6 || ^7 || ^8
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/7c61b1314d37a4ac2f2474f9571f801f1a1a5d81dcd4abbb5d07145406518722fb792367267757ee116bde254be9753242d6b93c9619110398b3fe1746e4848c
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"eslint-scope@npm:^7.2.2":
version: 7.2.2
resolution: "eslint-scope@npm:7.2.2"
dependencies:
esrecurse: "npm:^4.3.0"
estraverse: "npm:^5.2.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/613c267aea34b5a6d6c00514e8545ef1f1433108097e857225fed40d397dd6b1809dffd11c2fde23b37ca53d7bf935fe04d2a18e6fc932b31837b6ad67e1c116
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"eslint-visitor-keys@npm:^3.3.0, eslint-visitor-keys@npm:^3.4.1, eslint-visitor-keys@npm:^3.4.3":
version: 3.4.3
resolution: "eslint-visitor-keys@npm:3.4.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/92708e882c0a5ffd88c23c0b404ac1628cf20104a108c745f240a13c332a11aac54f49a22d5762efbffc18ecbc9a580d1b7ad034bf5f3cc3307e5cbff2ec9820
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"eslint@npm:^8.52.0":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 8.57.0
resolution: "eslint@npm:8.57.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
"@eslint-community/eslint-utils": "npm:^4.2.0"
"@eslint-community/regexpp": "npm:^4.6.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@eslint/eslintrc": "npm:^2.1.4"
"@eslint/js": "npm:8.57.0"
"@humanwhocodes/config-array": "npm:^0.11.14"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"@humanwhocodes/module-importer": "npm:^1.0.1"
"@nodelib/fs.walk": "npm:^1.2.8"
"@ungap/structured-clone": "npm:^1.2.0"
ajv: "npm:^6.12.4"
chalk: "npm:^4.0.0"
cross-spawn: "npm:^7.0.2"
debug: "npm:^4.3.2"
doctrine: "npm:^3.0.0"
escape-string-regexp: "npm:^4.0.0"
eslint-scope: "npm:^7.2.2"
eslint-visitor-keys: "npm:^3.4.3"
espree: "npm:^9.6.1"
esquery: "npm:^1.4.2"
esutils: "npm:^2.0.2"
fast-deep-equal: "npm:^3.1.3"
file-entry-cache: "npm:^6.0.1"
find-up: "npm:^5.0.0"
glob-parent: "npm:^6.0.2"
globals: "npm:^13.19.0"
graphemer: "npm:^1.4.0"
ignore: "npm:^5.2.0"
imurmurhash: "npm:^0.1.4"
is-glob: "npm:^4.0.0"
is-path-inside: "npm:^3.0.3"
js-yaml: "npm:^4.1.0"
json-stable-stringify-without-jsonify: "npm:^1.0.1"
levn: "npm:^0.4.1"
lodash.merge: "npm:^4.6.2"
minimatch: "npm:^3.1.2"
natural-compare: "npm:^1.4.0"
optionator: "npm:^0.9.3"
strip-ansi: "npm:^6.0.1"
text-table: "npm:^0.2.0"
bin:
eslint: bin/eslint.js
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/00bb96fd2471039a312435a6776fe1fd557c056755eaa2b96093ef3a8508c92c8775d5f754768be6b1dddd09fdd3379ddb231eeb9b6c579ee17ea7d68000a529
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"espree@npm:^9.6.0, espree@npm:^9.6.1":
version: 9.6.1
resolution: "espree@npm:9.6.1"
dependencies:
acorn: "npm:^8.9.0"
acorn-jsx: "npm:^5.3.2"
eslint-visitor-keys: "npm:^3.4.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/1a2e9b4699b715347f62330bcc76aee224390c28bb02b31a3752e9d07549c473f5f986720483c6469cf3cfb3c9d05df612ffc69eb1ee94b54b739e67de9bb460
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"esquery@npm:^1.4.2":
version: 1.5.0
resolution: "esquery@npm:1.5.0"
dependencies:
estraverse: "npm:^5.1.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/a084bd049d954cc88ac69df30534043fb2aee5555b56246493f42f27d1e168f00d9e5d4192e46f10290d312dc30dc7d58994d61a609c579c1219d636996f9213
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"esrecurse@npm:^4.3.0":
version: 4.3.0
resolution: "esrecurse@npm:4.3.0"
dependencies:
estraverse: "npm:^5.2.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/81a37116d1408ded88ada45b9fb16dbd26fba3aadc369ce50fcaf82a0bac12772ebd7b24cd7b91fc66786bf2c1ac7b5f196bc990a473efff972f5cb338877cf5
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"estraverse@npm:^5.1.0, estraverse@npm:^5.2.0, estraverse@npm:^5.3.0":
version: 5.3.0
resolution: "estraverse@npm:5.3.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/1ff9447b96263dec95d6d67431c5e0771eb9776427421260a3e2f0fdd5d6bd4f8e37a7338f5ad2880c9f143450c9b1e4fc2069060724570a49cf9cf0312bd107
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"esutils@npm:^2.0.2":
version: 2.0.3
resolution: "esutils@npm:2.0.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/9a2fe69a41bfdade834ba7c42de4723c97ec776e40656919c62cbd13607c45e127a003f05f724a1ea55e5029a4cf2de444b13009f2af71271e42d93a637137c7
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"etag@npm:~1.8.1":
version: 1.8.1
resolution: "etag@npm:1.8.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/12be11ef62fb9817314d790089a0a49fae4e1b50594135dcb8076312b7d7e470884b5100d249b28c18581b7fd52f8b485689ffae22a11ed9ec17377a33a08f84
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Split NeoPass dev server into main/backing servers
2024-03-13 13:00:27 -07:00
"express@npm:^4.18.2, express@npm:^4.18.3":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 4.19.2
resolution: "express@npm:4.19.2"
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
dependencies:
accepts: "npm:~1.3.8"
array-flatten: "npm:1.1.1"
body-parser: "npm:1.20.2"
content-disposition: "npm:0.5.4"
content-type: "npm:~1.0.4"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
cookie: "npm:0.6.0"
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
cookie-signature: "npm:1.0.6"
debug: "npm:2.6.9"
depd: "npm:2.0.0"
encodeurl: "npm:~1.0.2"
escape-html: "npm:~1.0.3"
etag: "npm:~1.8.1"
finalhandler: "npm:1.2.0"
fresh: "npm:0.5.2"
http-errors: "npm:2.0.0"
merge-descriptors: "npm:1.0.1"
methods: "npm:~1.1.2"
on-finished: "npm:2.4.1"
parseurl: "npm:~1.3.3"
path-to-regexp: "npm:0.1.7"
proxy-addr: "npm:~2.0.7"
qs: "npm:6.11.0"
range-parser: "npm:~1.2.1"
safe-buffer: "npm:5.2.1"
send: "npm:0.18.0"
serve-static: "npm:1.15.0"
setprototypeof: "npm:1.2.0"
statuses: "npm:2.0.1"
type-is: "npm:~1.6.18"
utils-merge: "npm:1.0.1"
vary: "npm:~1.1.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/e82e2662ea9971c1407aea9fc3c16d6b963e55e3830cd0ef5e00b533feda8b770af4e3be630488ef8a752d7c75c4fcefb15892868eeaafe7353cb9e3e269fdcb
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"fast-deep-equal@npm:^3.1.1, fast-deep-equal@npm:^3.1.3":
version: 3.1.3
resolution: "fast-deep-equal@npm:3.1.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/40dedc862eb8992c54579c66d914635afbec43350afbbe991235fdcb4e3a8d5af1b23ae7e79bef7d4882d0ecee06c3197488026998fb19f72dc95acff1d1b1d0
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"fast-glob@npm:^3.2.9":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 3.3.2
resolution: "fast-glob@npm:3.3.2"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
"@nodelib/fs.stat": "npm:^2.0.2"
"@nodelib/fs.walk": "npm:^1.2.3"
glob-parent: "npm:^5.1.2"
merge2: "npm:^1.3.0"
micromatch: "npm:^4.0.4"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/42baad7b9cd40b63e42039132bde27ca2cb3a4950d0a0f9abe4639ea1aa9d3e3b40f98b1fe31cbc0cc17b664c9ea7447d911a152fa34ec5b72977b125a6fc845
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"fast-json-stable-stringify@npm:^2.0.0":
version: 2.1.0
resolution: "fast-json-stable-stringify@npm:2.1.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/7f081eb0b8a64e0057b3bb03f974b3ef00135fbf36c1c710895cd9300f13c94ba809bb3a81cf4e1b03f6e5285610a61abbd7602d0652de423144dfee5a389c9b
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"fast-levenshtein@npm:^2.0.6":
version: 2.0.6
resolution: "fast-levenshtein@npm:2.0.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/111972b37338bcb88f7d9e2c5907862c280ebf4234433b95bc611e518d192ccb2d38119c4ac86e26b668d75f7f3894f4ff5c4982899afced7ca78633b08287c4
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"fastq@npm:^1.6.0":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 1.17.1
resolution: "fastq@npm:1.17.1"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
reusify: "npm:^1.0.4"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/1095f16cea45fb3beff558bb3afa74ca7a9250f5a670b65db7ed585f92b4b48381445cd328b3d87323da81e43232b5d5978a8201bde84e0cd514310f1ea6da34
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Split NeoPass dev server into main/backing servers
2024-03-13 13:00:27 -07:00
"fetch-blob@npm:^3.1.2, fetch-blob@npm:^3.1.4":
version: 3.2.0
resolution: "fetch-blob@npm:3.2.0"
dependencies:
node-domexception: "npm:^1.0.0"
web-streams-polyfill: "npm:^3.0.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/60054bf47bfa10fb0ba6cb7742acec2f37c1f56344f79a70bb8b1c48d77675927c720ff3191fa546410a0442c998d27ab05e9144c32d530d8a52fbe68f843b69
Split NeoPass dev server into main/backing servers
2024-03-13 13:00:27 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"file-entry-cache@npm:^6.0.1":
version: 6.0.1
resolution: "file-entry-cache@npm:6.0.1"
dependencies:
flat-cache: "npm:^3.0.4"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/58473e8a82794d01b38e5e435f6feaf648e3f36fdb3a56e98f417f4efae71ad1c0d4ebd8a9a7c50c3ad085820a93fc7494ad721e0e4ebc1da3573f4e1c3c7cdd
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"fill-range@npm:^7.0.1":
version: 7.0.1
resolution: "fill-range@npm:7.0.1"
dependencies:
to-regex-range: "npm:^5.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/7cdad7d426ffbaadf45aeb5d15ec675bbd77f7597ad5399e3d2766987ed20bda24d5fac64b3ee79d93276f5865608bb22344a26b9b1ae6c4d00bd94bf611623f
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"finalhandler@npm:1.2.0":
version: 1.2.0
resolution: "finalhandler@npm:1.2.0"
dependencies:
debug: "npm:2.6.9"
encodeurl: "npm:~1.0.2"
escape-html: "npm:~1.0.3"
on-finished: "npm:2.4.1"
parseurl: "npm:~1.3.3"
statuses: "npm:2.0.1"
unpipe: "npm:~1.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/64b7e5ff2ad1fcb14931cd012651631b721ce657da24aedb5650ddde9378bf8e95daa451da43398123f5de161a81e79ff5affe4f9f2a6d2df4a813d6d3e254b7
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"find-root@npm:^1.1.0":
version: 1.1.0
resolution: "find-root@npm:1.1.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/1abc7f3bf2f8d78ff26d9e00ce9d0f7b32e5ff6d1da2857bcdf4746134c422282b091c672cde0572cac3840713487e0a7a636af9aa1b74cb11894b447a521efa
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"find-up@npm:^5.0.0":
version: 5.0.0
resolution: "find-up@npm:5.0.0"
dependencies:
locate-path: "npm:^6.0.0"
path-exists: "npm:^4.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/062c5a83a9c02f53cdd6d175a37ecf8f87ea5bbff1fdfb828f04bfa021441bc7583e8ebc0872a4c1baab96221fb8a8a275a19809fb93fbc40bd69ec35634069a
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"flat-cache@npm:^3.0.4":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 3.2.0
resolution: "flat-cache@npm:3.2.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
flatted: "npm:^3.2.9"
keyv: "npm:^4.5.3"
rimraf: "npm:^3.0.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/b76f611bd5f5d68f7ae632e3ae503e678d205cf97a17c6ab5b12f6ca61188b5f1f7464503efae6dc18683ed8f0b41460beb48ac4b9ac63fe6201296a91ba2f75
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"flatted@npm:^3.2.9":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 3.3.1
resolution: "flatted@npm:3.3.1"
checksum: 10c0/324166b125ee07d4ca9bcf3a5f98d915d5db4f39d711fba640a3178b959919aae1f7cfd8aabcfef5826ed8aa8a2aa14cc85b2d7d18ff638ddf4ae3df39573eaf
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"focus-lock@npm:^0.9.1":
version: 0.9.2
resolution: "focus-lock@npm:0.9.2"
dependencies:
tslib: "npm:^2.0.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/7d8cf76f4dbd3345db4dc0ff20f4e529805062866dd2ab766912bc0c2a00092db1fb378f47ee2ea7a7e12e23ace802042030c0c5732801e6e0289cf9ad2f13dc
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"for-each@npm:^0.3.3":
version: 0.3.3
resolution: "for-each@npm:0.3.3"
dependencies:
is-callable: "npm:^1.1.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/22330d8a2db728dbf003ec9182c2d421fbcd2969b02b4f97ec288721cda63eb28f2c08585ddccd0f77cb2930af8d958005c9e72f47141dc51816127a118f39aa
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Split NeoPass dev server into main/backing servers
2024-03-13 13:00:27 -07:00
"formdata-polyfill@npm:^4.0.10":
version: 4.0.10
resolution: "formdata-polyfill@npm:4.0.10"
dependencies:
fetch-blob: "npm:^3.1.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/5392ec484f9ce0d5e0d52fb5a78e7486637d516179b0eb84d81389d7eccf9ca2f663079da56f761355c0a65792810e3b345dc24db9a8bbbcf24ef3c8c88570c6
Split NeoPass dev server into main/backing servers
2024-03-13 13:00:27 -07:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"forwarded@npm:0.2.0":
version: 0.2.0
resolution: "forwarded@npm:0.2.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/9b67c3fac86acdbc9ae47ba1ddd5f2f81526fa4c8226863ede5600a3f7c7416ef451f6f1e240a3cc32d0fd79fcfe6beb08fd0da454f360032bde70bf80afbb33
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"framer-motion@npm:^4.1.11":
version: 4.1.17
resolution: "framer-motion@npm:4.1.17"
dependencies:
"@emotion/is-prop-valid": "npm:^0.8.2"
framesync: "npm:5.3.0"
hey-listen: "npm:^1.0.8"
popmotion: "npm:9.3.6"
style-value-types: "npm:4.1.4"
tslib: "npm:^2.1.0"
peerDependencies:
react: ">=16.8 || ^17.0.0"
react-dom: ">=16.8 || ^17.0.0"
dependenciesMeta:
"@emotion/is-prop-valid":
optional: true
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/37a3e05f70c370703465f68964cfe795a1fcc6a8cca28813e11be853fff0324891676be4bf514c85ce6a63a78cb1a123b54847f2563325880e0878c8942249f1
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"framesync@npm:5.3.0":
version: 5.3.0
resolution: "framesync@npm:5.3.0"
dependencies:
tslib: "npm:^2.1.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/c11771528171354b508c3b367b76deb2be542d4214946f2db46fc4db92eceb89eb9aa97c9386c3062536d7068e4d63689d58a35f8e5b0c456a6e86c23a2f35bc
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"fresh@npm:0.5.2":
version: 0.5.2
resolution: "fresh@npm:0.5.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/c6d27f3ed86cc5b601404822f31c900dd165ba63fff8152a3ef714e2012e7535027063bc67ded4cb5b3a49fa596495d46cacd9f47d6328459cf570f08b7d9e5a
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"fs.realpath@npm:^1.0.0":
version: 1.0.0
resolution: "fs.realpath@npm:1.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/444cf1291d997165dfd4c0d58b69f0e4782bfd9149fd72faa4fe299e68e0e93d6db941660b37dd29153bf7186672ececa3b50b7e7249477b03fdf850f287c948
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"function-bind@npm:^1.1.2":
version: 1.1.2
resolution: "function-bind@npm:1.1.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/d8680ee1e5fcd4c197e4ac33b2b4dce03c71f4d91717292785703db200f5c21f977c568d28061226f9b5900cbcd2c84463646134fd5337e7925e0942bc3f46d5
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"function.prototype.name@npm:^1.1.5, function.prototype.name@npm:^1.1.6":
version: 1.1.6
resolution: "function.prototype.name@npm:1.1.6"
dependencies:
call-bind: "npm:^1.0.2"
define-properties: "npm:^1.2.0"
es-abstract: "npm:^1.22.1"
functions-have-names: "npm:^1.2.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/9eae11294905b62cb16874adb4fc687927cda3162285e0ad9612e6a1d04934005d46907362ea9cdb7428edce05a2f2c3dabc3b2d21e9fd343e9bb278230ad94b
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"functions-have-names@npm:^1.2.3":
version: 1.2.3
resolution: "functions-have-names@npm:1.2.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/33e77fd29bddc2d9bb78ab3eb854c165909201f88c75faa8272e35899e2d35a8a642a15e7420ef945e1f64a9670d6aa3ec744106b2aa42be68ca5114025954ca
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"get-intrinsic@npm:^1.1.3, get-intrinsic@npm:^1.2.1, get-intrinsic@npm:^1.2.3, get-intrinsic@npm:^1.2.4":
version: 1.2.4
resolution: "get-intrinsic@npm:1.2.4"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
es-errors: "npm:^1.3.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
function-bind: "npm:^1.1.2"
has-proto: "npm:^1.0.1"
has-symbols: "npm:^1.0.3"
hasown: "npm:^2.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/0a9b82c16696ed6da5e39b1267104475c47e3a9bdbe8b509dfe1710946e38a87be70d759f4bb3cda042d76a41ef47fe769660f3b7c0d1f68750299344ffb15b7
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"get-nonce@npm:^1.0.0":
version: 1.0.1
resolution: "get-nonce@npm:1.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/2d7df55279060bf0568549e1ffc9b84bc32a32b7541675ca092dce56317cdd1a59a98dcc4072c9f6a980779440139a3221d7486f52c488e69dc0fd27b1efb162
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"get-symbol-description@npm:^1.0.2":
version: 1.0.2
resolution: "get-symbol-description@npm:1.0.2"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
call-bind: "npm:^1.0.5"
es-errors: "npm:^1.3.0"
get-intrinsic: "npm:^1.2.4"
checksum: 10c0/867be6d63f5e0eb026cb3b0ef695ec9ecf9310febb041072d2e142f260bd91ced9eeb426b3af98791d1064e324e653424afa6fd1af17dee373bea48ae03162bc
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"glob-parent@npm:^5.1.2":
version: 5.1.2
resolution: "glob-parent@npm:5.1.2"
dependencies:
is-glob: "npm:^4.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/cab87638e2112bee3f839ef5f6e0765057163d39c66be8ec1602f3823da4692297ad4e972de876ea17c44d652978638d2fd583c6713d0eb6591706825020c9ee
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"glob-parent@npm:^6.0.2":
version: 6.0.2
resolution: "glob-parent@npm:6.0.2"
dependencies:
is-glob: "npm:^4.0.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/317034d88654730230b3f43bb7ad4f7c90257a426e872ea0bf157473ac61c99bf5d205fad8f0185f989be8d2fa6d3c7dce1645d99d545b6ea9089c39f838e7f8
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"glob@npm:^7.1.3":
version: 7.2.3
resolution: "glob@npm:7.2.3"
dependencies:
fs.realpath: "npm:^1.0.0"
inflight: "npm:^1.0.4"
inherits: "npm:2"
minimatch: "npm:^3.1.1"
once: "npm:^1.3.0"
path-is-absolute: "npm:^1.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/65676153e2b0c9095100fe7f25a778bf45608eeb32c6048cf307f579649bcc30353277b3b898a3792602c65764e5baa4f643714dfbdfd64ea271d210c7a425fe
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"globals@npm:^13.19.0":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 13.24.0
resolution: "globals@npm:13.24.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
type-fest: "npm:^0.20.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/d3c11aeea898eb83d5ec7a99508600fbe8f83d2cf00cbb77f873dbf2bcb39428eff1b538e4915c993d8a3b3473fa71eeebfe22c9bb3a3003d1e26b1f2c8a42cd
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"globalthis@npm:^1.0.3":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 1.0.4
resolution: "globalthis@npm:1.0.4"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
define-properties: "npm:^1.2.1"
gopd: "npm:^1.0.1"
checksum: 10c0/9d156f313af79d80b1566b93e19285f481c591ad6d0d319b4be5e03750d004dde40a39a0f26f7e635f9007a3600802f53ecd85a759b86f109e80a5f705e01846
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"globby@npm:^11.1.0":
version: 11.1.0
resolution: "globby@npm:11.1.0"
dependencies:
array-union: "npm:^2.1.0"
dir-glob: "npm:^3.0.1"
fast-glob: "npm:^3.2.9"
ignore: "npm:^5.2.0"
merge2: "npm:^1.4.1"
slash: "npm:^3.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/b39511b4afe4bd8a7aead3a27c4ade2b9968649abab0a6c28b1a90141b96ca68ca5db1302f7c7bd29eab66bf51e13916b8e0a3d0ac08f75e1e84a39b35691189
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"gopd@npm:^1.0.1":
version: 1.0.1
resolution: "gopd@npm:1.0.1"
dependencies:
get-intrinsic: "npm:^1.1.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/505c05487f7944c552cee72087bf1567debb470d4355b1335f2c262d218ebbff805cd3715448fe29b4b380bae6912561d0467233e4165830efd28da241418c63
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"graphemer@npm:^1.4.0":
version: 1.4.0
resolution: "graphemer@npm:1.4.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/e951259d8cd2e0d196c72ec711add7115d42eb9a8146c8eeda5b8d3ac91e5dd816b9cd68920726d9fd4490368e7ed86e9c423f40db87e2d8dfafa00fa17c3a31
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"graphql-tag@npm:^2.12.6":
version: 2.12.6
resolution: "graphql-tag@npm:2.12.6"
dependencies:
tslib: "npm:^2.1.0"
peerDependencies:
graphql: ^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0 || ^16.0.0
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/7763a72011bda454ed8ff1a0d82325f43ca6478e4ce4ab8b7910c4c651dd00db553132171c04d80af5d5aebf1ef6a8a9fd53ccfa33b90ddc00aa3d4be6114419
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"graphql@npm:^15.5.0":
version: 15.8.0
resolution: "graphql@npm:15.8.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/30cc09b77170a9d1ed68e4c017ec8c5265f69501c96e4f34f8f6613f39a886c96dd9853eac925f212566ed651736334c8fe24ceae6c44e8d7625c95c3009a801
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"has-bigints@npm:^1.0.1, has-bigints@npm:^1.0.2":
version: 1.0.2
resolution: "has-bigints@npm:1.0.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/724eb1485bfa3cdff6f18d95130aa190561f00b3fcf9f19dc640baf8176b5917c143b81ec2123f8cddb6c05164a198c94b13e1377c497705ccc8e1a80306e83b
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"has-flag@npm:^3.0.0":
version: 3.0.0
resolution: "has-flag@npm:3.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/1c6c83b14b8b1b3c25b0727b8ba3e3b647f99e9e6e13eb7322107261de07a4c1be56fc0d45678fc376e09772a3a1642ccdaf8fc69bdf123b6c086598397ce473
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"has-flag@npm:^4.0.0":
version: 4.0.0
resolution: "has-flag@npm:4.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/2e789c61b7888d66993e14e8331449e525ef42aac53c627cc53d1c3334e768bcb6abdc4f5f0de1478a25beec6f0bd62c7549058b7ac53e924040d4f301f02fd1
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"has-property-descriptors@npm:^1.0.0, has-property-descriptors@npm:^1.0.2":
version: 1.0.2
resolution: "has-property-descriptors@npm:1.0.2"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
es-define-property: "npm:^1.0.0"
checksum: 10c0/253c1f59e80bb476cf0dde8ff5284505d90c3bdb762983c3514d36414290475fe3fd6f574929d84de2a8eec00d35cf07cb6776205ff32efd7c50719125f00236
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"has-proto@npm:^1.0.1, has-proto@npm:^1.0.3":
version: 1.0.3
resolution: "has-proto@npm:1.0.3"
checksum: 10c0/35a6989f81e9f8022c2f4027f8b48a552de714938765d019dbea6bb547bd49ce5010a3c7c32ec6ddac6e48fc546166a3583b128f5a7add8b058a6d8b4afec205
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"has-symbols@npm:^1.0.2, has-symbols@npm:^1.0.3":
version: 1.0.3
resolution: "has-symbols@npm:1.0.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/e6922b4345a3f37069cdfe8600febbca791c94988c01af3394d86ca3360b4b93928bbf395859158f88099cb10b19d98e3bbab7c9ff2c1bd09cf665ee90afa2c3
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"has-tostringtag@npm:^1.0.0, has-tostringtag@npm:^1.0.2":
version: 1.0.2
resolution: "has-tostringtag@npm:1.0.2"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
has-symbols: "npm:^1.0.3"
checksum: 10c0/a8b166462192bafe3d9b6e420a1d581d93dd867adb61be223a17a8d6dad147aa77a8be32c961bb2f27b3ef893cae8d36f564ab651f5e9b7938ae86f74027c48c
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"hash.js@npm:^1.1.7":
version: 1.1.7
resolution: "hash.js@npm:1.1.7"
dependencies:
inherits: "npm:^2.0.3"
minimalistic-assert: "npm:^1.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/41ada59494eac5332cfc1ce6b7ebdd7b88a3864a6d6b08a3ea8ef261332ed60f37f10877e0c825aaa4bddebf164fbffa618286aeeec5296675e2671cbfa746c4
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"hasown@npm:^2.0.0, hasown@npm:^2.0.1, hasown@npm:^2.0.2":
version: 2.0.2
resolution: "hasown@npm:2.0.2"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
function-bind: "npm:^1.1.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/3769d434703b8ac66b209a4cca0737519925bbdb61dd887f93a16372b14694c63ff4e797686d87c90f08168e81082248b9b028bad60d4da9e0d1148766f56eb9
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"hey-listen@npm:^1.0.8":
version: 1.0.8
resolution: "hey-listen@npm:1.0.8"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/38db3028b4756f3d536c0f6a92da53bad577ab649b06dddfd0a4d953f9a46bbc6a7f693c8c5b466a538d6d23dbc469260c848427f0de14198a2bbecbac37b39e
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"hoist-non-react-statics@npm:^3.3.1, hoist-non-react-statics@npm:^3.3.2":
version: 3.3.2
resolution: "hoist-non-react-statics@npm:3.3.2"
dependencies:
react-is: "npm:^16.7.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/fe0889169e845d738b59b64badf5e55fa3cf20454f9203d1eb088df322d49d4318df774828e789898dcb280e8a5521bb59b3203385662ca5e9218a6ca5820e74
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"http-errors@npm:2.0.0":
version: 2.0.0
resolution: "http-errors@npm:2.0.0"
dependencies:
depd: "npm:2.0.0"
inherits: "npm:2.0.4"
setprototypeof: "npm:1.2.0"
statuses: "npm:2.0.1"
toidentifier: "npm:1.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/fc6f2715fe188d091274b5ffc8b3657bd85c63e969daa68ccb77afb05b071a4b62841acb7a21e417b5539014dff2ebf9550f0b14a9ff126f2734a7c1387f8e19
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"husky@npm:^8.0.3":
version: 8.0.3
resolution: "husky@npm:8.0.3"
bin:
husky: lib/bin.js
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/6722591771c657b91a1abb082e07f6547eca79144d678e586828ae806499d90dce2a6aee08b66183fd8b085f19d20e0990a2ad396961746b4c8bd5bdb619d668
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"iconv-lite@npm:0.4.24":
version: 0.4.24
resolution: "iconv-lite@npm:0.4.24"
dependencies:
safer-buffer: "npm:>= 2.1.2 < 3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/c6886a24cc00f2a059767440ec1bc00d334a89f250db8e0f7feb4961c8727118457e27c495ba94d082e51d3baca378726cd110aaf7ded8b9bbfd6a44760cf1d4
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
"ignore@npm:^5.2.0, ignore@npm:^5.3.1":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 5.3.1
resolution: "ignore@npm:5.3.1"
checksum: 10c0/703f7f45ffb2a27fb2c5a8db0c32e7dee66b33a225d28e8db4e1be6474795f606686a6e3bcc50e1aa12f2042db4c9d4a7d60af3250511de74620fbed052ea4cd
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"immer@npm:^9.0.6":
version: 9.0.21
resolution: "immer@npm:9.0.21"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/03ea3ed5d4d72e8bd428df4a38ad7e483ea8308e9a113d3b42e0ea2cc0cc38340eb0a6aca69592abbbf047c685dbda04e3d34bf2ff438ab57339ed0a34cc0a05
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"import-fresh@npm:^3.2.1":
version: 3.3.0
resolution: "import-fresh@npm:3.3.0"
dependencies:
parent-module: "npm:^1.0.0"
resolve-from: "npm:^4.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/7f882953aa6b740d1f0e384d0547158bc86efbf2eea0f1483b8900a6f65c5a5123c2cf09b0d542cc419d0b98a759ecaeb394237e97ea427f2da221dc3cd80cc3
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"impress@workspace:.":
version: 0.0.0-use.local
resolution: "impress@workspace:."
dependencies:
"@apollo/client": "npm:^3.6.9"
"@chakra-ui/icons": "npm:^1.0.4"
"@chakra-ui/react": "npm:^1.6.0"
"@emotion/react": "npm:^11.1.4"
"@emotion/styled": "npm:^11.0.0"
Add Turbo to speed up the app, and set up for missing UJS features Oh right, we don't have Rails UJS going on anymore, which is what handled the confirmation prompts for deleting lists. Turbo is the more standard modern solution to that, and should speed up certain pageloads, so let's do it! Here I install the `turbo-rails` gem, then run `rails turbo:install` to install the `@hotwired/turbo-rails` npm package. Then I move `application.js` that's run all on pages but the outfit editor into our section of JS that gets run through the bundler, and add Turbo to it. I had to fix a couple tricky things: 1. The outfit editor page doesn't play nice with being swapped into the document, so I make it require a full page reload instead. 2. Prefetching the Sign In link can cause the wrong `return_to` address to be written to the `session`. (It's a GET request that does, ever so slightly, take its own actions, oops!) As a simple hacky answer, we disallow prefetching on that link. Haven't fixed up the UJS stuff for confirm prompts to use Turbo yet, that's next!
2024-03-13 13:43:48 -07:00
"@hotwired/turbo-rails": "npm:^8.0.4"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"@loadable/component": "npm:^5.12.0"
"@sentry/react": "npm:^5.30.0"
"@sentry/tracing": "npm:^5.30.0"
"@tanstack/react-query": "npm:^5.4.3"
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
"@typescript-eslint/eslint-plugin": "npm:^7.8.0"
"@typescript-eslint/parser": "npm:^7.8.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
apollo-link-persisted-queries: "npm:^0.2.2"
easeljs: "npm:^1.0.2"
esbuild: "npm:^0.19.0"
eslint: "npm:^8.52.0"
eslint-plugin-jsx-a11y: "npm:^6.8.0"
eslint-plugin-react: "npm:^7.33.2"
eslint-plugin-react-hooks: "npm:^4.6.0"
Split NeoPass dev server into main/backing servers
2024-03-13 13:00:27 -07:00
express: "npm:^4.18.3"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
framer-motion: "npm:^4.1.11"
graphql: "npm:^15.5.0"
graphql-tag: "npm:^2.12.6"
husky: "npm:^8.0.3"
immer: "npm:^9.0.6"
lru-cache: "npm:^6.0.0"
Split NeoPass dev server into main/backing servers
2024-03-13 13:00:27 -07:00
node-fetch: "npm:^3.3.2"
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
oauth2-mock-server: "npm:^7.1.1"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
prettier: "npm:^3.0.3"
react: "npm:^18.2.0"
react-autosuggest: "npm:^10.0.2"
react-dom: "npm:^18.2.0"
react-icons: "npm:^4.2.0"
react-router-dom: "npm:^6.15.0"
react-transition-group: "npm:^4.3.0"
tweenjs: "npm:^1.0.2"
typescript: "npm:^5.2.2"
languageName: unknown
linkType: soft
"imurmurhash@npm:^0.1.4":
version: 0.1.4
resolution: "imurmurhash@npm:0.1.4"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/8b51313850dd33605c6c9d3fd9638b714f4c4c40250cff658209f30d40da60f78992fb2df5dabee4acf589a6a82bbc79ad5486550754bd9ec4e3fc0d4a57d6a6
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"inflight@npm:^1.0.4":
version: 1.0.6
resolution: "inflight@npm:1.0.6"
dependencies:
once: "npm:^1.3.0"
wrappy: "npm:1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/7faca22584600a9dc5b9fca2cd5feb7135ac8c935449837b315676b4c90aa4f391ec4f42240178244b5a34e8bede1948627fda392ca3191522fc46b34e985ab2
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"inherits@npm:2, inherits@npm:2.0.4, inherits@npm:^2.0.3":
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
version: 2.0.4
resolution: "inherits@npm:2.0.4"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/4e531f648b29039fb7426fb94075e6545faa1eb9fe83c29f0b6d9e7263aceb4289d2d4557db0d428188eeb449cc7c5e77b0a0b2c4e248ff2a65933a0dee49ef2
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"internal-slot@npm:^1.0.7":
version: 1.0.7
resolution: "internal-slot@npm:1.0.7"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
es-errors: "npm:^1.3.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
hasown: "npm:^2.0.0"
side-channel: "npm:^1.0.4"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/f8b294a4e6ea3855fc59551bbf35f2b832cf01fd5e6e2a97f5c201a071cc09b49048f856e484b67a6c721da5e55736c5b6ddafaf19e2dbeb4a3ff1821680de6c
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"invariant@npm:^2.2.4":
version: 2.2.4
resolution: "invariant@npm:2.2.4"
dependencies:
loose-envify: "npm:^1.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/5af133a917c0bcf65e84e7f23e779e7abc1cd49cb7fdc62d00d1de74b0d8c1b5ee74ac7766099fb3be1b05b26dfc67bab76a17030d2fe7ea2eef867434362dfc
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"ipaddr.js@npm:1.9.1":
version: 1.9.1
resolution: "ipaddr.js@npm:1.9.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/0486e775047971d3fdb5fb4f063829bac45af299ae0b82dcf3afa2145338e08290563a2a70f34b732d795ecc8311902e541a8530eeb30d75860a78ff4e94ce2a
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"is-array-buffer@npm:^3.0.4":
version: 3.0.4
resolution: "is-array-buffer@npm:3.0.4"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
call-bind: "npm:^1.0.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
get-intrinsic: "npm:^1.2.1"
checksum: 10c0/42a49d006cc6130bc5424eae113e948c146f31f9d24460fc0958f855d9d810e6fd2e4519bf19aab75179af9c298ea6092459d8cafdec523cd19e529b26eab860
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"is-arrayish@npm:^0.2.1":
version: 0.2.1
resolution: "is-arrayish@npm:0.2.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/e7fb686a739068bb70f860b39b67afc62acc62e36bb61c5f965768abce1873b379c563e61dd2adad96ebb7edf6651111b385e490cf508378959b0ed4cac4e729
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"is-async-function@npm:^2.0.0":
version: 2.0.0
resolution: "is-async-function@npm:2.0.0"
dependencies:
has-tostringtag: "npm:^1.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/787bc931576aad525d751fc5ce211960fe91e49ac84a5c22d6ae0bc9541945fbc3f686dc590c3175722ce4f6d7b798a93f6f8ff4847fdb2199aea6f4baf5d668
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"is-bigint@npm:^1.0.1":
version: 1.0.4
resolution: "is-bigint@npm:1.0.4"
dependencies:
has-bigints: "npm:^1.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/eb9c88e418a0d195ca545aff2b715c9903d9b0a5033bc5922fec600eb0c3d7b1ee7f882dbf2e0d5a6e694e42391be3683e4368737bd3c4a77f8ac293e7773696
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"is-boolean-object@npm:^1.1.0":
version: 1.1.2
resolution: "is-boolean-object@npm:1.1.2"
dependencies:
call-bind: "npm:^1.0.2"
has-tostringtag: "npm:^1.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/6090587f8a8a8534c0f816da868bc94f32810f08807aa72fa7e79f7e11c466d281486ffe7a788178809c2aa71fe3e700b167fe80dd96dad68026bfff8ebf39f7
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"is-callable@npm:^1.1.3, is-callable@npm:^1.1.4, is-callable@npm:^1.2.7":
version: 1.2.7
resolution: "is-callable@npm:1.2.7"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/ceebaeb9d92e8adee604076971dd6000d38d6afc40bb843ea8e45c5579b57671c3f3b50d7f04869618242c6cee08d1b67806a8cb8edaaaf7c0748b3720d6066f
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"is-core-module@npm:^2.13.0":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 2.13.1
resolution: "is-core-module@npm:2.13.1"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
hasown: "npm:^2.0.0"
checksum: 10c0/2cba9903aaa52718f11c4896dabc189bab980870aae86a62dc0d5cedb546896770ee946fb14c84b7adf0735f5eaea4277243f1b95f5cefa90054f92fbcac2518
languageName: node
linkType: hard
"is-data-view@npm:^1.0.1":
version: 1.0.1
resolution: "is-data-view@npm:1.0.1"
dependencies:
is-typed-array: "npm:^1.1.13"
checksum: 10c0/a3e6ec84efe303da859107aed9b970e018e2bee7ffcb48e2f8096921a493608134240e672a2072577e5f23a729846241d9634806e8a0e51d9129c56d5f65442d
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"is-date-object@npm:^1.0.1, is-date-object@npm:^1.0.5":
version: 1.0.5
resolution: "is-date-object@npm:1.0.5"
dependencies:
has-tostringtag: "npm:^1.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/eed21e5dcc619c48ccef804dfc83a739dbb2abee6ca202838ee1bd5f760fe8d8a93444f0d49012ad19bb7c006186e2884a1b92f6e1c056da7fd23d0a9ad5992e
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"is-extglob@npm:^2.1.1":
version: 2.1.1
resolution: "is-extglob@npm:2.1.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/5487da35691fbc339700bbb2730430b07777a3c21b9ebaecb3072512dfd7b4ba78ac2381a87e8d78d20ea08affb3f1971b4af629173a6bf435ff8a4c47747912
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"is-finalizationregistry@npm:^1.0.2":
version: 1.0.2
resolution: "is-finalizationregistry@npm:1.0.2"
dependencies:
call-bind: "npm:^1.0.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/81caecc984d27b1a35c68741156fc651fb1fa5e3e6710d21410abc527eb226d400c0943a167922b2e920f6b3e58b0dede9aa795882b038b85f50b3a4b877db86
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"is-generator-function@npm:^1.0.10":
version: 1.0.10
resolution: "is-generator-function@npm:1.0.10"
dependencies:
has-tostringtag: "npm:^1.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/df03514df01a6098945b5a0cfa1abff715807c8e72f57c49a0686ad54b3b74d394e2d8714e6f709a71eb00c9630d48e73ca1796c1ccc84ac95092c1fecc0d98b
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"is-glob@npm:^4.0.0, is-glob@npm:^4.0.1, is-glob@npm:^4.0.3":
version: 4.0.3
resolution: "is-glob@npm:4.0.3"
dependencies:
is-extglob: "npm:^2.1.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/17fb4014e22be3bbecea9b2e3a76e9e34ff645466be702f1693e8f1ee1adac84710d0be0bd9f967d6354036fd51ab7c2741d954d6e91dae6bb69714de92c197a
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"is-map@npm:^2.0.3":
version: 2.0.3
resolution: "is-map@npm:2.0.3"
checksum: 10c0/2c4d431b74e00fdda7162cd8e4b763d6f6f217edf97d4f8538b94b8702b150610e2c64961340015fe8df5b1fcee33ccd2e9b62619c4a8a3a155f8de6d6d355fc
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"is-negative-zero@npm:^2.0.3":
version: 2.0.3
resolution: "is-negative-zero@npm:2.0.3"
checksum: 10c0/bcdcf6b8b9714063ffcfa9929c575ac69bfdabb8f4574ff557dfc086df2836cf07e3906f5bbc4f2a5c12f8f3ba56af640c843cdfc74da8caed86c7c7d66fd08e
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"is-number-object@npm:^1.0.4":
version: 1.0.7
resolution: "is-number-object@npm:1.0.7"
dependencies:
has-tostringtag: "npm:^1.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/aad266da1e530f1804a2b7bd2e874b4869f71c98590b3964f9d06cc9869b18f8d1f4778f838ecd2a11011bce20aeecb53cb269ba916209b79c24580416b74b1b
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"is-number@npm:^7.0.0":
version: 7.0.0
resolution: "is-number@npm:7.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/b4686d0d3053146095ccd45346461bc8e53b80aeb7671cc52a4de02dbbf7dc0d1d2a986e2fe4ae206984b4d34ef37e8b795ebc4f4295c978373e6575e295d811
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"is-path-inside@npm:^3.0.3":
version: 3.0.3
resolution: "is-path-inside@npm:3.0.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/cf7d4ac35fb96bab6a1d2c3598fe5ebb29aafb52c0aaa482b5a3ed9d8ba3edc11631e3ec2637660c44b3ce0e61a08d54946e8af30dec0b60a7c27296c68ffd05
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"is-plain-object@npm:^5.0.0":
version: 5.0.0
resolution: "is-plain-object@npm:5.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/893e42bad832aae3511c71fd61c0bf61aa3a6d853061c62a307261842727d0d25f761ce9379f7ba7226d6179db2a3157efa918e7fe26360f3bf0842d9f28942c
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"is-regex@npm:^1.1.4":
version: 1.1.4
resolution: "is-regex@npm:1.1.4"
dependencies:
call-bind: "npm:^1.0.2"
has-tostringtag: "npm:^1.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/bb72aae604a69eafd4a82a93002058c416ace8cde95873589a97fc5dac96a6c6c78a9977d487b7b95426a8f5073969124dd228f043f9f604f041f32fcc465fc1
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"is-set@npm:^2.0.3":
version: 2.0.3
resolution: "is-set@npm:2.0.3"
checksum: 10c0/f73732e13f099b2dc879c2a12341cfc22ccaca8dd504e6edae26484bd5707a35d503fba5b4daad530a9b088ced1ae6c9d8200fd92e09b428fe14ea79ce8080b7
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"is-shared-array-buffer@npm:^1.0.2, is-shared-array-buffer@npm:^1.0.3":
version: 1.0.3
resolution: "is-shared-array-buffer@npm:1.0.3"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
call-bind: "npm:^1.0.7"
checksum: 10c0/adc11ab0acbc934a7b9e5e9d6c588d4ec6682f6fea8cda5180721704fa32927582ede5b123349e32517fdadd07958973d24716c80e7ab198970c47acc09e59c7
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"is-string@npm:^1.0.5, is-string@npm:^1.0.7":
version: 1.0.7
resolution: "is-string@npm:1.0.7"
dependencies:
has-tostringtag: "npm:^1.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/905f805cbc6eedfa678aaa103ab7f626aac9ebbdc8737abb5243acaa61d9820f8edc5819106b8fcd1839e33db21de9f0116ae20de380c8382d16dc2a601921f6
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"is-symbol@npm:^1.0.2, is-symbol@npm:^1.0.3":
version: 1.0.4
resolution: "is-symbol@npm:1.0.4"
dependencies:
has-symbols: "npm:^1.0.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/9381dd015f7c8906154dbcbf93fad769de16b4b961edc94f88d26eb8c555935caa23af88bda0c93a18e65560f6d7cca0fd5a3f8a8e1df6f1abbb9bead4502ef7
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"is-typed-array@npm:^1.1.13":
version: 1.1.13
resolution: "is-typed-array@npm:1.1.13"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
which-typed-array: "npm:^1.1.14"
checksum: 10c0/fa5cb97d4a80e52c2cc8ed3778e39f175a1a2ae4ddf3adae3187d69586a1fd57cfa0b095db31f66aa90331e9e3da79184cea9c6abdcd1abc722dc3c3edd51cca
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"is-weakmap@npm:^2.0.2":
version: 2.0.2
resolution: "is-weakmap@npm:2.0.2"
checksum: 10c0/443c35bb86d5e6cc5929cd9c75a4024bb0fff9586ed50b092f94e700b89c43a33b186b76dbc6d54f3d3d09ece689ab38dcdc1af6a482cbe79c0f2da0a17f1299
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"is-weakref@npm:^1.0.2":
version: 1.0.2
resolution: "is-weakref@npm:1.0.2"
dependencies:
call-bind: "npm:^1.0.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/1545c5d172cb690c392f2136c23eec07d8d78a7f57d0e41f10078aa4f5daf5d7f57b6513a67514ab4f073275ad00c9822fc8935e00229d0a2089e1c02685d4b1
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"is-weakset@npm:^2.0.3":
version: 2.0.3
resolution: "is-weakset@npm:2.0.3"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
call-bind: "npm:^1.0.7"
get-intrinsic: "npm:^1.2.4"
checksum: 10c0/8ad6141b6a400e7ce7c7442a13928c676d07b1f315ab77d9912920bf5f4170622f43126f111615788f26c3b1871158a6797c862233124507db0bcc33a9537d1a
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"isarray@npm:^2.0.5":
version: 2.0.5
resolution: "isarray@npm:2.0.5"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/4199f14a7a13da2177c66c31080008b7124331956f47bca57dd0b6ea9f11687aa25e565a2c7a2b519bc86988d10398e3049a1f5df13c9f6b7664154690ae79fd
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"isexe@npm:^2.0.0":
version: 2.0.0
resolution: "isexe@npm:2.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/228cfa503fadc2c31596ab06ed6aa82c9976eec2bfd83397e7eaf06d0ccf42cd1dfd6743bf9aeb01aebd4156d009994c5f76ea898d2832c1fe342da923ca457d
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"iterator.prototype@npm:^1.1.2":
version: 1.1.2
resolution: "iterator.prototype@npm:1.1.2"
dependencies:
define-properties: "npm:^1.2.1"
get-intrinsic: "npm:^1.2.1"
has-symbols: "npm:^1.0.3"
reflect.getprototypeof: "npm:^1.0.4"
set-function-name: "npm:^2.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/a32151326095e916f306990d909f6bbf23e3221999a18ba686419535dcd1749b10ded505e89334b77dc4c7a58a8508978f0eb16c2c8573e6d412eb7eb894ea79
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"jose@npm:^4.15.4":
version: 4.15.5
resolution: "jose@npm:4.15.5"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/9f208492f55ae9c547fd407c36f67ec3385051b5ca390e24f5449740f17359640b3f96fabfd38bc132cc4292b964c31b921bf356253373b1bd3eb6df799b7433
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"js-tokens@npm:^3.0.0 || ^4.0.0, js-tokens@npm:^4.0.0":
version: 4.0.0
resolution: "js-tokens@npm:4.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/e248708d377aa058eacf2037b07ded847790e6de892bbad3dac0abba2e759cb9f121b00099a65195616badcb6eca8d14d975cb3e89eb1cfda644756402c8aeed
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"js-yaml@npm:^4.1.0":
version: 4.1.0
resolution: "js-yaml@npm:4.1.0"
dependencies:
argparse: "npm:^2.0.1"
bin:
js-yaml: bin/js-yaml.js
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/184a24b4eaacfce40ad9074c64fd42ac83cf74d8c8cd137718d456ced75051229e5061b8633c3366b8aada17945a7a356b337828c19da92b51ae62126575018f
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"json-buffer@npm:3.0.1":
version: 3.0.1
resolution: "json-buffer@npm:3.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/0d1c91569d9588e7eef2b49b59851f297f3ab93c7b35c7c221e288099322be6b562767d11e4821da500f3219542b9afd2e54c5dc573107c1126ed1080f8e96d7
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"json-parse-even-better-errors@npm:^2.3.0":
version: 2.3.1
resolution: "json-parse-even-better-errors@npm:2.3.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/140932564c8f0b88455432e0f33c4cb4086b8868e37524e07e723f4eaedb9425bdc2bafd71bd1d9765bd15fd1e2d126972bc83990f55c467168c228c24d665f3
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"json-schema-traverse@npm:^0.4.1":
version: 0.4.1
resolution: "json-schema-traverse@npm:0.4.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/108fa90d4cc6f08243aedc6da16c408daf81793bf903e9fd5ab21983cda433d5d2da49e40711da016289465ec2e62e0324dcdfbc06275a607fe3233fde4942ce
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"json-stable-stringify-without-jsonify@npm:^1.0.1":
version: 1.0.1
resolution: "json-stable-stringify-without-jsonify@npm:1.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/cb168b61fd4de83e58d09aaa6425ef71001bae30d260e2c57e7d09a5fd82223e2f22a042dedaab8db23b7d9ae46854b08bb1f91675a8be11c5cffebef5fb66a5
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"jsx-ast-utils@npm:^2.4.1 || ^3.0.0, jsx-ast-utils@npm:^3.3.5":
version: 3.3.5
resolution: "jsx-ast-utils@npm:3.3.5"
dependencies:
array-includes: "npm:^3.1.6"
array.prototype.flat: "npm:^1.3.1"
object.assign: "npm:^4.1.4"
object.values: "npm:^1.1.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/a32679e9cb55469cb6d8bbc863f7d631b2c98b7fc7bf172629261751a6e7bc8da6ae374ddb74d5fbd8b06cf0eb4572287b259813d92b36e384024ed35e4c13e1
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"keyv@npm:^4.5.3":
version: 4.5.4
resolution: "keyv@npm:4.5.4"
dependencies:
json-buffer: "npm:3.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/aa52f3c5e18e16bb6324876bb8b59dd02acf782a4b789c7b2ae21107fab95fab3890ed448d4f8dba80ce05391eeac4bfabb4f02a20221342982f806fa2cf271e
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"language-subtag-registry@npm:^0.3.20":
version: 0.3.22
resolution: "language-subtag-registry@npm:0.3.22"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/d1e09971260a7cd3b9fdeb190d33af0b6e99c8697013537d9aaa15f7856d9d83aee128ba8078e219df0a7cf4b8dd18d1a0c188f6543b500d92a2689d2d114b70
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"language-tags@npm:^1.0.9":
version: 1.0.9
resolution: "language-tags@npm:1.0.9"
dependencies:
language-subtag-registry: "npm:^0.3.20"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/9ab911213c4bd8bd583c850201c17794e52cb0660d1ab6e32558aadc8324abebf6844e46f92b80a5d600d0fbba7eface2c207bfaf270a1c7fd539e4c3a880bff
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"levn@npm:^0.4.1":
version: 0.4.1
resolution: "levn@npm:0.4.1"
dependencies:
prelude-ls: "npm:^1.2.1"
type-check: "npm:~0.4.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/effb03cad7c89dfa5bd4f6989364bfc79994c2042ec5966cb9b95990e2edee5cd8969ddf42616a0373ac49fac1403437deaf6e9050fbbaa3546093a59b9ac94e
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"lines-and-columns@npm:^1.1.6":
version: 1.2.4
resolution: "lines-and-columns@npm:1.2.4"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/3da6ee62d4cd9f03f5dc90b4df2540fb85b352081bee77fe4bbcd12c9000ead7f35e0a38b8d09a9bb99b13223446dd8689ff3c4959807620726d788701a83d2d
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"locate-path@npm:^6.0.0":
version: 6.0.0
resolution: "locate-path@npm:6.0.0"
dependencies:
p-locate: "npm:^5.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/d3972ab70dfe58ce620e64265f90162d247e87159b6126b01314dd67be43d50e96a50b517bce2d9452a79409c7614054c277b5232377de50416564a77ac7aad3
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"lodash.merge@npm:^4.6.2":
version: 4.6.2
resolution: "lodash.merge@npm:4.6.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/402fa16a1edd7538de5b5903a90228aa48eb5533986ba7fa26606a49db2572bf414ff73a2c9f5d5fd36b31c46a5d5c7e1527749c07cbcf965ccff5fbdf32c506
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"lodash.mergewith@npm:4.6.2":
version: 4.6.2
resolution: "lodash.mergewith@npm:4.6.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/4adbed65ff96fd65b0b3861f6899f98304f90fd71e7f1eb36c1270e05d500ee7f5ec44c02ef979b5ddbf75c0a0b9b99c35f0ad58f4011934c4d4e99e5200b3b5
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"loose-envify@npm:^1.0.0, loose-envify@npm:^1.1.0, loose-envify@npm:^1.4.0":
version: 1.4.0
resolution: "loose-envify@npm:1.4.0"
dependencies:
js-tokens: "npm:^3.0.0 || ^4.0.0"
bin:
loose-envify: cli.js
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/655d110220983c1a4b9c0c679a2e8016d4b67f6e9c7b5435ff5979ecdb20d0813f4dec0a08674fcbdd4846a3f07edbb50a36811fd37930b94aaa0d9daceb017e
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"lru-cache@npm:^6.0.0":
version: 6.0.0
resolution: "lru-cache@npm:6.0.0"
dependencies:
yallist: "npm:^4.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/cb53e582785c48187d7a188d3379c181b5ca2a9c78d2bce3e7dee36f32761d1c42983da3fe12b55cb74e1779fa94cdc2e5367c028a9b35317184ede0c07a30a9
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"media-typer@npm:0.3.0":
version: 0.3.0
resolution: "media-typer@npm:0.3.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/d160f31246907e79fed398470285f21bafb45a62869dc469b1c8877f3f064f5eabc4bcc122f9479b8b605bc5c76187d7871cf84c4ee3ecd3e487da1993279928
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
"merge-descriptors@npm:1.0.1":
version: 1.0.1
resolution: "merge-descriptors@npm:1.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/b67d07bd44cfc45cebdec349bb6e1f7b077ee2fd5beb15d1f7af073849208cb6f144fe403e29a36571baf3f4e86469ac39acf13c318381e958e186b2766f54ec
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"merge2@npm:^1.3.0, merge2@npm:^1.4.1":
version: 1.4.1
resolution: "merge2@npm:1.4.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/254a8a4605b58f450308fc474c82ac9a094848081bf4c06778200207820e5193726dc563a0d2c16468810516a5c97d9d3ea0ca6585d23c58ccfff2403e8dbbeb
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"methods@npm:~1.1.2":
version: 1.1.2
resolution: "methods@npm:1.1.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/bdf7cc72ff0a33e3eede03708c08983c4d7a173f91348b4b1e4f47d4cdbf734433ad971e7d1e8c77247d9e5cd8adb81ea4c67b0a2db526b758b2233d7814b8b2
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"micromatch@npm:^4.0.4":
version: 4.0.5
resolution: "micromatch@npm:4.0.5"
dependencies:
braces: "npm:^3.0.2"
picomatch: "npm:^2.3.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/3d6505b20f9fa804af5d8c596cb1c5e475b9b0cd05f652c5b56141cf941bd72adaeb7a436fda344235cef93a7f29b7472efc779fcdb83b478eab0867b95cdeff
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"mime-db@npm:1.52.0":
version: 1.52.0
resolution: "mime-db@npm:1.52.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/0557a01deebf45ac5f5777fe7740b2a5c309c6d62d40ceab4e23da9f821899ce7a900b7ac8157d4548ddbb7beffe9abc621250e6d182b0397ec7f10c7b91a5aa
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
"mime-types@npm:~2.1.24, mime-types@npm:~2.1.34":
version: 2.1.35
resolution: "mime-types@npm:2.1.35"
dependencies:
mime-db: "npm:1.52.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/82fb07ec56d8ff1fc999a84f2f217aa46cb6ed1033fefaabd5785b9a974ed225c90dc72fff460259e66b95b73648596dbcc50d51ed69cdf464af2d237d3149b2
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
"mime@npm:1.6.0":
version: 1.6.0
resolution: "mime@npm:1.6.0"
bin:
mime: cli.js
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/b92cd0adc44888c7135a185bfd0dddc42c32606401c72896a842ae15da71eb88858f17669af41e498b463cd7eb998f7b48939a25b08374c7924a9c8a6f8a81b0
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"minimalistic-assert@npm:^1.0.1":
version: 1.0.1
resolution: "minimalistic-assert@npm:1.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/96730e5601cd31457f81a296f521eb56036e6f69133c0b18c13fe941109d53ad23a4204d946a0d638d7f3099482a0cec8c9bb6d642604612ce43ee536be3dddd
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"minimatch@npm:^3.0.5, minimatch@npm:^3.1.1, minimatch@npm:^3.1.2":
version: 3.1.2
resolution: "minimatch@npm:3.1.2"
dependencies:
brace-expansion: "npm:^1.1.7"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/0262810a8fc2e72cca45d6fd86bd349eee435eb95ac6aa45c9ea2180e7ee875ef44c32b55b5973ceabe95ea12682f6e3725cbb63d7a2d1da3ae1163c8b210311
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
"minimatch@npm:^9.0.4":
version: 9.0.4
resolution: "minimatch@npm:9.0.4"
dependencies:
brace-expansion: "npm:^2.0.1"
checksum: 10c0/2c16f21f50e64922864e560ff97c587d15fd491f65d92a677a344e970fe62aafdbeafe648965fa96d33c061b4d0eabfe0213466203dd793367e7f28658cf6414
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"ms@npm:2.0.0":
version: 2.0.0
resolution: "ms@npm:2.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/f8fda810b39fd7255bbdc451c46286e549794fcc700dc9cd1d25658bbc4dc2563a5de6fe7c60f798a16a60c6ceb53f033cb353f493f0cf63e5199b702943159d
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"ms@npm:2.1.2":
version: 2.1.2
resolution: "ms@npm:2.1.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/a437714e2f90dbf881b5191d35a6db792efbca5badf112f87b9e1c712aace4b4b9b742dd6537f3edf90fd6f684de897cec230abde57e87883766712ddda297cc
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"ms@npm:2.1.3":
version: 2.1.3
resolution: "ms@npm:2.1.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/d924b57e7312b3b63ad21fc5b3dc0af5e78d61a1fc7cfb5457edaf26326bf62be5307cc87ffb6862ef1c2b33b0233cdb5d4f01c4c958cc0d660948b65a287a48
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"natural-compare@npm:^1.4.0":
version: 1.4.0
resolution: "natural-compare@npm:1.4.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/f5f9a7974bfb28a91afafa254b197f0f22c684d4a1731763dda960d2c8e375b36c7d690e0d9dc8fba774c537af14a7e979129bca23d88d052fbeb9466955e447
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"negotiator@npm:0.6.3":
version: 0.6.3
resolution: "negotiator@npm:0.6.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/3ec9fd413e7bf071c937ae60d572bc67155262068ed522cf4b3be5edbe6ddf67d095ec03a3a14ebf8fc8e95f8e1d61be4869db0dbb0de696f6b837358bd43fc2
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Split NeoPass dev server into main/backing servers
2024-03-13 13:00:27 -07:00
"node-domexception@npm:^1.0.0":
version: 1.0.0
resolution: "node-domexception@npm:1.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/5e5d63cda29856402df9472335af4bb13875e1927ad3be861dc5ebde38917aecbf9ae337923777af52a48c426b70148815e890a5d72760f1b4d758cc671b1a2b
Split NeoPass dev server into main/backing servers
2024-03-13 13:00:27 -07:00
languageName: node
linkType: hard
"node-fetch@npm:^3.3.2":
version: 3.3.2
resolution: "node-fetch@npm:3.3.2"
dependencies:
data-uri-to-buffer: "npm:^4.0.0"
fetch-blob: "npm:^3.1.4"
formdata-polyfill: "npm:^4.0.10"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/f3d5e56190562221398c9f5750198b34cf6113aa304e34ee97c94fd300ec578b25b2c2906edba922050fce983338fde0d5d34fcb0fc3336ade5bd0e429ad7538
Split NeoPass dev server into main/backing servers
2024-03-13 13:00:27 -07:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"oauth2-mock-server@npm:^7.1.1":
version: 7.1.1
resolution: "oauth2-mock-server@npm:7.1.1"
dependencies:
basic-auth: "npm:^2.0.1"
cors: "npm:^2.8.5"
express: "npm:^4.18.2"
is-plain-object: "npm:^5.0.0"
jose: "npm:^4.15.4"
bin:
oauth2-mock-server: dist/oauth2-mock-server.js
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/79e0871fa272f0f816cf099977825cfd2faa150a8bd82a88819ce84a4ef920fb42cb99f6af7918095b3d399a46d33f5dd13f79e60ff6a979feb38e4f85f89d8c
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"object-assign@npm:^3.0.0":
version: 3.0.0
resolution: "object-assign@npm:3.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/88d1b93de35a2073df309239486829b8b3252ef86196a0d5e06fae20f9e6e5830a33ccaa1c675bd63191eec4310961797ff577fa586583a92a09ece53e668416
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"object-assign@npm:^4, object-assign@npm:^4.1.1":
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
version: 4.1.1
resolution: "object-assign@npm:4.1.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/1f4df9945120325d041ccf7b86f31e8bcc14e73d29171e37a7903050e96b81323784ec59f93f102ec635bcf6fa8034ba3ea0a8c7e69fa202b87ae3b6cec5a414
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"object-inspect@npm:^1.13.1":
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
version: 1.13.1
resolution: "object-inspect@npm:1.13.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/fad603f408e345c82e946abdf4bfd774260a5ed3e5997a0b057c44153ac32c7271ff19e3a5ae39c858da683ba045ccac2f65245c12763ce4e8594f818f4a648d
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"object-keys@npm:^1.1.1":
version: 1.1.1
resolution: "object-keys@npm:1.1.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/b11f7ccdbc6d406d1f186cdadb9d54738e347b2692a14439ca5ac70c225fa6db46db809711b78589866d47b25fc3e8dee0b4c722ac751e11180f9380e3d8601d
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"object.assign@npm:^4.1.4, object.assign@npm:^4.1.5":
version: 4.1.5
resolution: "object.assign@npm:4.1.5"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
call-bind: "npm:^1.0.5"
define-properties: "npm:^1.2.1"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
has-symbols: "npm:^1.0.3"
object-keys: "npm:^1.1.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/60108e1fa2706f22554a4648299b0955236c62b3685c52abf4988d14fffb0e7731e00aa8c6448397e3eb63d087dcc124a9f21e1980f36d0b2667f3c18bacd469
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"object.entries@npm:^1.1.7":
version: 1.1.8
resolution: "object.entries@npm:1.1.8"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
call-bind: "npm:^1.0.7"
define-properties: "npm:^1.2.1"
es-object-atoms: "npm:^1.0.0"
checksum: 10c0/db9ea979d2956a3bc26c262da4a4d212d36f374652cc4c13efdd069c1a519c16571c137e2893d1c46e1cb0e15c88fd6419eaf410c945f329f09835487d7e65d3
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"object.fromentries@npm:^2.0.7":
version: 2.0.8
resolution: "object.fromentries@npm:2.0.8"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
call-bind: "npm:^1.0.7"
define-properties: "npm:^1.2.1"
es-abstract: "npm:^1.23.2"
es-object-atoms: "npm:^1.0.0"
checksum: 10c0/cd4327e6c3369cfa805deb4cbbe919bfb7d3aeebf0bcaba291bb568ea7169f8f8cdbcabe2f00b40db0c20cd20f08e11b5f3a5a36fb7dd3fe04850c50db3bf83b
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"object.hasown@npm:^1.1.3":
version: 1.1.4
resolution: "object.hasown@npm:1.1.4"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
define-properties: "npm:^1.2.1"
es-abstract: "npm:^1.23.2"
es-object-atoms: "npm:^1.0.0"
checksum: 10c0/f23187b08d874ef1aea060118c8259eb7f99f93c15a50771d710569534119062b90e087b92952b2d0fb1bb8914d61fb0b43c57fb06f622aaad538fe6868ab987
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"object.values@npm:^1.1.6, object.values@npm:^1.1.7":
version: 1.2.0
resolution: "object.values@npm:1.2.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
call-bind: "npm:^1.0.7"
define-properties: "npm:^1.2.1"
es-object-atoms: "npm:^1.0.0"
checksum: 10c0/15809dc40fd6c5529501324fec5ff08570b7d70fb5ebbe8e2b3901afec35cf2b3dc484d1210c6c642cd3e7e0a5e18dd1d6850115337fef46bdae14ab0cb18ac3
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"on-finished@npm:2.4.1":
version: 2.4.1
resolution: "on-finished@npm:2.4.1"
dependencies:
ee-first: "npm:1.1.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/46fb11b9063782f2d9968863d9cbba33d77aa13c17f895f56129c274318b86500b22af3a160fe9995aa41317efcd22941b6eba747f718ced08d9a73afdb087b4
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"once@npm:^1.3.0":
version: 1.4.0
resolution: "once@npm:1.4.0"
dependencies:
wrappy: "npm:1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/5d48aca287dfefabd756621c5dfce5c91a549a93e9fdb7b8246bc4c4790aa2ec17b34a260530474635147aeb631a2dcc8b32c613df0675f96041cbb8244517d0
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"optimism@npm:^0.18.0":
version: 0.18.0
resolution: "optimism@npm:0.18.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@wry/caches": "npm:^1.0.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"@wry/context": "npm:^0.7.0"
"@wry/trie": "npm:^0.4.3"
tslib: "npm:^2.3.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/8e97c6d660cb80cf5f444209b9dd29ee6951fa7b344d4c4fc6d4aaf0ad0710dddaf834d0f5d7211b3658b15ef6c6a22cbcb98c7a8121e3fee9666fe0fd62d876
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"optionator@npm:^0.9.3":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 0.9.4
resolution: "optionator@npm:0.9.4"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
deep-is: "npm:^0.1.3"
fast-levenshtein: "npm:^2.0.6"
levn: "npm:^0.4.1"
prelude-ls: "npm:^1.2.1"
type-check: "npm:^0.4.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
word-wrap: "npm:^1.2.5"
checksum: 10c0/4afb687a059ee65b61df74dfe87d8d6815cd6883cb8b3d5883a910df72d0f5d029821f37025e4bccf4048873dbdb09acc6d303d27b8f76b1a80dd5a7d5334675
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"p-limit@npm:^3.0.2":
version: 3.1.0
resolution: "p-limit@npm:3.1.0"
dependencies:
yocto-queue: "npm:^0.1.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/9db675949dbdc9c3763c89e748d0ef8bdad0afbb24d49ceaf4c46c02c77d30db4e0652ed36d0a0a7a95154335fab810d95c86153105bb73b3a90448e2bb14e1a
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"p-locate@npm:^5.0.0":
version: 5.0.0
resolution: "p-locate@npm:5.0.0"
dependencies:
p-limit: "npm:^3.0.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/2290d627ab7903b8b70d11d384fee714b797f6040d9278932754a6860845c4d3190603a0772a663c8cb5a7b21d1b16acb3a6487ebcafa9773094edc3dfe6009a
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"parent-module@npm:^1.0.0":
version: 1.0.1
resolution: "parent-module@npm:1.0.1"
dependencies:
callsites: "npm:^3.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/c63d6e80000d4babd11978e0d3fee386ca7752a02b035fd2435960ffaa7219dc42146f07069fb65e6e8bf1caef89daf9af7535a39bddf354d78bf50d8294f556
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"parse-json@npm:^5.0.0":
version: 5.2.0
resolution: "parse-json@npm:5.2.0"
dependencies:
"@babel/code-frame": "npm:^7.0.0"
error-ex: "npm:^1.3.1"
json-parse-even-better-errors: "npm:^2.3.0"
lines-and-columns: "npm:^1.1.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/77947f2253005be7a12d858aedbafa09c9ae39eb4863adf330f7b416ca4f4a08132e453e08de2db46459256fb66afaac5ee758b44fe6541b7cdaf9d252e59585
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"parseurl@npm:~1.3.3":
version: 1.3.3
resolution: "parseurl@npm:1.3.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/90dd4760d6f6174adb9f20cf0965ae12e23879b5f5464f38e92fce8073354341e4b3b76fa3d878351efe7d01e617121955284cfd002ab087fba1a0726ec0b4f5
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"path-exists@npm:^4.0.0":
version: 4.0.0
resolution: "path-exists@npm:4.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/8c0bd3f5238188197dc78dced15207a4716c51cc4e3624c44fc97acf69558f5ebb9a2afff486fe1b4ee148e0c133e96c5e11a9aa5c48a3006e3467da070e5e1b
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"path-is-absolute@npm:^1.0.0":
version: 1.0.1
resolution: "path-is-absolute@npm:1.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/127da03c82172a2a50099cddbf02510c1791fc2cc5f7713ddb613a56838db1e8168b121a920079d052e0936c23005562059756d653b7c544c53185efe53be078
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"path-key@npm:^3.1.0":
version: 3.1.1
resolution: "path-key@npm:3.1.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/748c43efd5a569c039d7a00a03b58eecd1d75f3999f5a28303d75f521288df4823bc057d8784eb72358b2895a05f29a070bc9f1f17d28226cc4e62494cc58c4c
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"path-parse@npm:^1.0.7":
version: 1.0.7
resolution: "path-parse@npm:1.0.7"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/11ce261f9d294cc7a58d6a574b7f1b935842355ec66fba3c3fd79e0f036462eaf07d0aa95bb74ff432f9afef97ce1926c720988c6a7451d8a584930ae7de86e1
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"path-to-regexp@npm:0.1.7":
version: 0.1.7
resolution: "path-to-regexp@npm:0.1.7"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/50a1ddb1af41a9e68bd67ca8e331a705899d16fb720a1ea3a41e310480948387daf603abb14d7b0826c58f10146d49050a1291ba6a82b78a382d1c02c0b8f905
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"path-type@npm:^4.0.0":
version: 4.0.0
resolution: "path-type@npm:4.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/666f6973f332f27581371efaf303fd6c272cc43c2057b37aa99e3643158c7e4b2626549555d88626e99ea9e046f82f32e41bbde5f1508547e9a11b149b52387c
languageName: node
linkType: hard
"picocolors@npm:^1.0.0":
version: 1.0.0
resolution: "picocolors@npm:1.0.0"
checksum: 10c0/20a5b249e331c14479d94ec6817a182fd7a5680debae82705747b2db7ec50009a5f6648d0621c561b0572703f84dbef0858abcbd5856d3c5511426afcb1961f7
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"picomatch@npm:^2.3.1":
version: 2.3.1
resolution: "picomatch@npm:2.3.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/26c02b8d06f03206fc2ab8d16f19960f2ff9e81a658f831ecb656d8f17d9edc799e8364b1f4a7873e89d9702dff96204be0fa26fe4181f6843f040f819dac4be
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"popmotion@npm:9.3.6":
version: 9.3.6
resolution: "popmotion@npm:9.3.6"
dependencies:
framesync: "npm:5.3.0"
hey-listen: "npm:^1.0.8"
style-value-types: "npm:4.1.4"
tslib: "npm:^2.1.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/c0936cbd00006f2872eaa4716e176399f11622369a216f397ac6bc690d9211b993f94a8336586fd4ab9f67a53d6dc9098ec485874542e559a357be2050605f7a
languageName: node
linkType: hard
"possible-typed-array-names@npm:^1.0.0":
version: 1.0.0
resolution: "possible-typed-array-names@npm:1.0.0"
checksum: 10c0/d9aa22d31f4f7680e20269db76791b41c3a32c01a373e25f8a4813b4d45f7456bfc2b6d68f752dc4aab0e0bb0721cb3d76fb678c9101cb7a16316664bc2c73fd
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"prelude-ls@npm:^1.2.1":
version: 1.2.1
resolution: "prelude-ls@npm:1.2.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/b00d617431e7886c520a6f498a2e14c75ec58f6d93ba48c3b639cf241b54232d90daa05d83a9e9b9fef6baa63cb7e1e4602c2372fea5bc169668401eb127d0cd
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"prettier@npm:^3.0.3":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 3.2.5
resolution: "prettier@npm:3.2.5"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
bin:
prettier: bin/prettier.cjs
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/ea327f37a7d46f2324a34ad35292af2ad4c4c3c3355da07313339d7e554320f66f65f91e856add8530157a733c6c4a897dc41b577056be5c24c40f739f5ee8c6
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"prop-types@npm:^15.6.2, prop-types@npm:^15.7.2, prop-types@npm:^15.8.1":
version: 15.8.1
resolution: "prop-types@npm:15.8.1"
dependencies:
loose-envify: "npm:^1.4.0"
object-assign: "npm:^4.1.1"
react-is: "npm:^16.13.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/59ece7ca2fb9838031d73a48d4becb9a7cc1ed10e610517c7d8f19a1e02fa47f7c27d557d8a5702bec3cfeccddc853579832b43f449e54635803f277b1c78077
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"proxy-addr@npm:~2.0.7":
version: 2.0.7
resolution: "proxy-addr@npm:2.0.7"
dependencies:
forwarded: "npm:0.2.0"
ipaddr.js: "npm:1.9.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/c3eed999781a35f7fd935f398b6d8920b6fb00bbc14287bc6de78128ccc1a02c89b95b56742bf7cf0362cc333c61d138532049c7dedc7a328ef13343eff81210
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"punycode@npm:^2.1.0":
version: 2.3.1
resolution: "punycode@npm:2.3.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/14f76a8206bc3464f794fb2e3d3cc665ae416c01893ad7a02b23766eb07159144ee612ad67af5e84fa4479ccfe67678c4feb126b0485651b302babf66f04f9e9
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"qs@npm:6.11.0":
version: 6.11.0
resolution: "qs@npm:6.11.0"
dependencies:
side-channel: "npm:^1.0.4"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/4e4875e4d7c7c31c233d07a448e7e4650f456178b9dd3766b7cfa13158fdb24ecb8c4f059fa91e820dc6ab9f2d243721d071c9c0378892dcdad86e9e9a27c68f
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"queue-microtask@npm:^1.2.2":
version: 1.2.3
resolution: "queue-microtask@npm:1.2.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/900a93d3cdae3acd7d16f642c29a642aea32c2026446151f0778c62ac089d4b8e6c986811076e1ae180a694cedf077d453a11b58ff0a865629a4f82ab558e102
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"range-parser@npm:~1.2.1":
version: 1.2.1
resolution: "range-parser@npm:1.2.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/96c032ac2475c8027b7a4e9fe22dc0dfe0f6d90b85e496e0f016fbdb99d6d066de0112e680805075bd989905e2123b3b3d002765149294dce0c1f7f01fcc2ea0
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
"raw-body@npm:2.5.2":
version: 2.5.2
resolution: "raw-body@npm:2.5.2"
dependencies:
bytes: "npm:3.1.2"
http-errors: "npm:2.0.0"
iconv-lite: "npm:0.4.24"
unpipe: "npm:1.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/b201c4b66049369a60e766318caff5cb3cc5a900efd89bdac431463822d976ad0670912c931fdbdcf5543207daf6f6833bca57aa116e1661d2ea91e12ca692c4
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"react-autosuggest@npm:^10.0.2":
version: 10.1.0
resolution: "react-autosuggest@npm:10.1.0"
dependencies:
es6-promise: "npm:^4.2.8"
prop-types: "npm:^15.7.2"
react-themeable: "npm:^1.1.0"
section-iterator: "npm:^2.0.0"
shallow-equal: "npm:^1.2.1"
peerDependencies:
react: ">=16.3.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/30e8432bc7e9c6a1e8ec5024de4d391f96cd29638d2040de7d348742b534fd4a1f0cd511d08f9bab5104651b31456bf3cbbe5714810458442caec293d5d34880
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"react-clientside-effect@npm:^1.2.5":
version: 1.2.6
resolution: "react-clientside-effect@npm:1.2.6"
dependencies:
"@babel/runtime": "npm:^7.12.13"
peerDependencies:
react: ^15.3.0 || ^16.0.0 || ^17.0.0 || ^18.0.0
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/aba0adb666018e5c64657c31f4914a8558be73f71d6e2210fa871ebfcab94d786c83082868d7c7fa66feddc2aec19e375745cf0903e0619f2efffef08b92d941
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"react-dom@npm:^18.2.0":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 18.3.1
resolution: "react-dom@npm:18.3.1"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
loose-envify: "npm:^1.1.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
scheduler: "npm:^0.23.2"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
peerDependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
react: ^18.3.1
checksum: 10c0/a752496c1941f958f2e8ac56239172296fcddce1365ce45222d04a1947e0cc5547df3e8447f855a81d6d39f008d7c32eab43db3712077f09e3f67c4874973e85
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"react-fast-compare@npm:3.2.0":
version: 3.2.0
resolution: "react-fast-compare@npm:3.2.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/2a7d75ce9fb5da1e3c01f74a5cd592f3369a8cc8d44e93654bf147ab221f430238e8be70677e896f2bfcb96a1cb7a47a8d05d84633de764a9d57d27005a4bb9e
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"react-focus-lock@npm:2.5.2":
version: 2.5.2
resolution: "react-focus-lock@npm:2.5.2"
dependencies:
"@babel/runtime": "npm:^7.0.0"
focus-lock: "npm:^0.9.1"
prop-types: "npm:^15.6.2"
react-clientside-effect: "npm:^1.2.5"
use-callback-ref: "npm:^1.2.5"
use-sidecar: "npm:^1.0.5"
peerDependencies:
react: ^16.8.0 || ^17.0.0
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/f8a33b9199bed1c7a1ebc016da880b0277ae798418adfacd0d356f64314556cddca764f1b595ef3253a6710f336b5e2309f6a8f5b3ac7c7ae0e3c80427f879f9
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"react-icons@npm:^4.2.0":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 4.12.0
resolution: "react-icons@npm:4.12.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
peerDependencies:
react: "*"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/2170f43031ee7365539f72d4075cbe6c7fbf9a66d6cf4494aa9393b194272da0564f5b19d1b24dbfc567c0ac89f5fe5b8974d92dd83f61e252388dde6a226fb8
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"react-is@npm:^16.12.0, react-is@npm:^16.13.1, react-is@npm:^16.7.0":
version: 16.13.1
resolution: "react-is@npm:16.13.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/33977da7a5f1a287936a0c85639fec6ca74f4f15ef1e59a6bc20338fc73dc69555381e211f7a3529b8150a1f71e4225525b41b60b52965bda53ce7d47377ada1
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"react-remove-scroll-bar@npm:^2.1.0":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 2.3.6
resolution: "react-remove-scroll-bar@npm:2.3.6"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
react-style-singleton: "npm:^2.2.1"
tslib: "npm:^2.0.0"
peerDependencies:
"@types/react": ^16.8.0 || ^17.0.0 || ^18.0.0
react: ^16.8.0 || ^17.0.0 || ^18.0.0
peerDependenciesMeta:
"@types/react":
optional: true
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/4e32ee04bf655a8bd3b4aacf6ffc596ae9eb1b9ba27eef83f7002632ee75371f61516ae62250634a9eae4b2c8fc6f6982d9b182de260f6c11841841e6e2e7515
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"react-remove-scroll@npm:2.4.1":
version: 2.4.1
resolution: "react-remove-scroll@npm:2.4.1"
dependencies:
react-remove-scroll-bar: "npm:^2.1.0"
react-style-singleton: "npm:^2.1.0"
tslib: "npm:^1.0.0"
use-callback-ref: "npm:^1.2.3"
use-sidecar: "npm:^1.0.1"
peerDependencies:
"@types/react": ^16.8.0 || ^17.0.0
react: ^16.8.0 || ^17.0.0
peerDependenciesMeta:
"@types/react":
optional: true
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/08cac29ba800dfafc67c8fe9a962d16bcdded8bf08a64193cb580549582400c52d71cfabb1ca46478578f92c5d8f16b2d060cb254af5a0d97cb6cec8b177e065
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"react-router-dom@npm:^6.15.0":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 6.23.0
resolution: "react-router-dom@npm:6.23.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@remix-run/router": "npm:1.16.0"
react-router: "npm:6.23.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
peerDependencies:
react: ">=16.8"
react-dom: ">=16.8"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/c249f3ca44a9e73cb931665563273c7d69709e9dbc9532f145cb6d9a3b3874f18c0752e2d949090b6d139d915ae14a3cbdfedb351c731a8202e20bbcfc800fd4
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"react-router@npm:6.23.0":
version: 6.23.0
resolution: "react-router@npm:6.23.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"@remix-run/router": "npm:1.16.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
peerDependencies:
react: ">=16.8"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/567eb764d0814a9af2ea83c7d0bcf8a0a49d7070b4a7fffbbe8a4e4a376ca4e6adaa762b47760b110993eb2773fc617da7e26ab564d59cfd768130671a1b990e
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"react-style-singleton@npm:^2.1.0, react-style-singleton@npm:^2.2.1":
version: 2.2.1
resolution: "react-style-singleton@npm:2.2.1"
dependencies:
get-nonce: "npm:^1.0.0"
invariant: "npm:^2.2.4"
tslib: "npm:^2.0.0"
peerDependencies:
"@types/react": ^16.8.0 || ^17.0.0 || ^18.0.0
react: ^16.8.0 || ^17.0.0 || ^18.0.0
peerDependenciesMeta:
"@types/react":
optional: true
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/6d66f3bdb65e1ec79089f80314da97c9a005087a04ee034255a5de129a4c0d9fd0bf99fa7bf642781ac2dc745ca687aae3de082bd8afdd0d117bc953241e15ad
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"react-themeable@npm:^1.1.0":
version: 1.1.0
resolution: "react-themeable@npm:1.1.0"
dependencies:
object-assign: "npm:^3.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/08804b8bee88b483ddc54159c8bf5512615053125223aa57dd702cf871a2244b8e0f5d44de3aa08f10a52d6a959d23537c427fe7a08099a6e02a203370736174
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"react-transition-group@npm:^4.3.0":
version: 4.4.5
resolution: "react-transition-group@npm:4.4.5"
dependencies:
"@babel/runtime": "npm:^7.5.5"
dom-helpers: "npm:^5.0.1"
loose-envify: "npm:^1.4.0"
prop-types: "npm:^15.6.2"
peerDependencies:
react: ">=16.6.0"
react-dom: ">=16.6.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/2ba754ba748faefa15f87c96dfa700d5525054a0141de8c75763aae6734af0740e77e11261a1e8f4ffc08fd9ab78510122e05c21c2d79066c38bb6861a886c82
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"react@npm:^18.2.0":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 18.3.1
resolution: "react@npm:18.3.1"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
loose-envify: "npm:^1.1.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/283e8c5efcf37802c9d1ce767f302dd569dd97a70d9bb8c7be79a789b9902451e0d16334b05d73299b20f048cbc3c7d288bbbde10b701fa194e2089c237dbea3
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"reflect.getprototypeof@npm:^1.0.4":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 1.0.6
resolution: "reflect.getprototypeof@npm:1.0.6"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
call-bind: "npm:^1.0.7"
define-properties: "npm:^1.2.1"
es-abstract: "npm:^1.23.1"
es-errors: "npm:^1.3.0"
get-intrinsic: "npm:^1.2.4"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
globalthis: "npm:^1.0.3"
which-builtin-type: "npm:^1.1.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/baf4ef8ee6ff341600f4720b251cf5a6cb552d6a6ab0fdc036988c451bf16f920e5feb0d46bd4f530a5cce568f1f7aca2d77447ca798920749cfc52783c39b55
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"regenerator-runtime@npm:^0.14.0":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 0.14.1
resolution: "regenerator-runtime@npm:0.14.1"
checksum: 10c0/1b16eb2c4bceb1665c89de70dcb64126a22bc8eb958feef3cd68fe11ac6d2a4899b5cd1b80b0774c7c03591dc57d16631a7f69d2daa2ec98100e2f29f7ec4cc4
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"regexp.prototype.flags@npm:^1.5.2":
version: 1.5.2
resolution: "regexp.prototype.flags@npm:1.5.2"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
call-bind: "npm:^1.0.6"
define-properties: "npm:^1.2.1"
es-errors: "npm:^1.3.0"
set-function-name: "npm:^2.0.1"
checksum: 10c0/0f3fc4f580d9c349f8b560b012725eb9c002f36daa0041b3fbf6f4238cb05932191a4d7d5db3b5e2caa336d5150ad0402ed2be81f711f9308fe7e1a9bf9bd552
languageName: node
linkType: hard
"rehackt@npm:^0.1.0":
version: 0.1.0
resolution: "rehackt@npm:0.1.0"
peerDependencies:
"@types/react": "*"
react: "*"
peerDependenciesMeta:
"@types/react":
optional: true
react:
optional: true
checksum: 10c0/3d838bfee84ec06c976f21027936f3b0fdb7660ab8a2d4d3f19c65e0daa78a268aa81352311352b8576b89a074714b36ae6cd5bdadb6e975eca079f2b342de73
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"resolve-from@npm:^4.0.0":
version: 4.0.0
resolution: "resolve-from@npm:4.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/8408eec31a3112ef96e3746c37be7d64020cda07c03a920f5024e77290a218ea758b26ca9529fd7b1ad283947f34b2291c1c0f6aa0ed34acfdda9c6014c8d190
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"resolve@npm:^1.19.0":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 1.22.8
resolution: "resolve@npm:1.22.8"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
is-core-module: "npm:^2.13.0"
path-parse: "npm:^1.0.7"
supports-preserve-symlinks-flag: "npm:^1.0.0"
bin:
resolve: bin/resolve
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/07e179f4375e1fd072cfb72ad66d78547f86e6196c4014b31cb0b8bb1db5f7ca871f922d08da0fbc05b94e9fd42206f819648fa3b5b873ebbc8e1dc68fec433a
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"resolve@npm:^2.0.0-next.5":
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
version: 2.0.0-next.5
resolution: "resolve@npm:2.0.0-next.5"
dependencies:
is-core-module: "npm:^2.13.0"
path-parse: "npm:^1.0.7"
supports-preserve-symlinks-flag: "npm:^1.0.0"
bin:
resolve: bin/resolve
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/a6c33555e3482ea2ec4c6e3d3bf0d78128abf69dca99ae468e64f1e30acaa318fd267fb66c8836b04d558d3e2d6ed875fe388067e7d8e0de647d3c21af21c43a
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"resolve@patch:resolve@npm%3A^1.19.0#optional!builtin<compat/resolve>":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 1.22.8
resolution: "resolve@patch:resolve@npm%3A1.22.8#optional!builtin<compat/resolve>::version=1.22.8&hash=c3c19d"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
is-core-module: "npm:^2.13.0"
path-parse: "npm:^1.0.7"
supports-preserve-symlinks-flag: "npm:^1.0.0"
bin:
resolve: bin/resolve
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/0446f024439cd2e50c6c8fa8ba77eaa8370b4180f401a96abf3d1ebc770ac51c1955e12764cde449fde3fff480a61f84388e3505ecdbab778f4bef5f8212c729
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"resolve@patch:resolve@npm%3A^2.0.0-next.5#optional!builtin<compat/resolve>":
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
version: 2.0.0-next.5
resolution: "resolve@patch:resolve@npm%3A2.0.0-next.5#optional!builtin<compat/resolve>::version=2.0.0-next.5&hash=c3c19d"
dependencies:
is-core-module: "npm:^2.13.0"
path-parse: "npm:^1.0.7"
supports-preserve-symlinks-flag: "npm:^1.0.0"
bin:
resolve: bin/resolve
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/78ad6edb8309a2bfb720c2c1898f7907a37f858866ce11a5974643af1203a6a6e05b2fa9c53d8064a673a447b83d42569260c306d43628bff5bb101969708355
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"response-iterator@npm:^0.2.6":
version: 0.2.6
resolution: "response-iterator@npm:0.2.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/60e6b552cd610643269d5d916d270cc8a4bea978cbe4779d6ef8083ac6b89006795508034e4c4ebe204eded75ac32bf243589ba82c1184591dde0674f6db785e
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"reusify@npm:^1.0.4":
version: 1.0.4
resolution: "reusify@npm:1.0.4"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/c19ef26e4e188f408922c46f7ff480d38e8dfc55d448310dfb518736b23ed2c4f547fb64a6ed5bdba92cd7e7ddc889d36ff78f794816d5e71498d645ef476107
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"rimraf@npm:^3.0.2":
version: 3.0.2
resolution: "rimraf@npm:3.0.2"
dependencies:
glob: "npm:^7.1.3"
bin:
rimraf: bin.js
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/9cb7757acb489bd83757ba1a274ab545eafd75598a9d817e0c3f8b164238dd90eba50d6b848bd4dcc5f3040912e882dc7ba71653e35af660d77b25c381d402e8
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"run-parallel@npm:^1.1.9":
version: 1.2.0
resolution: "run-parallel@npm:1.2.0"
dependencies:
queue-microtask: "npm:^1.2.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/200b5ab25b5b8b7113f9901bfe3afc347e19bb7475b267d55ad0eb86a62a46d77510cb0f232507c9e5d497ebda569a08a9867d0d14f57a82ad5564d991588b39
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"safe-array-concat@npm:^1.1.2":
version: 1.1.2
resolution: "safe-array-concat@npm:1.1.2"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
call-bind: "npm:^1.0.7"
get-intrinsic: "npm:^1.2.4"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
has-symbols: "npm:^1.0.3"
isarray: "npm:^2.0.5"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/12f9fdb01c8585e199a347eacc3bae7b5164ae805cdc8c6707199dbad5b9e30001a50a43c4ee24dc9ea32dbb7279397850e9208a7e217f4d8b1cf5d90129dec9
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"safe-buffer@npm:5.1.2":
version: 5.1.2
resolution: "safe-buffer@npm:5.1.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/780ba6b5d99cc9a40f7b951d47152297d0e260f0df01472a1b99d4889679a4b94a13d644f7dbc4f022572f09ae9005fa2fbb93bbbd83643316f365a3e9a45b21
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
"safe-buffer@npm:5.2.1":
version: 5.2.1
resolution: "safe-buffer@npm:5.2.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/6501914237c0a86e9675d4e51d89ca3c21ffd6a31642efeba25ad65720bce6921c9e7e974e5be91a786b25aa058b5303285d3c15dbabf983a919f5f630d349f3
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"safe-regex-test@npm:^1.0.3":
version: 1.0.3
resolution: "safe-regex-test@npm:1.0.3"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
call-bind: "npm:^1.0.6"
es-errors: "npm:^1.3.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
is-regex: "npm:^1.1.4"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/900bf7c98dc58f08d8523b7012b468e4eb757afa624f198902c0643d7008ba777b0bdc35810ba0b758671ce887617295fb742b3f3968991b178ceca54cb07603
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"safer-buffer@npm:>= 2.1.2 < 3":
version: 2.1.2
resolution: "safer-buffer@npm:2.1.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/7e3c8b2e88a1841c9671094bbaeebd94448111dd90a81a1f606f3f67708a6ec57763b3b47f06da09fc6054193e0e6709e77325415dc8422b04497a8070fa02d4
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"scheduler@npm:^0.23.2":
version: 0.23.2
resolution: "scheduler@npm:0.23.2"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
loose-envify: "npm:^1.1.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/26383305e249651d4c58e6705d5f8425f153211aef95f15161c151f7b8de885f24751b377e4a0b3dd42cce09aad3f87a61dab7636859c0d89b7daf1a1e2a5c78
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"section-iterator@npm:^2.0.0":
version: 2.0.0
resolution: "section-iterator@npm:2.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/24a88bbf205b1b2daf9da4797fa6b2e135ef291ea91a317ada403fba316cf142716e41f8da2eb27c95ea38ebf603244c4f0b73c8bd1f403f15cba0d4fadc14f6
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"semver@npm:^6.3.1":
version: 6.3.1
resolution: "semver@npm:6.3.1"
bin:
semver: bin/semver.js
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/e3d79b609071caa78bcb6ce2ad81c7966a46a7431d9d58b8800cfa9cb6a63699b3899a0e4bcce36167a284578212d9ae6942b6929ba4aa5015c079a67751d42d
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
"semver@npm:^7.6.0":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 7.6.0
resolution: "semver@npm:7.6.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
lru-cache: "npm:^6.0.0"
bin:
semver: bin/semver.js
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/fbfe717094ace0aa8d6332d7ef5ce727259815bd8d8815700853f4faf23aacbd7192522f0dc5af6df52ef4fa85a355ebd2f5d39f554bd028200d6cf481ab9b53
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"send@npm:0.18.0":
version: 0.18.0
resolution: "send@npm:0.18.0"
dependencies:
debug: "npm:2.6.9"
depd: "npm:2.0.0"
destroy: "npm:1.2.0"
encodeurl: "npm:~1.0.2"
escape-html: "npm:~1.0.3"
etag: "npm:~1.8.1"
fresh: "npm:0.5.2"
http-errors: "npm:2.0.0"
mime: "npm:1.6.0"
ms: "npm:2.1.3"
on-finished: "npm:2.4.1"
range-parser: "npm:~1.2.1"
statuses: "npm:2.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/0eb134d6a51fc13bbcb976a1f4214ea1e33f242fae046efc311e80aff66c7a43603e26a79d9d06670283a13000e51be6e0a2cb80ff0942eaf9f1cd30b7ae736a
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
"serve-static@npm:1.15.0":
version: 1.15.0
resolution: "serve-static@npm:1.15.0"
dependencies:
encodeurl: "npm:~1.0.2"
escape-html: "npm:~1.0.3"
parseurl: "npm:~1.3.3"
send: "npm:0.18.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/fa9f0e21a540a28f301258dfe1e57bb4f81cd460d28f0e973860477dd4acef946a1f41748b5bd41c73b621bea2029569c935faa38578fd34cd42a9b4947088ba
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"set-function-length@npm:^1.2.1":
version: 1.2.2
resolution: "set-function-length@npm:1.2.2"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
define-data-property: "npm:^1.1.4"
es-errors: "npm:^1.3.0"
function-bind: "npm:^1.1.2"
get-intrinsic: "npm:^1.2.4"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
gopd: "npm:^1.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
has-property-descriptors: "npm:^1.0.2"
checksum: 10c0/82850e62f412a258b71e123d4ed3873fa9377c216809551192bb6769329340176f109c2eeae8c22a8d386c76739855f78e8716515c818bcaef384b51110f0f3c
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"set-function-name@npm:^2.0.1, set-function-name@npm:^2.0.2":
version: 2.0.2
resolution: "set-function-name@npm:2.0.2"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
define-data-property: "npm:^1.1.4"
es-errors: "npm:^1.3.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
functions-have-names: "npm:^1.2.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
has-property-descriptors: "npm:^1.0.2"
checksum: 10c0/fce59f90696c450a8523e754abb305e2b8c73586452619c2bad5f7bf38c7b6b4651895c9db895679c5bef9554339cf3ef1c329b66ece3eda7255785fbe299316
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"setprototypeof@npm:1.2.0":
version: 1.2.0
resolution: "setprototypeof@npm:1.2.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/68733173026766fa0d9ecaeb07f0483f4c2dc70ca376b3b7c40b7cda909f94b0918f6c5ad5ce27a9160bdfb475efaa9d5e705a11d8eaae18f9835d20976028bc
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"shallow-equal@npm:^1.2.1":
version: 1.2.1
resolution: "shallow-equal@npm:1.2.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/51e03abadd97c9ebe590547d92db9148446962a3f23a3a0fb1ba2fccab80af881eef0ff1f8ccefd3f066c0bc5a4c8ca53706194813b95c8835fa66448a843a26
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"shebang-command@npm:^2.0.0":
version: 2.0.0
resolution: "shebang-command@npm:2.0.0"
dependencies:
shebang-regex: "npm:^3.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/a41692e7d89a553ef21d324a5cceb5f686d1f3c040759c50aab69688634688c5c327f26f3ecf7001ebfd78c01f3c7c0a11a7c8bfd0a8bc9f6240d4f40b224e4e
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"shebang-regex@npm:^3.0.0":
version: 3.0.0
resolution: "shebang-regex@npm:3.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/1dbed0726dd0e1152a92696c76c7f06084eb32a90f0528d11acd764043aacf76994b2fb30aa1291a21bd019d6699164d048286309a278855ee7bec06cf6fb690
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"side-channel@npm:^1.0.4, side-channel@npm:^1.0.6":
version: 1.0.6
resolution: "side-channel@npm:1.0.6"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
call-bind: "npm:^1.0.7"
es-errors: "npm:^1.3.0"
get-intrinsic: "npm:^1.2.4"
object-inspect: "npm:^1.13.1"
checksum: 10c0/d2afd163dc733cc0a39aa6f7e39bf0c436293510dbccbff446733daeaf295857dbccf94297092ec8c53e2503acac30f0b78830876f0485991d62a90e9cad305f
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"slash@npm:^3.0.0":
version: 3.0.0
resolution: "slash@npm:3.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/e18488c6a42bdfd4ac5be85b2ced3ccd0224773baae6ad42cfbb9ec74fc07f9fa8396bd35ee638084ead7a2a0818eb5e7151111544d4731ce843019dab4be47b
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"source-map@npm:^0.5.7":
version: 0.5.7
resolution: "source-map@npm:0.5.7"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/904e767bb9c494929be013017380cbba013637da1b28e5943b566031e29df04fba57edf3f093e0914be094648b577372bd8ad247fa98cfba9c600794cd16b599
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"statuses@npm:2.0.1":
version: 2.0.1
resolution: "statuses@npm:2.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/34378b207a1620a24804ce8b5d230fea0c279f00b18a7209646d5d47e419d1cc23e7cbf33a25a1e51ac38973dc2ac2e1e9c647a8e481ef365f77668d72becfd0
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"string.prototype.matchall@npm:^4.0.10":
version: 4.0.11
resolution: "string.prototype.matchall@npm:4.0.11"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
call-bind: "npm:^1.0.7"
define-properties: "npm:^1.2.1"
es-abstract: "npm:^1.23.2"
es-errors: "npm:^1.3.0"
es-object-atoms: "npm:^1.0.0"
get-intrinsic: "npm:^1.2.4"
gopd: "npm:^1.0.1"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
has-symbols: "npm:^1.0.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
internal-slot: "npm:^1.0.7"
regexp.prototype.flags: "npm:^1.5.2"
set-function-name: "npm:^2.0.2"
side-channel: "npm:^1.0.6"
checksum: 10c0/915a2562ac9ab5e01b7be6fd8baa0b2b233a0a9aa975fcb2ec13cc26f08fb9a3e85d5abdaa533c99c6fc4c5b65b914eba3d80c4aff9792a4c9fed403f28f7d9d
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"string.prototype.trim@npm:^1.2.9":
version: 1.2.9
resolution: "string.prototype.trim@npm:1.2.9"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
call-bind: "npm:^1.0.7"
define-properties: "npm:^1.2.1"
es-abstract: "npm:^1.23.0"
es-object-atoms: "npm:^1.0.0"
checksum: 10c0/dcef1a0fb61d255778155006b372dff8cc6c4394bc39869117e4241f41a2c52899c0d263ffc7738a1f9e61488c490b05c0427faa15151efad721e1a9fb2663c2
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"string.prototype.trimend@npm:^1.0.8":
version: 1.0.8
resolution: "string.prototype.trimend@npm:1.0.8"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
call-bind: "npm:^1.0.7"
define-properties: "npm:^1.2.1"
es-object-atoms: "npm:^1.0.0"
checksum: 10c0/0a0b54c17c070551b38e756ae271865ac6cc5f60dabf2e7e343cceae7d9b02e1a1120a824e090e79da1b041a74464e8477e2da43e2775c85392be30a6f60963c
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"string.prototype.trimstart@npm:^1.0.8":
version: 1.0.8
resolution: "string.prototype.trimstart@npm:1.0.8"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
call-bind: "npm:^1.0.7"
define-properties: "npm:^1.2.1"
es-object-atoms: "npm:^1.0.0"
checksum: 10c0/d53af1899959e53c83b64a5fd120be93e067da740e7e75acb433849aa640782fb6c7d4cd5b84c954c84413745a3764df135a8afeb22908b86a835290788d8366
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"strip-ansi@npm:^6.0.1":
version: 6.0.1
resolution: "strip-ansi@npm:6.0.1"
dependencies:
ansi-regex: "npm:^5.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/1ae5f212a126fe5b167707f716942490e3933085a5ff6c008ab97ab2f272c8025d3aa218b7bd6ab25729ca20cc81cddb252102f8751e13482a5199e873680952
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"strip-json-comments@npm:^3.1.1":
version: 3.1.1
resolution: "strip-json-comments@npm:3.1.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/9681a6257b925a7fa0f285851c0e613cc934a50661fa7bb41ca9cbbff89686bb4a0ee366e6ecedc4daafd01e83eee0720111ab294366fe7c185e935475ebcecd
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"style-value-types@npm:4.1.4":
version: 4.1.4
resolution: "style-value-types@npm:4.1.4"
dependencies:
hey-listen: "npm:^1.0.8"
tslib: "npm:^2.1.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/96415a82217890e11bf8b9c278a0870fc343508c1e8fd614ef0b17a1a75d387ae0220d53dbe8acf60226cfdb7dd898678b4fa3d90d23d778bd606ccb069cdc7f
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"stylis@npm:4.2.0":
version: 4.2.0
resolution: "stylis@npm:4.2.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/a7128ad5a8ed72652c6eba46bed4f416521bc9745a460ef5741edc725252cebf36ee45e33a8615a7057403c93df0866ab9ee955960792db210bb80abd5ac6543
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"supports-color@npm:^5.3.0":
version: 5.5.0
resolution: "supports-color@npm:5.5.0"
dependencies:
has-flag: "npm:^3.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/6ae5ff319bfbb021f8a86da8ea1f8db52fac8bd4d499492e30ec17095b58af11f0c55f8577390a749b1c4dde691b6a0315dab78f5f54c9b3d83f8fb5905c1c05
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"supports-color@npm:^7.1.0":
version: 7.2.0
resolution: "supports-color@npm:7.2.0"
dependencies:
has-flag: "npm:^4.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/afb4c88521b8b136b5f5f95160c98dee7243dc79d5432db7efc27efb219385bbc7d9427398e43dd6cc730a0f87d5085ce1652af7efbe391327bc0a7d0f7fc124
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"supports-preserve-symlinks-flag@npm:^1.0.0":
version: 1.0.0
resolution: "supports-preserve-symlinks-flag@npm:1.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/6c4032340701a9950865f7ae8ef38578d8d7053f5e10518076e6554a9381fa91bd9c6850193695c141f32b21f979c985db07265a758867bac95de05f7d8aeb39
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"symbol-observable@npm:^4.0.0":
version: 4.0.0
resolution: "symbol-observable@npm:4.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/5e9a3ab08263a6be8cbee76587ad5880dcc62a47002787ed5ebea56b1eb30dc87da6f0183d67e88286806799fbe21c69077fbd677be4be2188e92318d6c6f31d
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"text-table@npm:^0.2.0":
version: 0.2.0
resolution: "text-table@npm:0.2.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/02805740c12851ea5982686810702e2f14369a5f4c5c40a836821e3eefc65ffeec3131ba324692a37608294b0fd8c1e55a2dd571ffed4909822787668ddbee5c
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"tiny-invariant@npm:^1.0.6":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 1.3.3
resolution: "tiny-invariant@npm:1.3.3"
checksum: 10c0/65af4a07324b591a059b35269cd696aba21bef2107f29b9f5894d83cc143159a204b299553435b03874ebb5b94d019afa8b8eff241c8a4cfee95872c2e1c1c4a
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"to-fast-properties@npm:^2.0.0":
version: 2.0.0
resolution: "to-fast-properties@npm:2.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/b214d21dbfb4bce3452b6244b336806ffea9c05297148d32ebb428d5c43ce7545bdfc65a1ceb58c9ef4376a65c0cb2854d645f33961658b3e3b4f84910ddcdd7
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"to-regex-range@npm:^5.0.1":
version: 5.0.1
resolution: "to-regex-range@npm:5.0.1"
dependencies:
is-number: "npm:^7.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/487988b0a19c654ff3e1961b87f471702e708fa8a8dd02a298ef16da7206692e8552a0250e8b3e8759270f62e9d8314616f6da274734d3b558b1fc7b7724e892
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"toggle-selection@npm:^1.0.6":
version: 1.0.6
resolution: "toggle-selection@npm:1.0.6"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/f2cf1f2c70f374fd87b0cdc8007453ba9e981c4305a8bf4eac10a30e62ecdfd28bca7d18f8f15b15a506bf8a7bfb20dbe3539f0fcf2a2c8396c1a78d53e1f179
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"toidentifier@npm:1.0.1":
version: 1.0.1
resolution: "toidentifier@npm:1.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/93937279934bd66cc3270016dd8d0afec14fb7c94a05c72dc57321f8bd1fa97e5bea6d1f7c89e728d077ca31ea125b78320a616a6c6cd0e6b9cb94cb864381c1
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
"ts-api-utils@npm:^1.3.0":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 1.3.0
resolution: "ts-api-utils@npm:1.3.0"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
peerDependencies:
typescript: ">=4.2.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/f54a0ba9ed56ce66baea90a3fa087a484002e807f28a8ccb2d070c75e76bde64bd0f6dce98b3802834156306050871b67eec325cb4e918015a360a3f0868c77c
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"ts-invariant@npm:^0.10.3":
version: 0.10.3
resolution: "ts-invariant@npm:0.10.3"
dependencies:
tslib: "npm:^2.1.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/2fbc178d5903d325ee0b87fad38827eac11888b6e86979b06754fd4bcdcf44c2a99b8bcd5d59d149c0464ede55ae810b02a2aee6835ad10efe4dd0e22efd68c0
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"ts-invariant@npm:^0.4.0":
version: 0.4.4
resolution: "ts-invariant@npm:0.4.4"
dependencies:
tslib: "npm:^1.9.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/73783533764fb453bd71ceeaed238e7b4ccc0e2b12a631bf779d357b2520c71bace2be98a3ef2e96848d44a6d2202e1cad1e6cac74d5a09c3abac58f9225bf8f
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"tslib@npm:^1.0.0, tslib@npm:^1.10.0, tslib@npm:^1.9.3":
version: 1.14.1
resolution: "tslib@npm:1.14.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/69ae09c49eea644bc5ebe1bca4fa4cc2c82b7b3e02f43b84bd891504edf66dbc6b2ec0eef31a957042de2269139e4acff911e6d186a258fb14069cd7f6febce2
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"tslib@npm:^2.0.0, tslib@npm:^2.0.3, tslib@npm:^2.1.0, tslib@npm:^2.3.0":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 2.6.2
resolution: "tslib@npm:2.6.2"
checksum: 10c0/e03a8a4271152c8b26604ed45535954c0a45296e32445b4b87f8a5abdb2421f40b59b4ca437c4346af0f28179780d604094eb64546bee2019d903d01c6c19bdb
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"tweenjs@npm:^1.0.2":
version: 1.0.2
resolution: "tweenjs@npm:1.0.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/34159c2dd69f3b6e6883346427aedb43eb5c4bdab8082e6d8a9b0b11c49ab0e3f656df0849af6f7bb5617469e42851bf07e4a3bac20c734cca53c88a53e98810
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"type-check@npm:^0.4.0, type-check@npm:~0.4.0":
version: 0.4.0
resolution: "type-check@npm:0.4.0"
dependencies:
prelude-ls: "npm:^1.2.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/7b3fd0ed43891e2080bf0c5c504b418fbb3e5c7b9708d3d015037ba2e6323a28152ec163bcb65212741fa5d2022e3075ac3c76440dbd344c9035f818e8ecee58
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"type-fest@npm:^0.20.2":
version: 0.20.2
resolution: "type-fest@npm:0.20.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/dea9df45ea1f0aaa4e2d3bed3f9a0bfe9e5b2592bddb92eb1bf06e50bcf98dbb78189668cd8bc31a0511d3fc25539b4cd5c704497e53e93e2d40ca764b10bfc3
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"type-is@npm:~1.6.18":
version: 1.6.18
resolution: "type-is@npm:1.6.18"
dependencies:
media-typer: "npm:0.3.0"
mime-types: "npm:~2.1.24"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/a23daeb538591b7efbd61ecf06b6feb2501b683ffdc9a19c74ef5baba362b4347e42f1b4ed81f5882a8c96a3bfff7f93ce3ffaf0cbbc879b532b04c97a55db9d
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"typed-array-buffer@npm:^1.0.2":
version: 1.0.2
resolution: "typed-array-buffer@npm:1.0.2"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
call-bind: "npm:^1.0.7"
es-errors: "npm:^1.3.0"
is-typed-array: "npm:^1.1.13"
checksum: 10c0/9e043eb38e1b4df4ddf9dde1aa64919ae8bb909571c1cc4490ba777d55d23a0c74c7d73afcdd29ec98616d91bb3ae0f705fad4421ea147e1daf9528200b562da
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"typed-array-byte-length@npm:^1.0.1":
version: 1.0.1
resolution: "typed-array-byte-length@npm:1.0.1"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
call-bind: "npm:^1.0.7"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
for-each: "npm:^0.3.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
gopd: "npm:^1.0.1"
has-proto: "npm:^1.0.3"
is-typed-array: "npm:^1.1.13"
checksum: 10c0/fcebeffb2436c9f355e91bd19e2368273b88c11d1acc0948a2a306792f1ab672bce4cfe524ab9f51a0505c9d7cd1c98eff4235c4f6bfef6a198f6cfc4ff3d4f3
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"typed-array-byte-offset@npm:^1.0.2":
version: 1.0.2
resolution: "typed-array-byte-offset@npm:1.0.2"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
available-typed-arrays: "npm:^1.0.7"
call-bind: "npm:^1.0.7"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
for-each: "npm:^0.3.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
gopd: "npm:^1.0.1"
has-proto: "npm:^1.0.3"
is-typed-array: "npm:^1.1.13"
checksum: 10c0/d2628bc739732072e39269389a758025f75339de2ed40c4f91357023c5512d237f255b633e3106c461ced41907c1bf9a533c7e8578066b0163690ca8bc61b22f
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"typed-array-length@npm:^1.0.6":
version: 1.0.6
resolution: "typed-array-length@npm:1.0.6"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
call-bind: "npm:^1.0.7"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
for-each: "npm:^0.3.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
gopd: "npm:^1.0.1"
has-proto: "npm:^1.0.3"
is-typed-array: "npm:^1.1.13"
possible-typed-array-names: "npm:^1.0.0"
checksum: 10c0/74253d7dc488eb28b6b2711cf31f5a9dcefc9c41b0681fd1c178ed0a1681b4468581a3626d39cd4df7aee3d3927ab62be06aa9ca74e5baf81827f61641445b77
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"typescript@npm:^5.2.2":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 5.4.5
resolution: "typescript@npm:5.4.5"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
bin:
tsc: bin/tsc
tsserver: bin/tsserver
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/2954022ada340fd3d6a9e2b8e534f65d57c92d5f3989a263754a78aba549f7e6529acc1921913560a4b816c46dce7df4a4d29f9f11a3dc0d4213bb76d043251e
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"typescript@patch:typescript@npm%3A^5.2.2#optional!builtin<compat/typescript>":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 5.4.5
resolution: "typescript@patch:typescript@npm%3A5.4.5#optional!builtin<compat/typescript>::version=5.4.5&hash=5adc0c"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
bin:
tsc: bin/tsc
tsserver: bin/tsserver
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/db2ad2a16ca829f50427eeb1da155e7a45e598eec7b086d8b4e8ba44e5a235f758e606d681c66992230d3fc3b8995865e5fd0b22a2c95486d0b3200f83072ec9
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"unbox-primitive@npm:^1.0.2":
version: 1.0.2
resolution: "unbox-primitive@npm:1.0.2"
dependencies:
call-bind: "npm:^1.0.2"
has-bigints: "npm:^1.0.2"
has-symbols: "npm:^1.0.3"
which-boxed-primitive: "npm:^1.0.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/81ca2e81134167cc8f75fa79fbcc8a94379d6c61de67090986a2273850989dd3bae8440c163121b77434b68263e34787a675cbdcb34bb2f764c6b9c843a11b66
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"unpipe@npm:1.0.0, unpipe@npm:~1.0.0":
version: 1.0.0
resolution: "unpipe@npm:1.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/193400255bd48968e5c5383730344fbb4fa114cdedfab26e329e50dd2d81b134244bb8a72c6ac1b10ab0281a58b363d06405632c9d49ca9dfd5e90cbd7d0f32c
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"uri-js@npm:^4.2.2":
version: 4.4.1
resolution: "uri-js@npm:4.4.1"
dependencies:
punycode: "npm:^2.1.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/4ef57b45aa820d7ac6496e9208559986c665e49447cb072744c13b66925a362d96dd5a46c4530a6b8e203e5db5fe849369444440cb22ecfc26c679359e5dfa3c
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"use-callback-ref@npm:^1.2.3, use-callback-ref@npm:^1.2.5":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 1.3.2
resolution: "use-callback-ref@npm:1.3.2"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
tslib: "npm:^2.0.0"
peerDependencies:
"@types/react": ^16.8.0 || ^17.0.0 || ^18.0.0
react: ^16.8.0 || ^17.0.0 || ^18.0.0
peerDependenciesMeta:
"@types/react":
optional: true
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/d232c37160fe3970c99255da19b5fb5299fb5926a5d6141d928a87feb47732c323d29be2f8137d3b1e5499c70d284cd1d9cfad703cc58179db8be24d7dd8f1f2
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"use-sidecar@npm:^1.0.1, use-sidecar@npm:^1.0.5":
version: 1.1.2
resolution: "use-sidecar@npm:1.1.2"
dependencies:
detect-node-es: "npm:^1.1.0"
tslib: "npm:^2.0.0"
peerDependencies:
"@types/react": ^16.9.0 || ^17.0.0 || ^18.0.0
react: ^16.8.0 || ^17.0.0 || ^18.0.0
peerDependenciesMeta:
"@types/react":
optional: true
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/89f0018fd9aee1fc17c85ac18c4bf8944d460d453d0d0e04ddbc8eaddf3fa591e9c74a1f8a438a1bff368a7a2417fab380bdb3df899d2194c4375b0982736de0
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"utils-merge@npm:1.0.1":
version: 1.0.1
resolution: "utils-merge@npm:1.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/02ba649de1b7ca8854bfe20a82f1dfbdda3fb57a22ab4a8972a63a34553cf7aa51bc9081cf7e001b035b88186d23689d69e71b510e610a09a4c66f68aa95b672
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
"vary@npm:^1, vary@npm:~1.1.2":
version: 1.1.2
resolution: "vary@npm:1.1.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/f15d588d79f3675135ba783c91a4083dcd290a2a5be9fcb6514220a1634e23df116847b1cc51f66bfb0644cf9353b2abb7815ae499bab06e46dd33c1a6bf1f4f
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"warning@npm:^4.0.3":
version: 4.0.3
resolution: "warning@npm:4.0.3"
dependencies:
loose-envify: "npm:^1.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/aebab445129f3e104c271f1637fa38e55eb25f968593e3825bd2f7a12bd58dc3738bb70dc8ec85826621d80b4acfed5a29ebc9da17397c6125864d72301b937e
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Split NeoPass dev server into main/backing servers
2024-03-13 13:00:27 -07:00
"web-streams-polyfill@npm:^3.0.3":
version: 3.3.3
resolution: "web-streams-polyfill@npm:3.3.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/64e855c47f6c8330b5436147db1c75cb7e7474d924166800e8e2aab5eb6c76aac4981a84261dd2982b3e754490900b99791c80ae1407a9fa0dcff74f82ea3a7f
Split NeoPass dev server into main/backing servers
2024-03-13 13:00:27 -07:00
languageName: node
linkType: hard
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"which-boxed-primitive@npm:^1.0.2":
version: 1.0.2
resolution: "which-boxed-primitive@npm:1.0.2"
dependencies:
is-bigint: "npm:^1.0.1"
is-boolean-object: "npm:^1.1.0"
is-number-object: "npm:^1.0.4"
is-string: "npm:^1.0.5"
is-symbol: "npm:^1.0.3"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/0a62a03c00c91dd4fb1035b2f0733c341d805753b027eebd3a304b9cb70e8ce33e25317add2fe9b5fea6f53a175c0633ae701ff812e604410ddd049777cd435e
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"which-builtin-type@npm:^1.1.3":
version: 1.1.3
resolution: "which-builtin-type@npm:1.1.3"
dependencies:
function.prototype.name: "npm:^1.1.5"
has-tostringtag: "npm:^1.0.0"
is-async-function: "npm:^2.0.0"
is-date-object: "npm:^1.0.5"
is-finalizationregistry: "npm:^1.0.2"
is-generator-function: "npm:^1.0.10"
is-regex: "npm:^1.1.4"
is-weakref: "npm:^1.0.2"
isarray: "npm:^2.0.5"
which-boxed-primitive: "npm:^1.0.2"
which-collection: "npm:^1.0.1"
which-typed-array: "npm:^1.1.9"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/2b7b234df3443b52f4fbd2b65b731804de8d30bcc4210ec84107ef377a81923cea7f2763b7fb78b394175cea59118bf3c41b9ffd2d643cb1d748ef93b33b6bd4
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"which-collection@npm:^1.0.1":
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
version: 1.0.2
resolution: "which-collection@npm:1.0.2"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
is-map: "npm:^2.0.3"
is-set: "npm:^2.0.3"
is-weakmap: "npm:^2.0.2"
is-weakset: "npm:^2.0.3"
checksum: 10c0/3345fde20964525a04cdf7c4a96821f85f0cc198f1b2ecb4576e08096746d129eb133571998fe121c77782ac8f21cbd67745a3d35ce100d26d4e684c142ea1f2
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
"which-typed-array@npm:^1.1.14, which-typed-array@npm:^1.1.15, which-typed-array@npm:^1.1.9":
version: 1.1.15
resolution: "which-typed-array@npm:1.1.15"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
dependencies:
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
available-typed-arrays: "npm:^1.0.7"
call-bind: "npm:^1.0.7"
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
for-each: "npm:^0.3.3"
gopd: "npm:^1.0.1"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
has-tostringtag: "npm:^1.0.2"
checksum: 10c0/4465d5348c044032032251be54d8988270e69c6b7154f8fcb2a47ff706fe36f7624b3a24246b8d9089435a8f4ec48c1c1025c5d6b499456b9e5eff4f48212983
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"which@npm:^2.0.1":
version: 2.0.2
resolution: "which@npm:2.0.2"
dependencies:
isexe: "npm:^2.0.0"
bin:
node-which: ./bin/node-which
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/66522872a768b60c2a65a57e8ad184e5372f5b6a9ca6d5f033d4b0dc98aff63995655a7503b9c0a2598936f532120e81dd8cc155e2e92ed662a2b9377cc4374f
languageName: node
linkType: hard
"word-wrap@npm:^1.2.5":
version: 1.2.5
resolution: "word-wrap@npm:1.2.5"
checksum: 10c0/e0e4a1ca27599c92a6ca4c32260e8a92e8a44f4ef6ef93f803f8ed823f486e0889fc0b93be4db59c8d51b3064951d25e43d434e95dc8c960cc3a63d65d00ba20
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"wrappy@npm:1":
version: 1.0.2
resolution: "wrappy@npm:1.0.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/56fece1a4018c6a6c8e28fbc88c87e0fbf4ea8fd64fc6c63b18f4acc4bd13e0ad2515189786dd2c30d3eec9663d70f4ecf699330002f8ccb547e4a18231fc9f0
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"yallist@npm:^4.0.0":
version: 4.0.0
resolution: "yallist@npm:4.0.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/2286b5e8dbfe22204ab66e2ef5cc9bbb1e55dfc873bbe0d568aa943eb255d131890dfd5bf243637273d31119b870f49c18fcde2c6ffbb7a7a092b870dc90625a
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"yaml@npm:^1.10.0":
version: 1.10.2
resolution: "yaml@npm:1.10.2"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/5c28b9eb7adc46544f28d9a8d20c5b3cb1215a886609a2fd41f51628d8aaa5878ccd628b755dbcd29f6bb4921bd04ffbc6dcc370689bb96e594e2f9813d2605f
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"yocto-queue@npm:^0.1.0":
version: 0.1.0
resolution: "yocto-queue@npm:0.1.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/dceb44c28578b31641e13695d200d34ec4ab3966a5729814d5445b194933c096b7ced71494ce53a0e8820685d1d010df8b2422e5bf2cdea7e469d97ffbea306f
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"zen-observable-ts@npm:^0.8.21":
version: 0.8.21
resolution: "zen-observable-ts@npm:0.8.21"
dependencies:
tslib: "npm:^1.9.3"
zen-observable: "npm:^0.8.0"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/fe4a02f862b5f7e8ae0f86230c37b84c7d5611f5c206981afb4043e732d04cf7067a6cbe1ba82d20f18b735a3387937195a12542158a631d308ae3959a1d93c4
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"zen-observable-ts@npm:^1.2.5":
version: 1.2.5
resolution: "zen-observable-ts@npm:1.2.5"
dependencies:
zen-observable: "npm:0.8.15"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/21d586f3d0543e1d6f05d9333a137b407dbf337907c1ee1c2fa7a7da044f7e1262e4baf4ef8902f230c6f5acb561047659eb7df73df33307233cc451efe46db1
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
"zen-observable@npm:0.8.15, zen-observable@npm:^0.8.0":
version: 0.8.15
resolution: "zen-observable@npm:0.8.15"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
checksum: 10c0/71cc2f2bbb537300c3f569e25693d37b3bc91f225cefce251a71c30bc6bb3e7f8e9420ca0eb57f2ac9e492b085b8dfa075fd1e8195c40b83c951dd59c6e4fbf8
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
languageName: node
linkType: hard
Copy permalink