github-mirror/framework
2
0
Fork 0
mirror of https://github.com/flarum/framework.git synced 2024-11-22 12:48:28 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
dk/no-one-permission
framework/yarn.lock

5106 lines
210 KiB
Plaintext
Raw Permalink Normal View History

chore: use yarn v1 in extensions/core
2022-03-12 07:28:26 +08:00
# THIS IS AN AUTOGENERATED FILE. DO NOT EDIT THIS FILE DIRECTLY.
# yarn lockfile v1
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@ampproject/remapping@^2.1.0":
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "2.2.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@ampproject/remapping/-/remapping-2.2.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-qRmjj8nj9qmLTQXXmaR1cck3UXSRMPrbsLJAasZpF+t3riI71BXed5ebIOYwQntykeZuhjsdweEc9BxH5Jc26w==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@jridgewell/gen-mapping" "^0.1.0"
"@jridgewell/trace-mapping" "^0.3.9"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@askvortsov/rich-icu-message-formatter@^0.2.4":
version "0.2.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@askvortsov/rich-icu-message-formatter/-/rich-icu-message-formatter-0.2.4.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-JOdZ7iw7qF3uxC3cfY8dighM3rgrV0WufgwVeFD9VEkxB7IwA7DX2kHs24zk4CYPR6HQXUEnM6fwOy+VKUrc8w==
dependencies:
"@babel/runtime" "^7.11.2"
"@ultraq/array-utils" "^2.1.0"
"@ultraq/icu-message-formatter" "^0.12.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@babel/code-frame@^7.0.0", "@babel/code-frame@^7.12.13", "@babel/code-frame@^7.18.6":
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/code-frame/-/code-frame-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-TDCmlK5eOvH+eH7cdAFlNXeVJqWIQ7gW9tY1GJIpUtFb6CmjVyq2VM3u71bOyR8CRihcCgMUYoDNyLXao3+70Q==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/highlight" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/compat-data@^7.17.7", "@babel/compat-data@^7.20.0", "@babel/compat-data@^7.20.1":
version "7.20.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/compat-data/-/compat-data-7.20.1.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-EWZ4mE2diW3QALKvDMiXnbZpRvlj+nayZ112nK93SnhqOtpdsbVD4W+2tEoT3YNBAG9RBR0ISY758ZkOgsn6pQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@babel/core@^7.0.0", "@babel/core@^7.0.0-0", "@babel/core@^7.11.6", "@babel/core@^7.12.0", "@babel/core@^7.12.3", "@babel/core@^7.13.0", "@babel/core@^7.16.0", "@babel/core@^7.4.0-0", "@babel/core@^7.8.0", "@babel/core@>=7.0.0-beta.0 <8":
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "7.20.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/core/-/core-7.20.2.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-w7DbG8DtMrJcFOi4VrLm+8QM4az8Mo+PuLBKLp2zrYRCow8W/f9xiXm5sN53C8HksCyDQwCKha9JiDoIyPjT2g==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
"@ampproject/remapping" "^2.1.0"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/code-frame" "^7.18.6"
"@babel/generator" "^7.20.2"
"@babel/helper-compilation-targets" "^7.20.0"
"@babel/helper-module-transforms" "^7.20.2"
"@babel/helpers" "^7.20.1"
"@babel/parser" "^7.20.2"
"@babel/template" "^7.18.10"
"@babel/traverse" "^7.20.1"
"@babel/types" "^7.20.2"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
convert-source-map "^1.7.0"
debug "^4.1.0"
gensync "^1.0.0-beta.2"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
json5 "^2.2.1"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
semver "^6.3.0"
feat(jest): mithril component testing (#3679) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * feat(jest): mithril component testing * fix: use separate `tsconfig.test.json` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-11 06:02:50 +08:00
"@babel/generator@^7.20.1", "@babel/generator@^7.20.2", "@babel/generator@^7.7.2":
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "7.20.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/generator/-/generator-7.20.4.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-luCf7yk/cm7yab6CAW1aiFnmEfBJplb/JojV56MYEK7ziWfGmFlTfmL9Ehwfy4gFhbjBfWO1wj7/TuSbVNEEtA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/types" "^7.20.2"
"@jridgewell/gen-mapping" "^0.3.2"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
jsesc "^2.5.1"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-annotate-as-pure@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/helper-annotate-as-pure/-/helper-annotate-as-pure-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-duORpUiYrEpzKIop6iNbjnwKLAKnJ47csTyRACyEmWj0QdUrm5aqNJGHSSEQSUAvNW0ojX0dOmK9dZduvkfeXA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/types" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-builder-binary-assignment-operator-visitor@^7.18.6":
version "7.18.9"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/helper-builder-binary-assignment-operator-visitor/-/helper-builder-binary-assignment-operator-visitor-7.18.9.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-yFQ0YCHoIqarl8BCRwBL8ulYUaZpz3bNsA7oFepAzee+8/+ImtADXNOmO5vJvsPff3qi+hvpkY/NYBTrBQgdNw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-explode-assignable-expression" "^7.18.6"
"@babel/types" "^7.18.9"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-compilation-targets@^7.17.7", "@babel/helper-compilation-targets@^7.18.9", "@babel/helper-compilation-targets@^7.20.0":
version "7.20.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/helper-compilation-targets/-/helper-compilation-targets-7.20.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-0jp//vDGp9e8hZzBc6N/KwA5ZK3Wsm/pfm4CrY7vzegkVxc65SgSn6wYOnwHe9Js9HRQ1YTCKLGPzDtaS3RoLQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/compat-data" "^7.20.0"
"@babel/helper-validator-option" "^7.18.6"
browserslist "^4.21.3"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
semver "^6.3.0"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-create-class-features-plugin@^7.18.6", "@babel/helper-create-class-features-plugin@^7.20.2":
version "7.20.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/helper-create-class-features-plugin/-/helper-create-class-features-plugin-7.20.2.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-k22GoYRAHPYr9I+Gvy2ZQlAe5mGy8BqWst2wRt8cwIufWTxrsVshhIBvYNqC80N0GSFWTsqRVexOtfzlgOEDvA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-annotate-as-pure" "^7.18.6"
"@babel/helper-environment-visitor" "^7.18.9"
"@babel/helper-function-name" "^7.19.0"
"@babel/helper-member-expression-to-functions" "^7.18.9"
"@babel/helper-optimise-call-expression" "^7.18.6"
"@babel/helper-replace-supers" "^7.19.1"
"@babel/helper-split-export-declaration" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-create-regexp-features-plugin@^7.18.6", "@babel/helper-create-regexp-features-plugin@^7.19.0":
version "7.19.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/helper-create-regexp-features-plugin/-/helper-create-regexp-features-plugin-7.19.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-htnV+mHX32DF81amCDrwIDr8nrp1PTm+3wfBN9/v8QJOLEioOCOG7qNyq0nHeFiWbT3Eb7gsPwEmV64UCQ1jzw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-annotate-as-pure" "^7.18.6"
regexpu-core "^5.1.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-define-polyfill-provider@^0.3.3":
version "0.3.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/helper-define-polyfill-provider/-/helper-define-polyfill-provider-0.3.3.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-z5aQKU4IzbqCC1XH0nAqfsFLMVSo22SBKUc0BxGrLkolTdPTructy0ToNnlO2zA4j9Q/7pjMZf0DSY+DSTYzww==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-compilation-targets" "^7.17.7"
"@babel/helper-plugin-utils" "^7.16.7"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
debug "^4.1.1"
lodash.debounce "^4.0.8"
resolve "^1.14.2"
semver "^6.1.2"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-environment-visitor@^7.18.9":
version "7.18.9"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/helper-environment-visitor/-/helper-environment-visitor-7.18.9.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-3r/aACDJ3fhQ/EVgFy0hpj8oHyHpQc+LPtJoY9SzTThAsStm4Ptegq92vqKoE3vD706ZVFWITnMnxucw+S9Ipg==
"@babel/helper-explode-assignable-expression@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/helper-explode-assignable-expression/-/helper-explode-assignable-expression-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-eyAYAsQmB80jNfg4baAtLeWAQHfHFiR483rzFK+BhETlGZaQC9bsfrugfXDCbRHLQbIA7U5NxhhOxN7p/dWIcg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/types" "^7.18.6"
"@babel/helper-function-name@^7.18.9", "@babel/helper-function-name@^7.19.0":
version "7.19.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/helper-function-name/-/helper-function-name-7.19.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-WAwHBINyrpqywkUH0nTnNgI5ina5TFn85HKS0pbPDfxFfhyR/aNQEn4hGi1P1JyT//I0t4OgXUlofzWILRvS5w==
dependencies:
"@babel/template" "^7.18.10"
"@babel/types" "^7.19.0"
"@babel/helper-hoist-variables@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/helper-hoist-variables/-/helper-hoist-variables-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-UlJQPkFqFULIcyW5sbzgbkxn2FKRgwWiRexcuaR8RNJRy8+LLveqPjwZV/bwrLZCN0eUHD/x8D0heK1ozuoo6Q==
dependencies:
"@babel/types" "^7.18.6"
"@babel/helper-member-expression-to-functions@^7.18.9":
version "7.18.9"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/helper-member-expression-to-functions/-/helper-member-expression-to-functions-7.18.9.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-RxifAh2ZoVU67PyKIO4AMi1wTenGfMR/O/ae0CCRqwgBAt5v7xjdtRw7UoSbsreKrQn5t7r89eruK/9JjYHuDg==
dependencies:
"@babel/types" "^7.18.9"
"@babel/helper-module-imports@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/helper-module-imports/-/helper-module-imports-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-0NFvs3VkuSYbFi1x2Vd6tKrywq+z/cLeYC/RJNFrIX/30Bf5aiGYbtvGXolEktzJH8o5E5KJ3tT+nkxuuZFVlA==
dependencies:
"@babel/types" "^7.18.6"
"@babel/helper-module-transforms@^7.18.6", "@babel/helper-module-transforms@^7.19.6", "@babel/helper-module-transforms@^7.20.2":
version "7.20.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/helper-module-transforms/-/helper-module-transforms-7.20.2.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-zvBKyJXRbmK07XhMuujYoJ48B5yvvmM6+wcpv6Ivj4Yg6qO7NOZOSnvZN9CRl1zz1Z4cKf8YejmCMh8clOoOeA==
dependencies:
"@babel/helper-environment-visitor" "^7.18.9"
"@babel/helper-module-imports" "^7.18.6"
"@babel/helper-simple-access" "^7.20.2"
"@babel/helper-split-export-declaration" "^7.18.6"
"@babel/helper-validator-identifier" "^7.19.1"
"@babel/template" "^7.18.10"
"@babel/traverse" "^7.20.1"
"@babel/types" "^7.20.2"
"@babel/helper-optimise-call-expression@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/helper-optimise-call-expression/-/helper-optimise-call-expression-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-HP59oD9/fEHQkdcbgFCnbmgH5vIQTJbxh2yf+CdM89/glUNnuzr87Q8GIjGEnOktTROemO0Pe0iPAYbqZuOUiA==
dependencies:
"@babel/types" "^7.18.6"
"@babel/helper-plugin-utils@^7.0.0", "@babel/helper-plugin-utils@^7.10.4", "@babel/helper-plugin-utils@^7.12.13", "@babel/helper-plugin-utils@^7.14.5", "@babel/helper-plugin-utils@^7.16.7", "@babel/helper-plugin-utils@^7.18.6", "@babel/helper-plugin-utils@^7.18.9", "@babel/helper-plugin-utils@^7.19.0", "@babel/helper-plugin-utils@^7.20.2", "@babel/helper-plugin-utils@^7.8.0", "@babel/helper-plugin-utils@^7.8.3":
version "7.20.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/helper-plugin-utils/-/helper-plugin-utils-7.20.2.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-8RvlJG2mj4huQ4pZ+rU9lqKi9ZKiRmuvGuM2HlWmkmgOhbs6zEAw6IEiJ5cQqGbDzGZOhwuOQNtZMi/ENLjZoQ==
"@babel/helper-remap-async-to-generator@^7.18.6", "@babel/helper-remap-async-to-generator@^7.18.9":
version "7.18.9"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/helper-remap-async-to-generator/-/helper-remap-async-to-generator-7.18.9.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-dI7q50YKd8BAv3VEfgg7PS7yD3Rtbi2J1XMXaalXO0W0164hYLnh8zpjRS0mte9MfVp/tltvr/cfdXPvJr1opA==
dependencies:
"@babel/helper-annotate-as-pure" "^7.18.6"
"@babel/helper-environment-visitor" "^7.18.9"
"@babel/helper-wrap-function" "^7.18.9"
"@babel/types" "^7.18.9"
"@babel/helper-replace-supers@^7.18.6", "@babel/helper-replace-supers@^7.19.1":
version "7.19.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/helper-replace-supers/-/helper-replace-supers-7.19.1.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-T7ahH7wV0Hfs46SFh5Jz3s0B6+o8g3c+7TMxu7xKfmHikg7EAZ3I2Qk9LFhjxXq8sL7UkP5JflezNwoZa8WvWw==
dependencies:
"@babel/helper-environment-visitor" "^7.18.9"
"@babel/helper-member-expression-to-functions" "^7.18.9"
"@babel/helper-optimise-call-expression" "^7.18.6"
"@babel/traverse" "^7.19.1"
"@babel/types" "^7.19.0"
"@babel/helper-simple-access@^7.19.4", "@babel/helper-simple-access@^7.20.2":
version "7.20.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/helper-simple-access/-/helper-simple-access-7.20.2.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-+0woI/WPq59IrqDYbVGfshjT5Dmk/nnbdpcF8SnMhhXObpTq2KNBdLFRFrkVdbDOyUmHBCxzm5FHV1rACIkIbA==
dependencies:
"@babel/types" "^7.20.2"
"@babel/helper-skip-transparent-expression-wrappers@^7.18.9":
version "7.20.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/helper-skip-transparent-expression-wrappers/-/helper-skip-transparent-expression-wrappers-7.20.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-5y1JYeNKfvnT8sZcK9DVRtpTbGiomYIHviSP3OQWmDPU3DeH4a1ZlT/N2lyQ5P8egjcRaT/Y9aNqUxK0WsnIIg==
dependencies:
"@babel/types" "^7.20.0"
"@babel/helper-split-export-declaration@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/helper-split-export-declaration/-/helper-split-export-declaration-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-bde1etTx6ZyTmobl9LLMMQsaizFVZrquTEHOqKeQESMKo4PlObf+8+JA25ZsIpZhT/WEd39+vOdLXAFG/nELpA==
dependencies:
"@babel/types" "^7.18.6"
"@babel/helper-string-parser@^7.19.4":
version "7.19.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/helper-string-parser/-/helper-string-parser-7.19.4.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-nHtDoQcuqFmwYNYPz3Rah5ph2p8PFeFCsZk9A/48dPc/rGocJ5J3hAAZ7pb76VWX3fZKu+uEr/FhH5jLx7umrw==
"@babel/helper-validator-identifier@^7.18.6", "@babel/helper-validator-identifier@^7.19.1":
version "7.19.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/helper-validator-identifier/-/helper-validator-identifier-7.19.1.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-awrNfaMtnHUr653GgGEs++LlAvW6w+DcPrOliSMXWCKo597CwL5Acf/wWdNkf/tfEQE3mjkeD1YOVZOUV/od1w==
"@babel/helper-validator-option@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/helper-validator-option/-/helper-validator-option-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-XO7gESt5ouv/LRJdrVjkShckw6STTaB7l9BrpBaAHDeF5YZT+01PCwmR0SJHnkW6i8OwW/EVWRShfi4j2x+KQw==
"@babel/helper-wrap-function@^7.18.9":
version "7.19.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/helper-wrap-function/-/helper-wrap-function-7.19.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-txX8aN8CZyYGTwcLhlk87KRqncAzhh5TpQamZUa0/u3an36NtDpUP6bQgBCBcLeBs09R/OwQu3OjK0k/HwfNDg==
dependencies:
"@babel/helper-function-name" "^7.19.0"
"@babel/template" "^7.18.10"
"@babel/traverse" "^7.19.0"
"@babel/types" "^7.19.0"
"@babel/helpers@^7.20.1":
version "7.20.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/helpers/-/helpers-7.20.1.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-J77mUVaDTUJFZ5BpP6mMn6OIl3rEWymk2ZxDBQJUG3P+PbmyMcF3bYWvz0ma69Af1oobDqT/iAsvzhB58xhQUg==
dependencies:
"@babel/template" "^7.18.10"
"@babel/traverse" "^7.20.1"
"@babel/types" "^7.20.0"
"@babel/highlight@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/highlight/-/highlight-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-u7stbOuYjaPezCuLj29hNW1v64M2Md2qupEKP1fHc7WdOA3DgLh37suiSrZYY7haUB7iBeQZ9P1uiRF359do3g==
dependencies:
"@babel/helper-validator-identifier" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chalk "^2.0.0"
js-tokens "^4.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@babel/parser@^7.1.0", "@babel/parser@^7.14.7", "@babel/parser@^7.18.10", "@babel/parser@^7.20.1", "@babel/parser@^7.20.2", "@babel/parser@^7.20.7":
version "7.21.3"
resolved "https://registry.npmjs.org/@babel/parser/-/parser-7.21.3.tgz"
integrity sha512-lobG0d7aOfQRXh8AyklEAgZGvA4FShxo6xQbUrrT/cNBPUdIDojlokwJsQyCC/eKia7ifqM0yP+2DRZ4WKw2RQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-bugfix-safari-id-destructuring-collision-in-function-expression@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-bugfix-safari-id-destructuring-collision-in-function-expression/-/plugin-bugfix-safari-id-destructuring-collision-in-function-expression-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-Dgxsyg54Fx1d4Nge8UnvTrED63vrwOdPmyvPzlNN/boaliRP54pm3pGzZD1SJUwrBA+Cs/xdG8kXX6Mn/RfISQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining@^7.18.9":
version "7.18.9"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining/-/plugin-bugfix-v8-spread-parameters-in-optional-chaining-7.18.9.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-AHrP9jadvH7qlOj6PINbgSuphjQUAK7AOT7DPjBo9EHoLhQTnnK5u45e1Hd4DbSQEO9nqPWtQ89r+XEOWFScKg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.9"
"@babel/helper-skip-transparent-expression-wrappers" "^7.18.9"
"@babel/plugin-proposal-optional-chaining" "^7.18.9"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-proposal-async-generator-functions@^7.20.1":
version "7.20.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-proposal-async-generator-functions/-/plugin-proposal-async-generator-functions-7.20.1.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-Gh5rchzSwE4kC+o/6T8waD0WHEQIsDmjltY8WnWRXHUdH8axZhuH86Ov9M72YhJfDrZseQwuuWaaIT/TmePp3g==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-environment-visitor" "^7.18.9"
"@babel/helper-plugin-utils" "^7.19.0"
"@babel/helper-remap-async-to-generator" "^7.18.9"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@babel/plugin-syntax-async-generators" "^7.8.4"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-proposal-class-properties@^7.16.0", "@babel/plugin-proposal-class-properties@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-proposal-class-properties/-/plugin-proposal-class-properties-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-cumfXOF0+nzZrrN8Rf0t7M+tF6sZc7vhQwYQck9q1/5w2OExlD+b4v4RpMJFaV1Z7WcDRgO6FqvxqxGlwo+RHQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-create-class-features-plugin" "^7.18.6"
"@babel/helper-plugin-utils" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-proposal-class-static-block@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-proposal-class-static-block/-/plugin-proposal-class-static-block-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-+I3oIiNxrCpup3Gi8n5IGMwj0gOCAjcJUSQEcotNnCCPMEnixawOQ+KeJPlgfjzx+FKQ1QSyZOWe7wmoJp7vhw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-create-class-features-plugin" "^7.18.6"
"@babel/helper-plugin-utils" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@babel/plugin-syntax-class-static-block" "^7.14.5"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-proposal-dynamic-import@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-proposal-dynamic-import/-/plugin-proposal-dynamic-import-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-1auuwmK+Rz13SJj36R+jqFPMJWyKEDd7lLSdOj4oJK0UTgGueSAtkrCvz9ewmgyU/P941Rv2fQwZJN8s6QruXw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@babel/plugin-syntax-dynamic-import" "^7.8.3"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-proposal-export-namespace-from@^7.18.9":
version "7.18.9"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-proposal-export-namespace-from/-/plugin-proposal-export-namespace-from-7.18.9.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-k1NtHyOMvlDDFeb9G5PhUXuGj8m/wiwojgQVEhJ/fsVsMCpLyOP4h0uGEjYJKrRI+EVPlb5Jk+Gt9P97lOGwtA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.9"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@babel/plugin-syntax-export-namespace-from" "^7.8.3"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-proposal-json-strings@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-proposal-json-strings/-/plugin-proposal-json-strings-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-lr1peyn9kOdbYc0xr0OdHTZ5FMqS6Di+H0Fz2I/JwMzGmzJETNeOFq2pBySw6X/KFL5EWDjlJuMsUGRFb8fQgQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@babel/plugin-syntax-json-strings" "^7.8.3"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-proposal-logical-assignment-operators@^7.18.9":
version "7.18.9"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-proposal-logical-assignment-operators/-/plugin-proposal-logical-assignment-operators-7.18.9.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-128YbMpjCrP35IOExw2Fq+x55LMP42DzhOhX2aNNIdI9avSWl2PI0yuBWarr3RYpZBSPtabfadkH2yeRiMD61Q==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.9"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@babel/plugin-syntax-logical-assignment-operators" "^7.10.4"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-proposal-nullish-coalescing-operator@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-proposal-nullish-coalescing-operator/-/plugin-proposal-nullish-coalescing-operator-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-wQxQzxYeJqHcfppzBDnm1yAY0jSRkUXR2z8RePZYrKwMKgMlE8+Z6LUno+bd6LvbGh8Gltvy74+9pIYkr+XkKA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@babel/plugin-syntax-nullish-coalescing-operator" "^7.8.3"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-proposal-numeric-separator@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-proposal-numeric-separator/-/plugin-proposal-numeric-separator-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-ozlZFogPqoLm8WBr5Z8UckIoE4YQ5KESVcNudyXOR8uqIkliTEgJ3RoketfG6pmzLdeZF0H/wjE9/cCEitBl7Q==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@babel/plugin-syntax-numeric-separator" "^7.10.4"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-proposal-object-rest-spread@^7.20.2":
version "7.20.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-proposal-object-rest-spread/-/plugin-proposal-object-rest-spread-7.20.2.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-Ks6uej9WFK+fvIMesSqbAto5dD8Dz4VuuFvGJFKgIGSkJuRGcrwGECPA1fDgQK3/DbExBJpEkTeYeB8geIFCSQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/compat-data" "^7.20.1"
"@babel/helper-compilation-targets" "^7.20.0"
"@babel/helper-plugin-utils" "^7.20.2"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@babel/plugin-syntax-object-rest-spread" "^7.8.3"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-parameters" "^7.20.1"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-proposal-optional-catch-binding@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-proposal-optional-catch-binding/-/plugin-proposal-optional-catch-binding-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-Q40HEhs9DJQyaZfUjjn6vE8Cv4GmMHCYuMGIWUnlxH6400VGxOuwWsPt4FxXxJkC/5eOzgn0z21M9gMT4MOhbw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@babel/plugin-syntax-optional-catch-binding" "^7.8.3"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-proposal-optional-chaining@^7.18.9":
version "7.18.9"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-proposal-optional-chaining/-/plugin-proposal-optional-chaining-7.18.9.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-v5nwt4IqBXihxGsW2QmCWMDS3B3bzGIk/EQVZz2ei7f3NJl8NzAJVvUmpDW5q1CRNY+Beb/k58UAH1Km1N411w==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.9"
"@babel/helper-skip-transparent-expression-wrappers" "^7.18.9"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@babel/plugin-syntax-optional-chaining" "^7.8.3"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-proposal-private-methods@^7.16.0", "@babel/plugin-proposal-private-methods@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-proposal-private-methods/-/plugin-proposal-private-methods-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-nutsvktDItsNn4rpGItSNV2sz1XwS+nfU0Rg8aCx3W3NOKVzdMjJRu0O5OkgDp3ZGICSTbgRpxZoWsxoKRvbeA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-create-class-features-plugin" "^7.18.6"
"@babel/helper-plugin-utils" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-proposal-private-property-in-object@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-proposal-private-property-in-object/-/plugin-proposal-private-property-in-object-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-9Rysx7FOctvT5ouj5JODjAFAkgGoudQuLPamZb0v1TGLpapdNaftzifU8NTWQm0IRjqoYypdrSmyWgkocDQ8Dw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-annotate-as-pure" "^7.18.6"
"@babel/helper-create-class-features-plugin" "^7.18.6"
"@babel/helper-plugin-utils" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@babel/plugin-syntax-private-property-in-object" "^7.14.5"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-proposal-unicode-property-regex@^7.18.6", "@babel/plugin-proposal-unicode-property-regex@^7.4.4":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-proposal-unicode-property-regex/-/plugin-proposal-unicode-property-regex-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-2BShG/d5yoZyXZfVePH91urL5wTG6ASZU9M4o03lKK8u8UW1y08OMttBSOADTcJrnPMpvDXRG3G8fyLh4ovs8w==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-create-regexp-features-plugin" "^7.18.6"
"@babel/helper-plugin-utils" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@babel/plugin-syntax-async-generators@^7.8.4":
version "7.8.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-syntax-async-generators/-/plugin-syntax-async-generators-7.8.4.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-tycmZxkGfZaxhMRbXlPXuVFpdWlXpir2W4AMhSJgRKzk/eDlIXOhb2LHWoLpDF7TEHylV5zNhykX6KAgHJmTNw==
dependencies:
"@babel/helper-plugin-utils" "^7.8.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@babel/plugin-syntax-bigint@^7.8.3":
version "7.8.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-syntax-bigint/-/plugin-syntax-bigint-7.8.3.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-wnTnFlG+YxQm3vDxpGE57Pj0srRU4sHE/mDkt1qv2YJJSeUAec2ma4WLUnUPeKjyrfntVwe/N6dCXpU+zL3Npg==
dependencies:
"@babel/helper-plugin-utils" "^7.8.0"
"@babel/plugin-syntax-class-properties@^7.12.13", "@babel/plugin-syntax-class-properties@^7.8.3":
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "7.12.13"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-syntax-class-properties/-/plugin-syntax-class-properties-7.12.13.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-fm4idjKla0YahUNgFNLCB0qySdsoPiZP3iQE3rky0mBUtMZ23yDJ9SJdg6dXTSDnulOVqiF3Hgr9nbXvXTQZYA==
dependencies:
"@babel/helper-plugin-utils" "^7.12.13"
"@babel/plugin-syntax-class-static-block@^7.14.5":
version "7.14.5"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-syntax-class-static-block/-/plugin-syntax-class-static-block-7.14.5.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-b+YyPmr6ldyNnM6sqYeMWE+bgJcJpO6yS4QD7ymxgH34GBPNDM/THBh8iunyvKIZztiwLH4CJZ0RxTk9emgpjw==
dependencies:
"@babel/helper-plugin-utils" "^7.14.5"
"@babel/plugin-syntax-dynamic-import@^7.8.3":
version "7.8.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-syntax-dynamic-import/-/plugin-syntax-dynamic-import-7.8.3.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-5gdGbFon+PszYzqs83S3E5mpi7/y/8M9eC90MRTZfduQOYW76ig6SOSPNe41IG5LoP3FGBn2N0RjVDSQiS94kQ==
dependencies:
"@babel/helper-plugin-utils" "^7.8.0"
"@babel/plugin-syntax-export-namespace-from@^7.8.3":
version "7.8.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-syntax-export-namespace-from/-/plugin-syntax-export-namespace-from-7.8.3.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-MXf5laXo6c1IbEbegDmzGPwGNTsHZmEy6QGznu5Sh2UCWvueywb2ee+CCE4zQiZstxU9BMoQO9i6zUFSY0Kj0Q==
dependencies:
"@babel/helper-plugin-utils" "^7.8.3"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-syntax-import-assertions@^7.20.0":
version "7.20.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-syntax-import-assertions/-/plugin-syntax-import-assertions-7.20.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-IUh1vakzNoWalR8ch/areW7qFopR2AEw03JlG7BbrDqmQ4X3q9uuipQwSGrUn7oGiemKjtSLDhNtQHzMHr1JdQ==
dependencies:
"@babel/helper-plugin-utils" "^7.19.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@babel/plugin-syntax-import-meta@^7.8.3":
version "7.10.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-syntax-import-meta/-/plugin-syntax-import-meta-7.10.4.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-Yqfm+XDx0+Prh3VSeEQCPU81yC+JWZ2pDPFSS4ZdpfZhp4MkFMaDC1UqseovEKwSUpnIL7+vK+Clp7bfh0iD7g==
dependencies:
"@babel/helper-plugin-utils" "^7.10.4"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@babel/plugin-syntax-json-strings@^7.8.3":
version "7.8.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-syntax-json-strings/-/plugin-syntax-json-strings-7.8.3.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-lY6kdGpWHvjoe2vk4WrAapEuBR69EMxZl+RoGRhrFGNYVK8mOPAW8VfbT/ZgrFbXlDNiiaxQnAtgVCZ6jv30EA==
dependencies:
"@babel/helper-plugin-utils" "^7.8.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@babel/plugin-syntax-jsx@^7.18.6", "@babel/plugin-syntax-jsx@^7.7.2":
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-syntax-jsx/-/plugin-syntax-jsx-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-6mmljtAedFGTWu2p/8WIORGwy+61PLgOMPOdazc7YoJ9ZCWUyFy3A6CpPkRKLKD1ToAesxX8KGEViAiLo9N+7Q==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@babel/plugin-syntax-logical-assignment-operators@^7.10.4", "@babel/plugin-syntax-logical-assignment-operators@^7.8.3":
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "7.10.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-syntax-logical-assignment-operators/-/plugin-syntax-logical-assignment-operators-7.10.4.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-d8waShlpFDinQ5MtvGU9xDAOzKH47+FFoney2baFIoMr952hKOLp1HR7VszoZvOsV/4+RRszNY7D17ba0te0ig==
dependencies:
"@babel/helper-plugin-utils" "^7.10.4"
"@babel/plugin-syntax-nullish-coalescing-operator@^7.8.3":
version "7.8.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-syntax-nullish-coalescing-operator/-/plugin-syntax-nullish-coalescing-operator-7.8.3.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-aSff4zPII1u2QD7y+F8oDsz19ew4IGEJg9SVW+bqwpwtfFleiQDMdzA/R+UlWDzfnHFCxxleFT0PMIrR36XLNQ==
dependencies:
"@babel/helper-plugin-utils" "^7.8.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@babel/plugin-syntax-numeric-separator@^7.10.4", "@babel/plugin-syntax-numeric-separator@^7.8.3":
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "7.10.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-syntax-numeric-separator/-/plugin-syntax-numeric-separator-7.10.4.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-9H6YdfkcK/uOnY/K7/aA2xpzaAgkQn37yzWUMRK7OaPOqOpGS1+n0H5hxT9AUw9EsSjPW8SVyMJwYRtWs3X3ug==
dependencies:
"@babel/helper-plugin-utils" "^7.10.4"
"@babel/plugin-syntax-object-rest-spread@^7.8.3":
version "7.8.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-syntax-object-rest-spread/-/plugin-syntax-object-rest-spread-7.8.3.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-XoqMijGZb9y3y2XskN+P1wUGiVwWZ5JmoDRwx5+3GmEplNyVM2s2Dg8ILFQm8rWM48orGy5YpI5Bl8U1y7ydlA==
dependencies:
"@babel/helper-plugin-utils" "^7.8.0"
"@babel/plugin-syntax-optional-catch-binding@^7.8.3":
version "7.8.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-syntax-optional-catch-binding/-/plugin-syntax-optional-catch-binding-7.8.3.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-6VPD0Pc1lpTqw0aKoeRTMiB+kWhAoT24PA+ksWSBrFtl5SIRVpZlwN3NNPQjehA2E/91FV3RjLWoVTglWcSV3Q==
dependencies:
"@babel/helper-plugin-utils" "^7.8.0"
"@babel/plugin-syntax-optional-chaining@^7.8.3":
version "7.8.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-syntax-optional-chaining/-/plugin-syntax-optional-chaining-7.8.3.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-KoK9ErH1MBlCPxV0VANkXW2/dw4vlbGDrFgz8bmUsBGYkFRcbRwMh6cIJubdPrkxRwuGdtCk0v/wPTKbQgBjkg==
dependencies:
"@babel/helper-plugin-utils" "^7.8.0"
"@babel/plugin-syntax-private-property-in-object@^7.14.5":
version "7.14.5"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-syntax-private-property-in-object/-/plugin-syntax-private-property-in-object-7.14.5.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-0wVnp9dxJ72ZUJDV27ZfbSj6iHLoytYZmh3rFcxNnvsJF3ktkzLDZPy/mA17HGsaQT3/DQsWYX1f1QGWkCoVUg==
dependencies:
"@babel/helper-plugin-utils" "^7.14.5"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@babel/plugin-syntax-top-level-await@^7.14.5", "@babel/plugin-syntax-top-level-await@^7.8.3":
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "7.14.5"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-syntax-top-level-await/-/plugin-syntax-top-level-await-7.14.5.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-hx++upLv5U1rgYfwe1xBQUhRmU41NEvpUvrp8jkrSCdvGSnM5/qdRMtylJ6PG5OFkBaHkbTAKTnd3/YyESRHFw==
dependencies:
"@babel/helper-plugin-utils" "^7.14.5"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@babel/plugin-syntax-typescript@^7.20.0", "@babel/plugin-syntax-typescript@^7.7.2":
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "7.20.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-syntax-typescript/-/plugin-syntax-typescript-7.20.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-rd9TkG+u1CExzS4SM1BlMEhMXwFLKVjOAFFCDx9PbX5ycJWDoWMcwdJH9RhkPu1dOgn5TrxLot/Gx6lWFuAUNQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.19.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-arrow-functions@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-arrow-functions/-/plugin-transform-arrow-functions-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-9S9X9RUefzrsHZmKMbDXxweEH+YlE8JJEuat9FdvW9Qh1cw7W64jELCtWNkPBPX5En45uy28KGvA/AySqUh8CQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-async-to-generator@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-async-to-generator/-/plugin-transform-async-to-generator-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-ARE5wZLKnTgPW7/1ftQmSi1CmkqqHo2DNmtztFhvgtOWSDfq0Cq9/9L+KnZNYSNrydBekhW3rwShduf59RoXag==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-module-imports" "^7.18.6"
"@babel/helper-plugin-utils" "^7.18.6"
"@babel/helper-remap-async-to-generator" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-block-scoped-functions@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-block-scoped-functions/-/plugin-transform-block-scoped-functions-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-ExUcOqpPWnliRcPqves5HJcJOvHvIIWfuS4sroBUenPuMdmW+SMHDakmtS7qOo13sVppmUijqeTv7qqGsvURpQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-block-scoping@^7.20.2":
version "7.20.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-block-scoping/-/plugin-transform-block-scoping-7.20.2.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-y5V15+04ry69OV2wULmwhEA6jwSWXO1TwAtIwiPXcvHcoOQUqpyMVd2bDsQJMW8AurjulIyUV8kDqtjSwHy1uQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.20.2"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-classes@^7.20.2":
version "7.20.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-classes/-/plugin-transform-classes-7.20.2.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-9rbPp0lCVVoagvtEyQKSo5L8oo0nQS/iif+lwlAz29MccX2642vWDlSZK+2T2buxbopotId2ld7zZAzRfz9j1g==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-annotate-as-pure" "^7.18.6"
"@babel/helper-compilation-targets" "^7.20.0"
"@babel/helper-environment-visitor" "^7.18.9"
"@babel/helper-function-name" "^7.19.0"
"@babel/helper-optimise-call-expression" "^7.18.6"
"@babel/helper-plugin-utils" "^7.20.2"
"@babel/helper-replace-supers" "^7.19.1"
"@babel/helper-split-export-declaration" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
globals "^11.1.0"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-computed-properties@^7.18.9":
version "7.18.9"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-computed-properties/-/plugin-transform-computed-properties-7.18.9.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-+i0ZU1bCDymKakLxn5srGHrsAPRELC2WIbzwjLhHW9SIE1cPYkLCL0NlnXMZaM1vhfgA2+M7hySk42VBvrkBRw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.9"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-destructuring@^7.20.2":
version "7.20.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-destructuring/-/plugin-transform-destructuring-7.20.2.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-mENM+ZHrvEgxLTBXUiQ621rRXZes3KWUv6NdQlrnr1TkWVw+hUjQBZuP2X32qKlrlG2BzgR95gkuCRSkJl8vIw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.20.2"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-dotall-regex@^7.18.6", "@babel/plugin-transform-dotall-regex@^7.4.4":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-dotall-regex/-/plugin-transform-dotall-regex-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-6S3jpun1eEbAxq7TdjLotAsl4WpQI9DxfkycRcKrjhQYzU87qpXdknpBg/e+TdcMehqGnLFi7tnFUBR02Vq6wg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-create-regexp-features-plugin" "^7.18.6"
"@babel/helper-plugin-utils" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-duplicate-keys@^7.18.9":
version "7.18.9"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-duplicate-keys/-/plugin-transform-duplicate-keys-7.18.9.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-d2bmXCtZXYc59/0SanQKbiWINadaJXqtvIQIzd4+hNwkWBgyCd5F/2t1kXoUdvPMrxzPvhK6EMQRROxsue+mfw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.9"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-exponentiation-operator@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-exponentiation-operator/-/plugin-transform-exponentiation-operator-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-wzEtc0+2c88FVR34aQmiz56dxEkxr2g8DQb/KfaFa1JYXOFVsbhvAonFN6PwVWj++fKmku8NP80plJ5Et4wqHw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-builder-binary-assignment-operator-visitor" "^7.18.6"
"@babel/helper-plugin-utils" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-for-of@^7.18.8":
version "7.18.8"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-for-of/-/plugin-transform-for-of-7.18.8.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-yEfTRnjuskWYo0k1mHUqrVWaZwrdq8AYbfrpqULOJOaucGSp4mNMVps+YtA8byoevxS/urwU75vyhQIxcCgiBQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-function-name@^7.18.9":
version "7.18.9"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-function-name/-/plugin-transform-function-name-7.18.9.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-WvIBoRPaJQ5yVHzcnJFor7oS5Ls0PYixlTYE63lCj2RtdQEl15M68FXQlxnG6wdraJIXRdR7KI+hQ7q/9QjrCQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-compilation-targets" "^7.18.9"
"@babel/helper-function-name" "^7.18.9"
"@babel/helper-plugin-utils" "^7.18.9"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-literals@^7.18.9":
version "7.18.9"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-literals/-/plugin-transform-literals-7.18.9.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-IFQDSRoTPnrAIrI5zoZv73IFeZu2dhu6irxQjY9rNjTT53VmKg9fenjvoiOWOkJ6mm4jKVPtdMzBY98Fp4Z4cg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.9"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-member-expression-literals@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-member-expression-literals/-/plugin-transform-member-expression-literals-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-qSF1ihLGO3q+/g48k85tUjD033C29TNTVB2paCwZPVmOsjn9pClvYYrM2VeJpBY2bcNkuny0YUyTNRyRxJ54KA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-modules-amd@^7.19.6":
version "7.19.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-modules-amd/-/plugin-transform-modules-amd-7.19.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-uG3od2mXvAtIFQIh0xrpLH6r5fpSQN04gIVovl+ODLdUMANokxQLZnPBHcjmv3GxRjnqwLuHvppjjcelqUFZvg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-module-transforms" "^7.19.6"
"@babel/helper-plugin-utils" "^7.19.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-modules-commonjs@^7.19.6":
version "7.19.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-modules-commonjs/-/plugin-transform-modules-commonjs-7.19.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-8PIa1ym4XRTKuSsOUXqDG0YaOlEuTVvHMe5JCfgBMOtHvJKw/4NGovEGN33viISshG/rZNVrACiBmPQLvWN8xQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-module-transforms" "^7.19.6"
"@babel/helper-plugin-utils" "^7.19.0"
"@babel/helper-simple-access" "^7.19.4"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-modules-systemjs@^7.19.6":
version "7.19.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-modules-systemjs/-/plugin-transform-modules-systemjs-7.19.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-fqGLBepcc3kErfR9R3DnVpURmckXP7gj7bAlrTQyBxrigFqszZCkFkcoxzCp2v32XmwXLvbw+8Yq9/b+QqksjQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-hoist-variables" "^7.18.6"
"@babel/helper-module-transforms" "^7.19.6"
"@babel/helper-plugin-utils" "^7.19.0"
"@babel/helper-validator-identifier" "^7.19.1"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-modules-umd@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-modules-umd/-/plugin-transform-modules-umd-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-dcegErExVeXcRqNtkRU/z8WlBLnvD4MRnHgNs3MytRO1Mn1sHRyhbcpYbVMGclAqOjdW+9cfkdZno9dFdfKLfQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-module-transforms" "^7.18.6"
"@babel/helper-plugin-utils" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-named-capturing-groups-regex@^7.19.1":
version "7.19.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-named-capturing-groups-regex/-/plugin-transform-named-capturing-groups-regex-7.19.1.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-oWk9l9WItWBQYS4FgXD4Uyy5kq898lvkXpXQxoJEY1RnvPk4R/Dvu2ebXU9q8lP+rlMwUQTFf2Ok6d78ODa0kw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-create-regexp-features-plugin" "^7.19.0"
"@babel/helper-plugin-utils" "^7.19.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-new-target@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-new-target/-/plugin-transform-new-target-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-DjwFA/9Iu3Z+vrAn+8pBUGcjhxKguSMlsFqeCKbhb9BAV756v0krzVK04CRDi/4aqmk8BsHb4a/gFcaA5joXRw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
fix: Assorted Typing Fixes (#3348) With all the commits below, we resolve all outstanding typing issues in the repo, and CI jobs run green. * fix: Convert DashboardPage and DashboardWidget to TypeScript * fix: fix type errors in package manager ext * fix: Convert Post component to TypeScript * fix: avatar typings should accept null user * fix: convert Notification component to TypeScript * fix: properly use `typeof` in ForumApplication * feat: make Notification content attr generic * chore: format Notification component * fix: Convert DiscussionRenamedNotification to TypeScript * fix(pusher) move shims to a location where they get applied * fix(pusher): fix some typing errors * fix(akismet): fix some typing issues * chore: update core dist typings * chore(pusher): format * fix: anchorScroll should accept string selectors * fix: more accurately represent ApiQueryParamsPlural * fix: convert PostStreamState to TypeScript * chore(core): rebuild typings * feat: allow extending app.routes * fix: more flexible typings for highlight.ts * fix: use primitive `number` type for Discussion typings * fix: convert DiscussionListItem to TypeScript * chore: rebuild core typings * fix: final pusher type fixes * feat: start tags TypeScript conversion * fix: require-dev tags in pusher for CI TypeScript purposes. * chore(core): format * chore(tags): build dist typings * feat(pusher): use dist types from tags. * feat: convert flags to TypeScript * chore(flags): generate dist typings * fix(akismet): last type errors * chore: update .yarn-integrity * chore: partially run flarum-cli audit infra --fix The tsconfig changes from that command are ignored, since we don't yet support "replacable sections" that would let us add custom config. * chore: use type imports * fix: broader gitattributes * chore: run flarum-cli audit infra --monorepo --fix * feat: make `app.data` typings extensible * chore(core): format * chore: boost tags TypeScript coverage * fix(tags): further increase type coverage.
2022-03-23 23:43:14 +08:00
"@babel/plugin-transform-object-assign@^7.16.0":
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-object-assign/-/plugin-transform-object-assign-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-mQisZ3JfqWh2gVXvfqYCAAyRs6+7oev+myBsTwW5RnPhYXOTuCEw2oe3YgxlXMViXUS53lG8koulI7mJ+8JE+A==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-object-super@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-object-super/-/plugin-transform-object-super-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-uvGz6zk+pZoS1aTZrOvrbj6Pp/kK2mp45t2B+bTDre2UgsZZ8EZLSJtUg7m/no0zOJUWgFONpB7Zv9W2tSaFlA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.6"
"@babel/helper-replace-supers" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-parameters@^7.20.1":
version "7.20.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-parameters/-/plugin-transform-parameters-7.20.3.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-oZg/Fpx0YDrj13KsLyO8I/CX3Zdw7z0O9qOd95SqcoIzuqy/WTGWvePeHAnZCN54SfdyjHcb1S30gc8zlzlHcA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.20.2"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-property-literals@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-property-literals/-/plugin-transform-property-literals-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-cYcs6qlgafTud3PAzrrRNbQtfpQ8+y/+M5tKmksS9+M1ckbH6kzY8MrexEM9mcA6JDsukE19iIRvAyYl463sMg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-react-display-name@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-react-display-name/-/plugin-transform-react-display-name-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-TV4sQ+T013n61uMoygyMRm+xf04Bd5oqFpv2jAEQwSZ8NwQA7zeRPg1LMVg2PWi3zWBz+CLKD+v5bcpZ/BS0aA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-react-jsx-development@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-react-jsx-development/-/plugin-transform-react-jsx-development-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-SA6HEjwYFKF7WDjWcMcMGUimmw/nhNRDWxr+KaLSCrkD/LMDBvWRmHAYgE1HDeF8KUuI8OAu+RT6EOtKxSW2qA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-react-jsx" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-react-jsx@^7.16.0", "@babel/plugin-transform-react-jsx@^7.18.6":
version "7.19.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-react-jsx/-/plugin-transform-react-jsx-7.19.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-UVEvX3tXie3Szm3emi1+G63jyw1w5IcMY0FSKM+CRnKRI5Mr1YbCNgsSTwoTwKphQEG9P+QqmuRFneJPZuHNhg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-annotate-as-pure" "^7.18.6"
"@babel/helper-module-imports" "^7.18.6"
"@babel/helper-plugin-utils" "^7.19.0"
"@babel/plugin-syntax-jsx" "^7.18.6"
"@babel/types" "^7.19.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-react-pure-annotations@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-react-pure-annotations/-/plugin-transform-react-pure-annotations-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-I8VfEPg9r2TRDdvnHgPepTKvuRomzA8+u+nhY7qSI1fR2hRNebasZEETLyM5mAUr0Ku56OkXJ0I7NHJnO6cJiQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-annotate-as-pure" "^7.18.6"
"@babel/helper-plugin-utils" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-regenerator@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-regenerator/-/plugin-transform-regenerator-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-poqRI2+qiSdeldcz4wTSTXBRryoq3Gc70ye7m7UD5Ww0nE29IXqMl6r7Nd15WBgRd74vloEMlShtH6CKxVzfmQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.6"
regenerator-transform "^0.15.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-reserved-words@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-reserved-words/-/plugin-transform-reserved-words-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-oX/4MyMoypzHjFrT1CdivfKZ+XvIPMFXwwxHp/r0Ddy2Vuomt4HDFGmft1TAY2yiTKiNSsh3kjBAzcM8kSdsjA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
fix: Assorted Typing Fixes (#3348) With all the commits below, we resolve all outstanding typing issues in the repo, and CI jobs run green. * fix: Convert DashboardPage and DashboardWidget to TypeScript * fix: fix type errors in package manager ext * fix: Convert Post component to TypeScript * fix: avatar typings should accept null user * fix: convert Notification component to TypeScript * fix: properly use `typeof` in ForumApplication * feat: make Notification content attr generic * chore: format Notification component * fix: Convert DiscussionRenamedNotification to TypeScript * fix(pusher) move shims to a location where they get applied * fix(pusher): fix some typing errors * fix(akismet): fix some typing issues * chore: update core dist typings * chore(pusher): format * fix: anchorScroll should accept string selectors * fix: more accurately represent ApiQueryParamsPlural * fix: convert PostStreamState to TypeScript * chore(core): rebuild typings * feat: allow extending app.routes * fix: more flexible typings for highlight.ts * fix: use primitive `number` type for Discussion typings * fix: convert DiscussionListItem to TypeScript * chore: rebuild core typings * fix: final pusher type fixes * feat: start tags TypeScript conversion * fix: require-dev tags in pusher for CI TypeScript purposes. * chore(core): format * chore(tags): build dist typings * feat(pusher): use dist types from tags. * feat: convert flags to TypeScript * chore(flags): generate dist typings * fix(akismet): last type errors * chore: update .yarn-integrity * chore: partially run flarum-cli audit infra --fix The tsconfig changes from that command are ignored, since we don't yet support "replacable sections" that would let us add custom config. * chore: use type imports * fix: broader gitattributes * chore: run flarum-cli audit infra --monorepo --fix * feat: make `app.data` typings extensible * chore(core): format * chore: boost tags TypeScript coverage * fix(tags): further increase type coverage.
2022-03-23 23:43:14 +08:00
"@babel/plugin-transform-runtime@^7.16.0":
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "7.19.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-runtime/-/plugin-transform-runtime-7.19.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-PRH37lz4JU156lYFW1p8OxE5i7d6Sl/zV58ooyr+q1J1lnQPyg5tIiXlIwNVhJaY4W3TmOtdc8jqdXQcB1v5Yw==
dependencies:
"@babel/helper-module-imports" "^7.18.6"
"@babel/helper-plugin-utils" "^7.19.0"
babel-plugin-polyfill-corejs2 "^0.3.3"
babel-plugin-polyfill-corejs3 "^0.6.0"
babel-plugin-polyfill-regenerator "^0.4.1"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
semver "^6.3.0"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-shorthand-properties@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-shorthand-properties/-/plugin-transform-shorthand-properties-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-eCLXXJqv8okzg86ywZJbRn19YJHU4XUa55oz2wbHhaQVn/MM+XhukiT7SYqp/7o00dg52Rj51Ny+Ecw4oyoygw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-spread@^7.19.0":
version "7.19.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-spread/-/plugin-transform-spread-7.19.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-RsuMk7j6n+r752EtzyScnWkQyuJdli6LdO5Klv8Yx0OfPVTcQkIUfS8clx5e9yHXzlnhOZF3CbQ8C2uP5j074w==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.19.0"
"@babel/helper-skip-transparent-expression-wrappers" "^7.18.9"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-sticky-regex@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-sticky-regex/-/plugin-transform-sticky-regex-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-kfiDrDQ+PBsQDO85yj1icueWMfGfJFKN1KCkndygtu/C9+XUfydLC8Iv5UYJqRwy4zk8EcplRxEOeLyjq1gm6Q==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-template-literals@^7.18.9":
version "7.18.9"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-template-literals/-/plugin-transform-template-literals-7.18.9.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-S8cOWfT82gTezpYOiVaGHrCbhlHgKhQt8XH5ES46P2XWmX92yisoZywf5km75wv5sYcXDUCLMmMxOLCtthDgMA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.9"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-typeof-symbol@^7.18.9":
version "7.18.9"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-typeof-symbol/-/plugin-transform-typeof-symbol-7.18.9.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-SRfwTtF11G2aemAZWivL7PD+C9z52v9EvMqH9BuYbabyPuKUvSWks3oCg6041pT925L4zVFqaVBeECwsmlguEw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.9"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-typescript@^7.18.6":
version "7.20.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-typescript/-/plugin-transform-typescript-7.20.2.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-jvS+ngBfrnTUBfOQq8NfGnSbF9BrqlR6hjJ2yVxMkmO5nL/cdifNbI30EfjRlN4g5wYWNnMPyj5Sa6R1pbLeag==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-create-class-features-plugin" "^7.20.2"
"@babel/helper-plugin-utils" "^7.20.2"
"@babel/plugin-syntax-typescript" "^7.20.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-unicode-escapes@^7.18.10":
version "7.18.10"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-unicode-escapes/-/plugin-transform-unicode-escapes-7.18.10.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-kKAdAI+YzPgGY/ftStBFXTI1LZFju38rYThnfMykS+IXy8BVx+res7s2fxf1l8I35DV2T97ezo6+SGrXz6B3iQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.9"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-unicode-regex@^7.18.6":
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/plugin-transform-unicode-regex/-/plugin-transform-unicode-regex-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-gE7A6Lt7YLnNOL3Pb9BNeZvi+d8l7tcRrG4+pwJjK9hD2xX4mEvjlQW60G9EEmfXVYRPv9VRQcyegIVHCql/AA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-create-regexp-features-plugin" "^7.18.6"
"@babel/helper-plugin-utils" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
fix: Assorted Typing Fixes (#3348) With all the commits below, we resolve all outstanding typing issues in the repo, and CI jobs run green. * fix: Convert DashboardPage and DashboardWidget to TypeScript * fix: fix type errors in package manager ext * fix: Convert Post component to TypeScript * fix: avatar typings should accept null user * fix: convert Notification component to TypeScript * fix: properly use `typeof` in ForumApplication * feat: make Notification content attr generic * chore: format Notification component * fix: Convert DiscussionRenamedNotification to TypeScript * fix(pusher) move shims to a location where they get applied * fix(pusher): fix some typing errors * fix(akismet): fix some typing issues * chore: update core dist typings * chore(pusher): format * fix: anchorScroll should accept string selectors * fix: more accurately represent ApiQueryParamsPlural * fix: convert PostStreamState to TypeScript * chore(core): rebuild typings * feat: allow extending app.routes * fix: more flexible typings for highlight.ts * fix: use primitive `number` type for Discussion typings * fix: convert DiscussionListItem to TypeScript * chore: rebuild core typings * fix: final pusher type fixes * feat: start tags TypeScript conversion * fix: require-dev tags in pusher for CI TypeScript purposes. * chore(core): format * chore(tags): build dist typings * feat(pusher): use dist types from tags. * feat: convert flags to TypeScript * chore(flags): generate dist typings * fix(akismet): last type errors * chore: update .yarn-integrity * chore: partially run flarum-cli audit infra --fix The tsconfig changes from that command are ignored, since we don't yet support "replacable sections" that would let us add custom config. * chore: use type imports * fix: broader gitattributes * chore: run flarum-cli audit infra --monorepo --fix * feat: make `app.data` typings extensible * chore(core): format * chore: boost tags TypeScript coverage * fix(tags): further increase type coverage.
2022-03-23 23:43:14 +08:00
"@babel/preset-env@^7.16.0":
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "7.20.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/preset-env/-/preset-env-7.20.2.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-1G0efQEWR1EHkKvKHqbG+IN/QdgwfByUpM5V5QroDzGV2t3S/WXNQd693cHiHTlCFMpr9B6FkPFXDA2lQcKoDg==
dependencies:
"@babel/compat-data" "^7.20.1"
"@babel/helper-compilation-targets" "^7.20.0"
"@babel/helper-plugin-utils" "^7.20.2"
"@babel/helper-validator-option" "^7.18.6"
"@babel/plugin-bugfix-safari-id-destructuring-collision-in-function-expression" "^7.18.6"
"@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining" "^7.18.9"
"@babel/plugin-proposal-async-generator-functions" "^7.20.1"
"@babel/plugin-proposal-class-properties" "^7.18.6"
"@babel/plugin-proposal-class-static-block" "^7.18.6"
"@babel/plugin-proposal-dynamic-import" "^7.18.6"
"@babel/plugin-proposal-export-namespace-from" "^7.18.9"
"@babel/plugin-proposal-json-strings" "^7.18.6"
"@babel/plugin-proposal-logical-assignment-operators" "^7.18.9"
"@babel/plugin-proposal-nullish-coalescing-operator" "^7.18.6"
"@babel/plugin-proposal-numeric-separator" "^7.18.6"
"@babel/plugin-proposal-object-rest-spread" "^7.20.2"
"@babel/plugin-proposal-optional-catch-binding" "^7.18.6"
"@babel/plugin-proposal-optional-chaining" "^7.18.9"
"@babel/plugin-proposal-private-methods" "^7.18.6"
"@babel/plugin-proposal-private-property-in-object" "^7.18.6"
"@babel/plugin-proposal-unicode-property-regex" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@babel/plugin-syntax-async-generators" "^7.8.4"
"@babel/plugin-syntax-class-properties" "^7.12.13"
"@babel/plugin-syntax-class-static-block" "^7.14.5"
"@babel/plugin-syntax-dynamic-import" "^7.8.3"
"@babel/plugin-syntax-export-namespace-from" "^7.8.3"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-syntax-import-assertions" "^7.20.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@babel/plugin-syntax-json-strings" "^7.8.3"
"@babel/plugin-syntax-logical-assignment-operators" "^7.10.4"
"@babel/plugin-syntax-nullish-coalescing-operator" "^7.8.3"
"@babel/plugin-syntax-numeric-separator" "^7.10.4"
"@babel/plugin-syntax-object-rest-spread" "^7.8.3"
"@babel/plugin-syntax-optional-catch-binding" "^7.8.3"
"@babel/plugin-syntax-optional-chaining" "^7.8.3"
"@babel/plugin-syntax-private-property-in-object" "^7.14.5"
"@babel/plugin-syntax-top-level-await" "^7.14.5"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/plugin-transform-arrow-functions" "^7.18.6"
"@babel/plugin-transform-async-to-generator" "^7.18.6"
"@babel/plugin-transform-block-scoped-functions" "^7.18.6"
"@babel/plugin-transform-block-scoping" "^7.20.2"
"@babel/plugin-transform-classes" "^7.20.2"
"@babel/plugin-transform-computed-properties" "^7.18.9"
"@babel/plugin-transform-destructuring" "^7.20.2"
"@babel/plugin-transform-dotall-regex" "^7.18.6"
"@babel/plugin-transform-duplicate-keys" "^7.18.9"
"@babel/plugin-transform-exponentiation-operator" "^7.18.6"
"@babel/plugin-transform-for-of" "^7.18.8"
"@babel/plugin-transform-function-name" "^7.18.9"
"@babel/plugin-transform-literals" "^7.18.9"
"@babel/plugin-transform-member-expression-literals" "^7.18.6"
"@babel/plugin-transform-modules-amd" "^7.19.6"
"@babel/plugin-transform-modules-commonjs" "^7.19.6"
"@babel/plugin-transform-modules-systemjs" "^7.19.6"
"@babel/plugin-transform-modules-umd" "^7.18.6"
"@babel/plugin-transform-named-capturing-groups-regex" "^7.19.1"
"@babel/plugin-transform-new-target" "^7.18.6"
"@babel/plugin-transform-object-super" "^7.18.6"
"@babel/plugin-transform-parameters" "^7.20.1"
"@babel/plugin-transform-property-literals" "^7.18.6"
"@babel/plugin-transform-regenerator" "^7.18.6"
"@babel/plugin-transform-reserved-words" "^7.18.6"
"@babel/plugin-transform-shorthand-properties" "^7.18.6"
"@babel/plugin-transform-spread" "^7.19.0"
"@babel/plugin-transform-sticky-regex" "^7.18.6"
"@babel/plugin-transform-template-literals" "^7.18.9"
"@babel/plugin-transform-typeof-symbol" "^7.18.9"
"@babel/plugin-transform-unicode-escapes" "^7.18.10"
"@babel/plugin-transform-unicode-regex" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@babel/preset-modules" "^0.1.5"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/types" "^7.20.2"
babel-plugin-polyfill-corejs2 "^0.3.3"
babel-plugin-polyfill-corejs3 "^0.6.0"
babel-plugin-polyfill-regenerator "^0.4.1"
core-js-compat "^3.25.1"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
semver "^6.3.0"
"@babel/preset-modules@^0.1.5":
version "0.1.5"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/preset-modules/-/preset-modules-0.1.5.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-A57th6YRG7oR3cq/yt/Y84MvGgE0eJG2F1JLhKuyG+jFxEgrd/HAMJatiFtmOiZurz+0DkrvbheCLaV5f2JfjA==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-proposal-unicode-property-regex" "^7.4.4"
"@babel/plugin-transform-dotall-regex" "^7.4.4"
"@babel/types" "^7.4.4"
esutils "^2.0.2"
fix: Assorted Typing Fixes (#3348) With all the commits below, we resolve all outstanding typing issues in the repo, and CI jobs run green. * fix: Convert DashboardPage and DashboardWidget to TypeScript * fix: fix type errors in package manager ext * fix: Convert Post component to TypeScript * fix: avatar typings should accept null user * fix: convert Notification component to TypeScript * fix: properly use `typeof` in ForumApplication * feat: make Notification content attr generic * chore: format Notification component * fix: Convert DiscussionRenamedNotification to TypeScript * fix(pusher) move shims to a location where they get applied * fix(pusher): fix some typing errors * fix(akismet): fix some typing issues * chore: update core dist typings * chore(pusher): format * fix: anchorScroll should accept string selectors * fix: more accurately represent ApiQueryParamsPlural * fix: convert PostStreamState to TypeScript * chore(core): rebuild typings * feat: allow extending app.routes * fix: more flexible typings for highlight.ts * fix: use primitive `number` type for Discussion typings * fix: convert DiscussionListItem to TypeScript * chore: rebuild core typings * fix: final pusher type fixes * feat: start tags TypeScript conversion * fix: require-dev tags in pusher for CI TypeScript purposes. * chore(core): format * chore(tags): build dist typings * feat(pusher): use dist types from tags. * feat: convert flags to TypeScript * chore(flags): generate dist typings * fix(akismet): last type errors * chore: update .yarn-integrity * chore: partially run flarum-cli audit infra --fix The tsconfig changes from that command are ignored, since we don't yet support "replacable sections" that would let us add custom config. * chore: use type imports * fix: broader gitattributes * chore: run flarum-cli audit infra --monorepo --fix * feat: make `app.data` typings extensible * chore(core): format * chore: boost tags TypeScript coverage * fix(tags): further increase type coverage.
2022-03-23 23:43:14 +08:00
"@babel/preset-react@^7.16.0":
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/preset-react/-/preset-react-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-zXr6atUmyYdiWRVLOZahakYmOBHtWc2WGCkP8PYTgZi0iJXDY2CN180TdrIW4OGOAdLc7TifzDIvtx6izaRIzg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.6"
"@babel/helper-validator-option" "^7.18.6"
"@babel/plugin-transform-react-display-name" "^7.18.6"
"@babel/plugin-transform-react-jsx" "^7.18.6"
"@babel/plugin-transform-react-jsx-development" "^7.18.6"
"@babel/plugin-transform-react-pure-annotations" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
fix: Assorted Typing Fixes (#3348) With all the commits below, we resolve all outstanding typing issues in the repo, and CI jobs run green. * fix: Convert DashboardPage and DashboardWidget to TypeScript * fix: fix type errors in package manager ext * fix: Convert Post component to TypeScript * fix: avatar typings should accept null user * fix: convert Notification component to TypeScript * fix: properly use `typeof` in ForumApplication * feat: make Notification content attr generic * chore: format Notification component * fix: Convert DiscussionRenamedNotification to TypeScript * fix(pusher) move shims to a location where they get applied * fix(pusher): fix some typing errors * fix(akismet): fix some typing issues * chore: update core dist typings * chore(pusher): format * fix: anchorScroll should accept string selectors * fix: more accurately represent ApiQueryParamsPlural * fix: convert PostStreamState to TypeScript * chore(core): rebuild typings * feat: allow extending app.routes * fix: more flexible typings for highlight.ts * fix: use primitive `number` type for Discussion typings * fix: convert DiscussionListItem to TypeScript * chore: rebuild core typings * fix: final pusher type fixes * feat: start tags TypeScript conversion * fix: require-dev tags in pusher for CI TypeScript purposes. * chore(core): format * chore(tags): build dist typings * feat(pusher): use dist types from tags. * feat: convert flags to TypeScript * chore(flags): generate dist typings * fix(akismet): last type errors * chore: update .yarn-integrity * chore: partially run flarum-cli audit infra --fix The tsconfig changes from that command are ignored, since we don't yet support "replacable sections" that would let us add custom config. * chore: use type imports * fix: broader gitattributes * chore: run flarum-cli audit infra --monorepo --fix * feat: make `app.data` typings extensible * chore(core): format * chore: boost tags TypeScript coverage * fix(tags): further increase type coverage.
2022-03-23 23:43:14 +08:00
"@babel/preset-typescript@^7.16.0":
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "7.18.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/preset-typescript/-/preset-typescript-7.18.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-s9ik86kXBAnD760aybBucdpnLsAt0jK1xqJn2juOn9lkOvSHV60os5hxoVJsPzMQxvnUJFAlkont2DvvaYEBtQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-plugin-utils" "^7.18.6"
"@babel/helper-validator-option" "^7.18.6"
"@babel/plugin-transform-typescript" "^7.18.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
fix: Assorted Typing Fixes (#3348) With all the commits below, we resolve all outstanding typing issues in the repo, and CI jobs run green. * fix: Convert DashboardPage and DashboardWidget to TypeScript * fix: fix type errors in package manager ext * fix: Convert Post component to TypeScript * fix: avatar typings should accept null user * fix: convert Notification component to TypeScript * fix: properly use `typeof` in ForumApplication * feat: make Notification content attr generic * chore: format Notification component * fix: Convert DiscussionRenamedNotification to TypeScript * fix(pusher) move shims to a location where they get applied * fix(pusher): fix some typing errors * fix(akismet): fix some typing issues * chore: update core dist typings * chore(pusher): format * fix: anchorScroll should accept string selectors * fix: more accurately represent ApiQueryParamsPlural * fix: convert PostStreamState to TypeScript * chore(core): rebuild typings * feat: allow extending app.routes * fix: more flexible typings for highlight.ts * fix: use primitive `number` type for Discussion typings * fix: convert DiscussionListItem to TypeScript * chore: rebuild core typings * fix: final pusher type fixes * feat: start tags TypeScript conversion * fix: require-dev tags in pusher for CI TypeScript purposes. * chore(core): format * chore(tags): build dist typings * feat(pusher): use dist types from tags. * feat: convert flags to TypeScript * chore(flags): generate dist typings * fix(akismet): last type errors * chore: update .yarn-integrity * chore: partially run flarum-cli audit infra --fix The tsconfig changes from that command are ignored, since we don't yet support "replacable sections" that would let us add custom config. * chore: use type imports * fix: broader gitattributes * chore: run flarum-cli audit infra --monorepo --fix * feat: make `app.data` typings extensible * chore(core): format * chore: boost tags TypeScript coverage * fix(tags): further increase type coverage.
2022-03-23 23:43:14 +08:00
"@babel/runtime@^7.1.2", "@babel/runtime@^7.11.2", "@babel/runtime@^7.16.0", "@babel/runtime@^7.8.4":
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "7.20.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/runtime/-/runtime-7.20.1.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-mrzLkl6U9YLF8qpqI7TB82PESyEGjm/0Ly91jG575eVxMMlb8fYfOXFZIJ8XfLrJZQbm7dlKry2bJmXBUEkdFg==
dependencies:
regenerator-runtime "^0.13.10"
feat(jest): mithril component testing (#3679) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * feat(jest): mithril component testing * fix: use separate `tsconfig.test.json` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-11 06:02:50 +08:00
"@babel/template@^7.18.10", "@babel/template@^7.3.3":
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "7.18.10"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/template/-/template-7.18.10.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-TI+rCtooWHr3QJ27kJxfjutghu44DLnasDMwpDqCXVTal9RLp3RSYNh4NdBrRP2cQAoG9A8juOQl6P6oZG4JxA==
dependencies:
"@babel/code-frame" "^7.18.6"
"@babel/parser" "^7.18.10"
"@babel/types" "^7.18.10"
feat(jest): mithril component testing (#3679) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * feat(jest): mithril component testing * fix: use separate `tsconfig.test.json` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-11 06:02:50 +08:00
"@babel/traverse@^7.19.0", "@babel/traverse@^7.19.1", "@babel/traverse@^7.20.1", "@babel/traverse@^7.7.2":
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "7.20.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@babel/traverse/-/traverse-7.20.1.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-d3tN8fkVJwFLkHkBN479SOsw4DMZnz8cdbL/gvuDuzy3TS6Nfw80HuQqhw1pITbIruHyh7d1fMA47kWzmcUEGA==
dependencies:
"@babel/code-frame" "^7.18.6"
"@babel/generator" "^7.20.1"
"@babel/helper-environment-visitor" "^7.18.9"
"@babel/helper-function-name" "^7.19.0"
"@babel/helper-hoist-variables" "^7.18.6"
"@babel/helper-split-export-declaration" "^7.18.6"
"@babel/parser" "^7.20.1"
"@babel/types" "^7.20.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
debug "^4.1.0"
globals "^11.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@babel/types@^7.0.0", "@babel/types@^7.18.10", "@babel/types@^7.18.6", "@babel/types@^7.18.9", "@babel/types@^7.19.0", "@babel/types@^7.20.0", "@babel/types@^7.20.2", "@babel/types@^7.20.7", "@babel/types@^7.3.0", "@babel/types@^7.3.3", "@babel/types@^7.4.4":
version "7.21.3"
resolved "https://registry.npmjs.org/@babel/types/-/types-7.21.3.tgz"
integrity sha512-sBGdETxC+/M4o/zKC0sl6sjWv62WFR/uzxrJ6uYyMLZOUlPnwzw0tKgVHOXxaAd5l2g8pEDM5RZ495GPQI77kg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-string-parser" "^7.19.4"
"@babel/helper-validator-identifier" "^7.19.1"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
to-fast-properties "^2.0.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@bcoe/v8-coverage@^0.2.3":
version "0.2.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@bcoe/v8-coverage/-/v8-coverage-0.2.3.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-0hYQ8SB4Db5zvZB4axdMHGwEaQjkZzFjQiN9LVYvIFB2nSUHW9tYpxWriPrWDASIxiaXax83REcLxuSdnGPZtw==
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@colors/colors@1.5.0":
version "1.5.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@colors/colors/-/colors-1.5.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-ooWCrlZP11i8GImSjTHYHLkvFDP48nS4+204nGb1RiX/WXYHmJA2III9/e2DWVabCESdW7hBAEzHRqUn9OUVvQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@discoveryjs/json-ext@^0.5.0":
version "0.5.7"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@discoveryjs/json-ext/-/json-ext-0.5.7.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-dBVuXR082gk3jsFp7Rd/JI4kytwGHecnCoTtXFb7DB6CNHp4rg5k1bhg0nWdLGLnOV71lmDzGQaLMy8iPLY0pw==
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@flarum/akismet@file:/home/luceos/code/flarum/framework/extensions/akismet/js":
version "0.0.0"
resolved "file:extensions/akismet/js"
"@flarum/approval@file:/home/luceos/code/flarum/framework/extensions/approval/js":
version "0.0.0"
resolved "file:extensions/approval/js"
"@flarum/core@file:/home/luceos/code/flarum/framework/framework/core/js":
version "0.0.0"
resolved "file:framework/core/js"
dependencies:
"@askvortsov/rich-icu-message-formatter" "^0.2.4"
"@ultraq/icu-message-formatter" "^0.12.0"
body-scroll-lock "^4.0.0-beta.0"
bootstrap "^3.4.1"
clsx "^1.1.1"
color-thief-browser "^2.0.2"
dayjs "^1.10.7"
focus-trap "^6.7.1"
jquery "^3.6.0"
jquery.hotkeys "^0.1.0"
mithril "~2.0.4"
nanoid "^3.1.30"
punycode "^2.1.1"
textarea-caret "^3.1.0"
throttle-debounce "^3.0.1"
"@flarum/embed@file:/home/luceos/code/flarum/framework/extensions/embed/js":
version "0.0.0"
resolved "file:extensions/embed/js"
dependencies:
iframe-resizer "^4.3.2"
"@flarum/emoji@file:/home/luceos/code/flarum/framework/extensions/emoji/js":
version "0.0.0"
resolved "file:extensions/emoji/js"
dependencies:
simple-emoji-map "^0.5.1"
twemoji "^14.0.2"
"@flarum/flags@file:/home/luceos/code/flarum/framework/extensions/flags/js":
version "0.0.0"
resolved "file:extensions/flags/js"
"@flarum/jest-config@^1.0.0", "@flarum/jest-config@file:/home/luceos/code/flarum/framework/js-packages/jest-config":
version "1.0.1"
resolved "file:js-packages/jest-config"
dependencies:
"@types/jest" "^29.2.2"
flarum-webpack-config "^2.0.1"
flat "^5.0.2"
jest "^29.3.1"
jest-environment-jsdom "^29.3.1"
js-yaml "^4.1.0"
mithril-query "^4.0.1"
ts-jest "^29.0.3"
"@flarum/likes@file:/home/luceos/code/flarum/framework/extensions/likes/js":
version "0.0.0"
resolved "file:extensions/likes/js"
"@flarum/lock@file:/home/luceos/code/flarum/framework/extensions/lock/js":
version "0.0.0"
resolved "file:extensions/lock/js"
"@flarum/markdown@file:/home/luceos/code/flarum/framework/extensions/markdown/js":
version "0.0.0"
resolved "file:extensions/markdown/js"
dependencies:
flarum-webpack-config "^2.0.0"
webpack "^5.65.0"
webpack-cli "^4.9.1"
"@flarum/mentions@file:/home/luceos/code/flarum/framework/extensions/mentions/js":
version "0.0.0"
resolved "file:extensions/mentions/js"
"@flarum/nicknames@file:/home/luceos/code/flarum/framework/extensions/nicknames/js":
version "0.0.0"
resolved "file:extensions/nicknames/js"
"@flarum/package-manager@file:/home/luceos/code/flarum/framework/extensions/package-manager/js":
version "0.0.0"
resolved "file:extensions/package-manager/js"
dependencies:
pretty-bytes "^6.0.0"
"@flarum/prettier-config@^1.0.0", "@flarum/prettier-config@file:/home/luceos/code/flarum/framework/js-packages/prettier-config":
version "1.0.0"
resolved "file:js-packages/prettier-config"
"@flarum/pusher@file:/home/luceos/code/flarum/framework/extensions/pusher/js":
version "0.0.0"
resolved "file:extensions/pusher/js"
"@flarum/statistics@file:/home/luceos/code/flarum/framework/extensions/statistics/js":
version "0.0.0"
resolved "file:extensions/statistics/js"
dependencies:
frappe-charts "^1.6.2"
"@flarum/sticky@file:/home/luceos/code/flarum/framework/extensions/sticky/js":
version "0.0.0"
resolved "file:extensions/sticky/js"
"@flarum/subscriptions@file:/home/luceos/code/flarum/framework/extensions/subscriptions/js":
version "0.0.0"
resolved "file:extensions/subscriptions/js"
"@flarum/suspend@file:/home/luceos/code/flarum/framework/extensions/suspend/js":
version "0.0.0"
resolved "file:extensions/suspend/js"
"@flarum/tags@file:/home/luceos/code/flarum/framework/extensions/tags/js":
version "0.0.0"
resolved "file:extensions/tags/js"
dependencies:
sortablejs "^1.14.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@hypnosphi/create-react-context@^0.3.1":
version "0.3.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@hypnosphi/create-react-context/-/create-react-context-0.3.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-V1klUed202XahrWJLLOT3EXNeCpFHCcJntdFGI15ntCwau+jfT386w7OFTMaCqOgXUH1fa0w/I1oZs+i/Rfr0A==
dependencies:
gud "^1.0.0"
warning "^4.0.3"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@istanbuljs/load-nyc-config@^1.0.0":
version "1.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@istanbuljs/load-nyc-config/-/load-nyc-config-1.1.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-VjeHSlIzpv/NyD3N0YuHfXOPDIixcA1q2ZV98wsMqcYlPmv2n3Yb2lYP9XMElnaFVXg5A7YLTeLu6V84uQDjmQ==
dependencies:
camelcase "^5.3.1"
find-up "^4.1.0"
get-package-type "^0.1.0"
js-yaml "^3.13.1"
resolve-from "^5.0.0"
"@istanbuljs/schema@^0.1.2":
version "0.1.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@istanbuljs/schema/-/schema-0.1.3.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-ZXRY4jNvVgSVQ8DL3LTcakaAtXwTVUxE81hslsyD2AtoXW/wVob10HkOJ1X/pAlcI7D+2YoZKg5do8G/w6RYgA==
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/console@^29.5.0":
version "29.5.0"
resolved "https://registry.npmjs.org/@jest/console/-/console-29.5.0.tgz"
integrity sha512-NEpkObxPwyw/XxZVLPmAGKE89IQRp4puc6IQRPru6JKd1M3fW9v1xM1AnzIJE65hbCkzQAdnL8P47e9hzhiYLQ==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/types" "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@types/node" "*"
chalk "^4.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-message-util "^29.5.0"
jest-util "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
slash "^3.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/core@^29.5.0":
version "29.5.0"
resolved "https://registry.npmjs.org/@jest/core/-/core-29.5.0.tgz"
integrity sha512-28UzQc7ulUrOQw1IsN/kv1QES3q2kkbl/wGslyhAclqZ/8cMdB5M68BffkIdSJgKBUt50d3hbwJ92XESlE7LiQ==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/console" "^29.5.0"
"@jest/reporters" "^29.5.0"
"@jest/test-result" "^29.5.0"
"@jest/transform" "^29.5.0"
"@jest/types" "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@types/node" "*"
ansi-escapes "^4.2.1"
chalk "^4.0.0"
ci-info "^3.2.0"
exit "^0.1.2"
graceful-fs "^4.2.9"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-changed-files "^29.5.0"
jest-config "^29.5.0"
jest-haste-map "^29.5.0"
jest-message-util "^29.5.0"
jest-regex-util "^29.4.3"
jest-resolve "^29.5.0"
jest-resolve-dependencies "^29.5.0"
jest-runner "^29.5.0"
jest-runtime "^29.5.0"
jest-snapshot "^29.5.0"
jest-util "^29.5.0"
jest-validate "^29.5.0"
jest-watcher "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
micromatch "^4.0.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
pretty-format "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
slash "^3.0.0"
strip-ansi "^6.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/environment@^29.5.0":
version "29.5.0"
resolved "https://registry.npmjs.org/@jest/environment/-/environment-29.5.0.tgz"
integrity sha512-5FXw2+wD29YU1d4I2htpRX7jYnAyTRjP2CsXQdo9SAM8g3ifxWPSV0HnClSn71xwctr0U3oZIIH+dtbfmnbXVQ==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/fake-timers" "^29.5.0"
"@jest/types" "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@types/node" "*"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-mock "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/expect-utils@^29.5.0":
version "29.5.0"
resolved "https://registry.npmjs.org/@jest/expect-utils/-/expect-utils-29.5.0.tgz"
integrity sha512-fmKzsidoXQT2KwnrwE0SQq3uj8Z763vzR8LnLBwC2qYWEFpjX8daRsk6rHUM1QvNlEW/UJXNXm59ztmJJWs2Mg==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-get-type "^29.4.3"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/expect@^29.5.0":
version "29.5.0"
resolved "https://registry.npmjs.org/@jest/expect/-/expect-29.5.0.tgz"
integrity sha512-PueDR2HGihN3ciUNGr4uelropW7rqUfTiOn+8u0leg/42UhblPxHkfoh0Ruu3I9Y1962P3u2DY4+h7GVTSVU6g==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
expect "^29.5.0"
jest-snapshot "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/fake-timers@^29.5.0":
version "29.5.0"
resolved "https://registry.npmjs.org/@jest/fake-timers/-/fake-timers-29.5.0.tgz"
integrity sha512-9ARvuAAQcBwDAqOnglWq2zwNIRUDtk/SCkp/ToGEhFv5r86K21l+VEs0qNTaXtyiY0lEePl3kylijSYJQqdbDg==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/types" "^29.5.0"
"@sinonjs/fake-timers" "^10.0.2"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@types/node" "*"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-message-util "^29.5.0"
jest-mock "^29.5.0"
jest-util "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/globals@^29.5.0":
version "29.5.0"
resolved "https://registry.npmjs.org/@jest/globals/-/globals-29.5.0.tgz"
integrity sha512-S02y0qMWGihdzNbUiqSAiKSpSozSuHX5UYc7QbnHP+D9Lyw8DgGGCinrN9uSuHPeKgSSzvPom2q1nAtBvUsvPQ==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/environment" "^29.5.0"
"@jest/expect" "^29.5.0"
"@jest/types" "^29.5.0"
jest-mock "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/reporters@^29.5.0":
version "29.5.0"
resolved "https://registry.npmjs.org/@jest/reporters/-/reporters-29.5.0.tgz"
integrity sha512-D05STXqj/M8bP9hQNSICtPqz97u7ffGzZu+9XLucXhkOFBqKcXe04JLZOgIekOxdb73MAoBUFnqvf7MCpKk5OA==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
"@bcoe/v8-coverage" "^0.2.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/console" "^29.5.0"
"@jest/test-result" "^29.5.0"
"@jest/transform" "^29.5.0"
"@jest/types" "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@jridgewell/trace-mapping" "^0.3.15"
"@types/node" "*"
chalk "^4.0.0"
collect-v8-coverage "^1.0.0"
exit "^0.1.2"
glob "^7.1.3"
graceful-fs "^4.2.9"
istanbul-lib-coverage "^3.0.0"
istanbul-lib-instrument "^5.1.0"
istanbul-lib-report "^3.0.0"
istanbul-lib-source-maps "^4.0.0"
istanbul-reports "^3.1.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-message-util "^29.5.0"
jest-util "^29.5.0"
jest-worker "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
slash "^3.0.0"
string-length "^4.0.1"
strip-ansi "^6.0.0"
v8-to-istanbul "^9.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/schemas@^29.4.3":
version "29.4.3"
resolved "https://registry.npmjs.org/@jest/schemas/-/schemas-29.4.3.tgz"
integrity sha512-VLYKXQmtmuEz6IxJsrZwzG9NvtkQsWNnWMsKxqWNu3+CnfzJQhp0WDDKWLVV9hLKr0l3SLLFRqcYHjhtyuDVxg==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@sinclair/typebox" "^0.25.16"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/source-map@^29.4.3":
version "29.4.3"
resolved "https://registry.npmjs.org/@jest/source-map/-/source-map-29.4.3.tgz"
integrity sha512-qyt/mb6rLyd9j1jUts4EQncvS6Yy3PM9HghnNv86QBlV+zdL2inCdK1tuVlL+J+lpiw2BI67qXOrX3UurBqQ1w==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
"@jridgewell/trace-mapping" "^0.3.15"
callsites "^3.0.0"
graceful-fs "^4.2.9"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/test-result@^29.5.0":
version "29.5.0"
resolved "https://registry.npmjs.org/@jest/test-result/-/test-result-29.5.0.tgz"
integrity sha512-fGl4rfitnbfLsrfx1uUpDEESS7zM8JdgZgOCQuxQvL1Sn/I6ijeAVQWGfXI9zb1i9Mzo495cIpVZhA0yr60PkQ==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/console" "^29.5.0"
"@jest/types" "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@types/istanbul-lib-coverage" "^2.0.0"
collect-v8-coverage "^1.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/test-sequencer@^29.5.0":
version "29.5.0"
resolved "https://registry.npmjs.org/@jest/test-sequencer/-/test-sequencer-29.5.0.tgz"
integrity sha512-yPafQEcKjkSfDXyvtgiV4pevSeyuA6MQr6ZIdVkWJly9vkqjnFfcfhRQqpD5whjoU8EORki752xQmjaqoFjzMQ==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/test-result" "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
graceful-fs "^4.2.9"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-haste-map "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
slash "^3.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/transform@^29.5.0":
version "29.5.0"
resolved "https://registry.npmjs.org/@jest/transform/-/transform-29.5.0.tgz"
integrity sha512-8vbeZWqLJOvHaDfeMuoHITGKSz5qWc9u04lnWrQE3VyuSw604PzQM824ZeX9XSjUCeDiE3GuxZe5UKa8J61NQw==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
"@babel/core" "^7.11.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/types" "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@jridgewell/trace-mapping" "^0.3.15"
babel-plugin-istanbul "^6.1.1"
chalk "^4.0.0"
convert-source-map "^2.0.0"
fast-json-stable-stringify "^2.1.0"
graceful-fs "^4.2.9"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-haste-map "^29.5.0"
jest-regex-util "^29.4.3"
jest-util "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
micromatch "^4.0.4"
pirates "^4.0.4"
slash "^3.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
write-file-atomic "^4.0.2"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/types@^29.0.0", "@jest/types@^29.5.0":
version "29.5.0"
resolved "https://registry.npmjs.org/@jest/types/-/types-29.5.0.tgz"
integrity sha512-qbu7kN6czmVRc3xWFQcAN03RAUamgppVUdXrvl1Wr3jlNF93o9mJbGcDWrwGB6ht44u7efB1qCFgVQmca24Uog==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/schemas" "^29.4.3"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@types/istanbul-lib-coverage" "^2.0.0"
"@types/istanbul-reports" "^3.0.0"
"@types/node" "*"
"@types/yargs" "^17.0.8"
chalk "^4.0.0"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@jridgewell/gen-mapping@^0.1.0":
version "0.1.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@jridgewell/gen-mapping/-/gen-mapping-0.1.1.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-sQXCasFk+U8lWYEe66WxRDOE9PjVz4vSM51fTu3Hw+ClTpUSQb718772vH3pyS5pShp6lvQM7SxgIDXXXmOX7w==
dependencies:
"@jridgewell/set-array" "^1.0.0"
"@jridgewell/sourcemap-codec" "^1.4.10"
"@jridgewell/gen-mapping@^0.3.0", "@jridgewell/gen-mapping@^0.3.2":
chore(deps): bump terser from 5.12.0 to 5.14.2 (#3551) Bumps [terser](https://github.com/terser/terser) from 5.12.0 to 5.14.2. - [Release notes](https://github.com/terser/terser/releases) - [Changelog](https://github.com/terser/terser/blob/master/CHANGELOG.md) - [Commits](https://github.com/terser/terser/commits) --- updated-dependencies: - dependency-name: terser dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2022-07-29 20:48:04 +08:00
version "0.3.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@jridgewell/gen-mapping/-/gen-mapping-0.3.2.tgz"
chore(deps): bump terser from 5.12.0 to 5.14.2 (#3551) Bumps [terser](https://github.com/terser/terser) from 5.12.0 to 5.14.2. - [Release notes](https://github.com/terser/terser/releases) - [Changelog](https://github.com/terser/terser/blob/master/CHANGELOG.md) - [Commits](https://github.com/terser/terser/commits) --- updated-dependencies: - dependency-name: terser dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2022-07-29 20:48:04 +08:00
integrity sha512-mh65xKQAzI6iBcFzwv28KVWSmCkdRBWoOh+bYQGW3+6OZvbbN3TqMGo5hqYxQniRcH9F2VZIoJCm4pa3BPDK/A==
dependencies:
"@jridgewell/set-array" "^1.0.1"
"@jridgewell/sourcemap-codec" "^1.4.10"
"@jridgewell/trace-mapping" "^0.3.9"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@jridgewell/resolve-uri@3.1.0":
chore(deps): bump terser from 5.12.0 to 5.14.2 (#3551) Bumps [terser](https://github.com/terser/terser) from 5.12.0 to 5.14.2. - [Release notes](https://github.com/terser/terser/releases) - [Changelog](https://github.com/terser/terser/blob/master/CHANGELOG.md) - [Commits](https://github.com/terser/terser/commits) --- updated-dependencies: - dependency-name: terser dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2022-07-29 20:48:04 +08:00
version "3.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@jridgewell/resolve-uri/-/resolve-uri-3.1.0.tgz"
chore(deps): bump terser from 5.12.0 to 5.14.2 (#3551) Bumps [terser](https://github.com/terser/terser) from 5.12.0 to 5.14.2. - [Release notes](https://github.com/terser/terser/releases) - [Changelog](https://github.com/terser/terser/blob/master/CHANGELOG.md) - [Commits](https://github.com/terser/terser/commits) --- updated-dependencies: - dependency-name: terser dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2022-07-29 20:48:04 +08:00
integrity sha512-F2msla3tad+Mfht5cJq7LSXcdudKTWCVYUgw6pLFOOHSTtZlj6SWNYAp+AhuqLmWdBO2X5hPrLcu8cVP8fy28w==
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@jridgewell/set-array@^1.0.0", "@jridgewell/set-array@^1.0.1":
chore(deps): bump terser from 5.12.0 to 5.14.2 (#3551) Bumps [terser](https://github.com/terser/terser) from 5.12.0 to 5.14.2. - [Release notes](https://github.com/terser/terser/releases) - [Changelog](https://github.com/terser/terser/blob/master/CHANGELOG.md) - [Commits](https://github.com/terser/terser/commits) --- updated-dependencies: - dependency-name: terser dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2022-07-29 20:48:04 +08:00
version "1.1.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@jridgewell/set-array/-/set-array-1.1.2.tgz"
chore(deps): bump terser from 5.12.0 to 5.14.2 (#3551) Bumps [terser](https://github.com/terser/terser) from 5.12.0 to 5.14.2. - [Release notes](https://github.com/terser/terser/releases) - [Changelog](https://github.com/terser/terser/blob/master/CHANGELOG.md) - [Commits](https://github.com/terser/terser/commits) --- updated-dependencies: - dependency-name: terser dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2022-07-29 20:48:04 +08:00
integrity sha512-xnkseuNADM0gt2bs+BvhO0p78Mk762YnZdsuzFV018NoG1Sj1SCQvpSqa7XUaTam5vAGasABV9qXASMKnFMwMw==
"@jridgewell/source-map@^0.3.2":
version "0.3.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@jridgewell/source-map/-/source-map-0.3.2.tgz"
chore(deps): bump terser from 5.12.0 to 5.14.2 (#3551) Bumps [terser](https://github.com/terser/terser) from 5.12.0 to 5.14.2. - [Release notes](https://github.com/terser/terser/releases) - [Changelog](https://github.com/terser/terser/blob/master/CHANGELOG.md) - [Commits](https://github.com/terser/terser/commits) --- updated-dependencies: - dependency-name: terser dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2022-07-29 20:48:04 +08:00
integrity sha512-m7O9o2uR8k2ObDysZYzdfhb08VuEml5oWGiosa1VdaPZ/A6QyPkAJuwN0Q1lhULOf6B7MtQmHENS743hWtCrgw==
dependencies:
"@jridgewell/gen-mapping" "^0.3.0"
"@jridgewell/trace-mapping" "^0.3.9"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jridgewell/sourcemap-codec@^1.4.10", "@jridgewell/sourcemap-codec@1.4.14":
chore(deps): bump terser from 5.12.0 to 5.14.2 (#3551) Bumps [terser](https://github.com/terser/terser) from 5.12.0 to 5.14.2. - [Release notes](https://github.com/terser/terser/releases) - [Changelog](https://github.com/terser/terser/blob/master/CHANGELOG.md) - [Commits](https://github.com/terser/terser/commits) --- updated-dependencies: - dependency-name: terser dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2022-07-29 20:48:04 +08:00
version "1.4.14"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@jridgewell/sourcemap-codec/-/sourcemap-codec-1.4.14.tgz"
chore(deps): bump terser from 5.12.0 to 5.14.2 (#3551) Bumps [terser](https://github.com/terser/terser) from 5.12.0 to 5.14.2. - [Release notes](https://github.com/terser/terser/releases) - [Changelog](https://github.com/terser/terser/blob/master/CHANGELOG.md) - [Commits](https://github.com/terser/terser/commits) --- updated-dependencies: - dependency-name: terser dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2022-07-29 20:48:04 +08:00
integrity sha512-XPSJHWmi394fuUuzDnGz1wiKqWfo1yXecHQMRf2l6hztTO+nPru658AyDngaBe7isIxEkRsPR3FZh+s7iVa4Uw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@jridgewell/trace-mapping@^0.3.12", "@jridgewell/trace-mapping@^0.3.14", "@jridgewell/trace-mapping@^0.3.15", "@jridgewell/trace-mapping@^0.3.9":
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "0.3.17"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@jridgewell/trace-mapping/-/trace-mapping-0.3.17.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-MCNzAp77qzKca9+W/+I0+sEpaUnZoeasnghNeVc41VZCEKaCH73Vq3BZZ/SzWIgrqE4H4ceI+p+b6C0mHf9T4g==
chore(deps): bump terser from 5.12.0 to 5.14.2 (#3551) Bumps [terser](https://github.com/terser/terser) from 5.12.0 to 5.14.2. - [Release notes](https://github.com/terser/terser/releases) - [Changelog](https://github.com/terser/terser/blob/master/CHANGELOG.md) - [Commits](https://github.com/terser/terser/commits) --- updated-dependencies: - dependency-name: terser dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2022-07-29 20:48:04 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@jridgewell/resolve-uri" "3.1.0"
"@jridgewell/sourcemap-codec" "1.4.14"
chore(deps): bump terser from 5.12.0 to 5.14.2 (#3551) Bumps [terser](https://github.com/terser/terser) from 5.12.0 to 5.14.2. - [Release notes](https://github.com/terser/terser/releases) - [Changelog](https://github.com/terser/terser/blob/master/CHANGELOG.md) - [Commits](https://github.com/terser/terser/commits) --- updated-dependencies: - dependency-name: terser dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2022-07-29 20:48:04 +08:00
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@nodelib/fs.scandir@2.1.5":
version "2.1.5"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@nodelib/fs.scandir/-/fs.scandir-2.1.5.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-vq24Bq3ym5HEQm2NKCr3yXDwjc7vTsEThRDnkp2DK9p1uqLR+DHurm/NOTo0KG7HYHU7eppKZj3MyqYuMBf62g==
dependencies:
"@nodelib/fs.stat" "2.0.5"
run-parallel "^1.1.9"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@nodelib/fs.stat@^2.0.2", "@nodelib/fs.stat@2.0.5":
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "2.0.5"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@nodelib/fs.stat/-/fs.stat-2.0.5.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-RkhPPp2zrqDAQA/2jNhnztcPAlv64XdhIp7a7454A5ovI7Bukxgt7MX7udwAu3zg1DcpPU0rz3VV1SeaqvY4+A==
"@nodelib/fs.walk@^1.2.3":
version "1.2.8"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@nodelib/fs.walk/-/fs.walk-1.2.8.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-oGB+UxlgWcgQkgwo8GcEGwemoTFt3FIO9ababBmaGwXIoBKZ+GTy0pP185beGg7Llih/NSHSV2XAs1lnznocSg==
dependencies:
"@nodelib/fs.scandir" "2.1.5"
fastq "^1.6.0"
"@polka/url@^1.0.0-next.20":
version "1.0.0-next.21"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@polka/url/-/url-1.0.0-next.21.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-a5Sab1C4/icpTZVzZc5Ghpz88yQtGOyNqYXcZgOssB2uuAr+wF/MvN6bgtW32q7HHrvBki+BsZ0OuNv6EV3K9g==
"@semantic-ui-react/event-stack@^3.1.0":
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "3.1.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@semantic-ui-react/event-stack/-/event-stack-3.1.3.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-FdTmJyWvJaYinHrKRsMLDrz4tTMGdFfds299Qory53hBugiDvGC0tEJf+cHsi5igDwWb/CLOgOiChInHwq8URQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
exenv "^1.2.2"
prop-types "^15.6.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@sinclair/typebox@^0.25.16":
version "0.25.24"
resolved "https://registry.npmjs.org/@sinclair/typebox/-/typebox-0.25.24.tgz"
integrity sha512-XJfwUVUKDHF5ugKwIcxEgc9k8b7HbznCp6eUfWgu710hMPNIO4aw4/zB5RogDQz8nd6gyCDpU9O/m6qYEWY6yQ==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@sinonjs/commons@^2.0.0":
version "2.0.0"
resolved "https://registry.npmjs.org/@sinonjs/commons/-/commons-2.0.0.tgz"
integrity sha512-uLa0j859mMrg2slwQYdO/AkrOfmH+X6LTVmNTS9CqexuE2IvVORIkSpJLqePAbEnKJ77aMmCwr1NUZ57120Xcg==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
type-detect "4.0.8"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@sinonjs/fake-timers@^10.0.2":
version "10.0.2"
resolved "https://registry.npmjs.org/@sinonjs/fake-timers/-/fake-timers-10.0.2.tgz"
integrity sha512-SwUDyjWnah1AaNl7kxsa7cfLhlTYoiyhDAIgyh+El30YvXs/o7OLXpYH88Zdhyx9JExKrmHDJ+10bwIcY80Jmw==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@sinonjs/commons" "^2.0.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@stardust-ui/react-component-event-listener@~0.38.0":
version "0.38.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@stardust-ui/react-component-event-listener/-/react-component-event-listener-0.38.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-sIP/e0dyOrrlb8K7KWumfMxj/gAifswTBC4o68Aa+C/GA73ccRp/6W1VlHvF/dlOR4KLsA+5SKnhjH36xzPsWg==
dependencies:
"@babel/runtime" "^7.1.2"
prop-types "^15.7.2"
"@stardust-ui/react-component-ref@~0.38.0":
version "0.38.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@stardust-ui/react-component-ref/-/react-component-ref-0.38.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-xjs6WnvJVueSIXMWw0C3oWIgAPpcD03qw43oGOjUXqFktvpNkB73JoKIhS4sCrtQxBdct75qqr4ZL6JiyPcESw==
dependencies:
"@babel/runtime" "^7.1.2"
prop-types "^15.7.2"
react-is "^16.6.3"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@tootallnate/once@2":
version "2.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@tootallnate/once/-/once-2.0.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-XCuKFP5PS55gnMVu3dty8KPatLqUoy/ZYzDzAGCQ8JNFCkLXzmI7vNHCR+XpbZaMWQK/vQubr7PkYq8g470J/A==
"@types/babel__core@^7.1.14":
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
version "7.20.0"
resolved "https://registry.npmjs.org/@types/babel__core/-/babel__core-7.20.0.tgz"
integrity sha512-+n8dL/9GWblDO0iU6eZAwEIJVr5DWigtle+Q6HLOrh/pdbXOhOtqzq8VPPE2zvNJzSKY4vH/z3iT3tn0A3ypiQ==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@babel/parser" "^7.20.7"
"@babel/types" "^7.20.7"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@types/babel__generator" "*"
"@types/babel__template" "*"
"@types/babel__traverse" "*"
"@types/babel__generator@*":
version "7.6.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@types/babel__generator/-/babel__generator-7.6.4.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-tFkciB9j2K755yrTALxD44McOrk+gfpIpvC3sxHjRawj6PfnQxrse4Clq5y/Rq+G3mrBurMax/lG8Qn2t9mSsg==
dependencies:
"@babel/types" "^7.0.0"
"@types/babel__template@*":
version "7.4.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@types/babel__template/-/babel__template-7.4.1.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-azBFKemX6kMg5Io+/rdGT0dkGreboUVR0Cdm3fz9QJWpaQGJRQXl7C+6hOTCZcMll7KFyEQpgbYI2lHdsS4U7g==
dependencies:
"@babel/parser" "^7.1.0"
"@babel/types" "^7.0.0"
"@types/babel__traverse@*", "@types/babel__traverse@^7.0.6":
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
version "7.18.3"
resolved "https://registry.npmjs.org/@types/babel__traverse/-/babel__traverse-7.18.3.tgz"
integrity sha512-1kbcJ40lLB7MHsj39U4Sh1uTd2E7rLEa79kmDpI6cy+XiXsteB3POdQomoq4FxszMrO3ZYchkhYJw7A2862b3w==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
"@babel/types" "^7.3.0"
feat(modals): support stacking modals, remove bootstrap modals dependency (#3456) * Feature: Stackable modals * Processed feedback * fix: use position in modal stack rather than key for modal number * fix: use correct base z-index * chore: simplify `className` to `class` * chore: add `key` attribute to ModalManager element * fix: backdrop flashing as modals are stacked/unstacked * chore: simplify modal close process * docs: add TS overload to indicate deprecated modal opening syntax Require explicit values for `attrs` and `stackModal` from Flarum 2.0, beginning deprecation from now. * feat: use stackable modal for forgot password modal above sign in * chore: explicitly check if modal is open before trying to focus trap * fix(a11y): add missing `aria-hidden` on main content when modal open * fix(a11y): add missing `aria-modal` on modal * chore: remove test code * chore: remove dead CSS * chore: remove overload * fix: lock page scrolling when modal is open * fix: strange scrolling behaviour * chore: convert to JSX * fix: event listener memory leak * chore: remove unneeded optional chaining * fix: incorrect return types * chore: rewrite backdrop system - use one backdrop for all modals * docs: typos in comment block * fix: show backdrop directly below top-most modal Co-authored-by: Sami Mazouz <sychocouldy@gmail.com> * chore: format * fix: use an invisible backdrop for each modal to exit Signed-off-by: Sami Mazouz <ilyasmazouz@gmail.com> * chore: remove debugging code Signed-off-by: Sami Mazouz <ilyasmazouz@gmail.com> * chore: remove forgotten debug code Co-authored-by: David Wheatley <david@davwheat.dev> Co-authored-by: Sami Mazouz <sychocouldy@gmail.com>
2022-08-08 20:29:14 +08:00
"@types/body-scroll-lock@^3.1.0":
version "3.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@types/body-scroll-lock/-/body-scroll-lock-3.1.0.tgz"
feat(modals): support stacking modals, remove bootstrap modals dependency (#3456) * Feature: Stackable modals * Processed feedback * fix: use position in modal stack rather than key for modal number * fix: use correct base z-index * chore: simplify `className` to `class` * chore: add `key` attribute to ModalManager element * fix: backdrop flashing as modals are stacked/unstacked * chore: simplify modal close process * docs: add TS overload to indicate deprecated modal opening syntax Require explicit values for `attrs` and `stackModal` from Flarum 2.0, beginning deprecation from now. * feat: use stackable modal for forgot password modal above sign in * chore: explicitly check if modal is open before trying to focus trap * fix(a11y): add missing `aria-hidden` on main content when modal open * fix(a11y): add missing `aria-modal` on modal * chore: remove test code * chore: remove dead CSS * chore: remove overload * fix: lock page scrolling when modal is open * fix: strange scrolling behaviour * chore: convert to JSX * fix: event listener memory leak * chore: remove unneeded optional chaining * fix: incorrect return types * chore: rewrite backdrop system - use one backdrop for all modals * docs: typos in comment block * fix: show backdrop directly below top-most modal Co-authored-by: Sami Mazouz <sychocouldy@gmail.com> * chore: format * fix: use an invisible backdrop for each modal to exit Signed-off-by: Sami Mazouz <ilyasmazouz@gmail.com> * chore: remove debugging code Signed-off-by: Sami Mazouz <ilyasmazouz@gmail.com> * chore: remove forgotten debug code Co-authored-by: David Wheatley <david@davwheat.dev> Co-authored-by: Sami Mazouz <sychocouldy@gmail.com>
2022-08-08 20:29:14 +08:00
integrity sha512-3owAC4iJub5WPqRhxd8INarF2bWeQq1yQHBgYhN0XLBJMpd5ED10RrJ3aKiAwlTyL5wK7RkBD4SZUQz2AAAMdA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@types/eslint-scope@^3.7.3":
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "3.7.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@types/eslint-scope/-/eslint-scope-3.7.4.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-9K4zoImiZc3HlIp6AVUDE4CWYx22a+lhSZMYNpbjW04+YF0KWj4pJXnEMjdnFTiQibFFmElcsasJXDbdI/EPhA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
"@types/eslint" "*"
"@types/estree" "*"
"@types/eslint@*":
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "8.4.10"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@types/eslint/-/eslint-8.4.10.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-Sl/HOqN8NKPmhWo2VBEPm0nvHnu2LL3v9vKo8MEq0EtbJ4eVzGPl41VNPvn5E1i5poMk4/XD8UriLHpJvEP/Nw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
"@types/estree" "*"
"@types/json-schema" "*"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@types/estree@*":
version "1.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@types/estree/-/estree-1.0.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-WulqXMDUTYAXCjZnk6JtIHPigp55cVtDgDrO2gHRwhyJto21+1zbVCtOYB2L1F9w4qCQ0rOGWBnBe0FNTiEJIQ==
"@types/estree@^0.0.51":
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "0.0.51"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@types/estree/-/estree-0.0.51.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-CuPgU6f3eT/XgKKPqKd/gLZV1Xmvf1a2R5POBOGQa6uv82xpls89HU5zKeVoyR8XzHd1RGNOlQlvUe3CFkjWNQ==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@types/graceful-fs@^4.1.3":
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
version "4.1.6"
resolved "https://registry.npmjs.org/@types/graceful-fs/-/graceful-fs-4.1.6.tgz"
integrity sha512-Sig0SNORX9fdW+bQuTEovKj3uHcUL6LQKbCrrqb1X7J6/ReAbhCXRAhc+SMejhLELFj2QcyuxmUooZ4bt5ReSw==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
"@types/node" "*"
"@types/istanbul-lib-coverage@*", "@types/istanbul-lib-coverage@^2.0.0", "@types/istanbul-lib-coverage@^2.0.1":
version "2.0.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@types/istanbul-lib-coverage/-/istanbul-lib-coverage-2.0.4.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-z/QT1XN4K4KYuslS23k62yDIDLwLFkzxOuMplDtObz0+y7VqJCaO2o+SPwHCvLFZh7xazvvoor2tA/hPz9ee7g==
"@types/istanbul-lib-report@*":
version "3.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@types/istanbul-lib-report/-/istanbul-lib-report-3.0.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-plGgXAPfVKFoYfa9NpYDAkseG+g6Jr294RqeqcqDixSbU34MZVJRi/P+7Y8GDpzkEwLaGZZOpKIEmeVZNtKsrg==
dependencies:
"@types/istanbul-lib-coverage" "*"
"@types/istanbul-reports@^3.0.0":
version "3.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@types/istanbul-reports/-/istanbul-reports-3.0.1.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-c3mAZEuK0lvBp8tmuL74XRKn1+y2dcwOUpH7x4WrF6gk1GIgiluDRgMYQtw2OFcBvAJWlt6ASU3tSqxp0Uu0Aw==
dependencies:
"@types/istanbul-lib-report" "*"
"@types/jest@^29.2.2":
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
version "29.5.0"
resolved "https://registry.npmjs.org/@types/jest/-/jest-29.5.0.tgz"
integrity sha512-3Emr5VOl/aoBwnWcH/EFQvlSAmjV+XtV9GGu5mwdYew5vhQh0IUZx/60x0TzHDu09Bi7HMx10t/namdJw5QIcg==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
expect "^29.0.0"
pretty-format "^29.0.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@types/jquery@^3.5.10", "@types/jquery@^3.5.5":
version "3.5.14"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@types/jquery/-/jquery-3.5.14.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-X1gtMRMbziVQkErhTQmSe2jFwwENA/Zr+PprCkF63vFq+Yt5PZ4AlKqgmeNlwgn7dhsXEK888eIW2520EpC+xg==
dependencies:
"@types/sizzle" "*"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@types/jsdom@^20.0.0":
version "20.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@types/jsdom/-/jsdom-20.0.1.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-d0r18sZPmMQr1eG35u12FZfhIXNrnsPU/g5wvRKCUf/tOGilKKwYMYGqh33BNR6ba+2gkHw1EUiHoN3mn7E5IQ==
dependencies:
"@types/node" "*"
"@types/tough-cookie" "*"
parse5 "^7.0.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@types/json-schema@*", "@types/json-schema@^7.0.5", "@types/json-schema@^7.0.8":
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "7.0.11"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@types/json-schema/-/json-schema-7.0.11.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-wOuvG1SN4Us4rez+tylwwwCV1psiNVOkJeM3AUWUNWg/jDQY2+HE/444y5gc+jBmRqASOm2Oeh5c1axHobwRKQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@types/mithril@^2.0.11", "@types/mithril@^2.0.7", "@types/mithril@^2.0.8":
perf(statistics): rewrite for performance on very large communities (#3531) Co-authored-by: Sami Mazouz <ilyasmazouz@gmail.com>
2022-07-19 02:07:38 +08:00
version "2.0.11"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@types/mithril/-/mithril-2.0.11.tgz"
perf(statistics): rewrite for performance on very large communities (#3531) Co-authored-by: Sami Mazouz <ilyasmazouz@gmail.com>
2022-07-19 02:07:38 +08:00
integrity sha512-2tYTImXc7RzWkPpgcbnSKpV46DQI4Bm8CfgmkrIbst8MJlX6d8hdgy2yQCEf5NZYLGNyK4xbzb4rr8VPmk0iXQ==
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@types/node@*", "@types/node@^14.14.31":
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "14.18.33"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@types/node/-/node-14.18.33.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-qelS/Ra6sacc4loe/3MSjXNL1dNQ/GjxNHVzuChwMfmk7HuycRLVQN2qNY3XahK+fZc5E2szqQSKUyAF0E+2bg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@types/normalize-package-data@^2.4.0":
version "2.4.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@types/normalize-package-data/-/normalize-package-data-2.4.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-Gj7cI7z+98M282Tqmp2K5EIsoouUEzbBJhQQzDE3jSIRk6r9gsz0oUokqIUR4u1R3dMHo0pDHM7sNOHyhulypw==
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
"@types/parse-json@^4.0.0":
version "4.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@types/parse-json/-/parse-json-4.0.0.tgz"
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
integrity sha512-//oorEZjL6sbPcKUaCdIGlIUeH26mgzimjBB77G6XRgnDl/L5wOnpyBGRe/Mmf5CVW3PwEBE1NjiMZ/ssFh4wA==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@types/prettier@^2.1.5":
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
version "2.7.2"
resolved "https://registry.npmjs.org/@types/prettier/-/prettier-2.7.2.tgz"
integrity sha512-KufADq8uQqo1pYKVIYzfKbJfBAc0sOeXqGbFaSpv8MRmC/zXgowNZmFcbngndGk922QDmOASEXUZCaY48gs4cg==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@types/punycode@^2.1.0":
version "2.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@types/punycode/-/punycode-2.1.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-PG5aLpW6PJOeV2fHRslP4IOMWn+G+Uq8CfnyJ+PDS8ndCbU+soO+fB3NKCKo0p/Jh2Y4aPaiQZsrOXFdzpcA6g==
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
"@types/pusher-js@^5.1.0":
version "5.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@types/pusher-js/-/pusher-js-5.1.0.tgz"
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
integrity sha512-VubdW1NvHAojLFtJ+FWmZsIlkSE+EiaLrrfCKcW/t9UDlXWF85rSPVc+5zdpZLVzkwaUaFeyIYSgeNfXc9Dxlg==
dependencies:
pusher-js "*"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@types/sizzle@*":
version "2.3.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@types/sizzle/-/sizzle-2.3.3.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-JYM8x9EGF163bEyhdJBpR2QX1R5naCJHC8ucJylJ3w9/CVBaskdQ8WqBf8MmQrd1kRvp/a4TS8HJ+bxzR7ZJYQ==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@types/stack-utils@^2.0.0":
version "2.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@types/stack-utils/-/stack-utils-2.0.1.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-Hl219/BT5fLAaz6NDkSuhzasy49dwQS/DSdu4MdggFB8zcXv7vflBI3xp7FEmkmdDkBUI2bPUNeMttp2knYdxw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@types/textarea-caret@^3.0.1":
version "3.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@types/textarea-caret/-/textarea-caret-3.0.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-JjrXYzk4t6dM/5nz1hHkZXmd3xSdJM6mOIDSBUrpg4xThwKNryiu4CqHx81LwUJHxEEoQWHTu4fMV4em+c5bXg==
"@types/throttle-debounce@^2.1.0":
version "2.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@types/throttle-debounce/-/throttle-debounce-2.1.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-5eQEtSCoESnh2FsiLTxE121IiE60hnMqcb435fShf4bpLRjEu1Eoekht23y6zXS9Ts3l+Szu3TARnTsA0GkOkQ==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@types/tough-cookie@*":
version "4.0.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@types/tough-cookie/-/tough-cookie-4.0.2.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-Q5vtl1W5ue16D+nIaW8JWebSSraJVlK+EthKn7e7UcD4KWsaSJ8BqGPXNaPghgtcn/fhvrN17Tv8ksUsQpiplw==
feat: access tokens user management UI (#3587) Signed-off-by: Sami Mazouz <ilyasmazouz@gmail.com> Co-authored-by: David <hi@davwheat.dev>
2023-02-21 21:14:53 +08:00
"@types/ua-parser-js@^0.7.36":
version "0.7.36"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@types/ua-parser-js/-/ua-parser-js-0.7.36.tgz"
feat: access tokens user management UI (#3587) Signed-off-by: Sami Mazouz <ilyasmazouz@gmail.com> Co-authored-by: David <hi@davwheat.dev>
2023-02-21 21:14:53 +08:00
integrity sha512-N1rW+njavs70y2cApeIw1vLMYXRwfBy+7trgavGuuTfOd7j1Yh7QTRc/yqsPl6ncokt72ZXuxEU0PiCp9bSwNQ==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@types/yargs-parser@*":
version "21.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@types/yargs-parser/-/yargs-parser-21.0.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-iO9ZQHkZxHn4mSakYV0vFHAVDyEOIJQrV2uZ06HxEPcx+mt8swXoZHIbaaJ2crJYFfErySgktuTZ3BeLz+XmFA==
"@types/yargs@^17.0.8":
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
version "17.0.22"
resolved "https://registry.npmjs.org/@types/yargs/-/yargs-17.0.22.tgz"
integrity sha512-pet5WJ9U8yPVRhkwuEIp5ktAeAqRZOq4UdAyWLWzxbtpyXnzbtLdKiXAjJzi/KLmPGS9wk86lUFWZFN6sISo4g==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
"@types/yargs-parser" "*"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@ultraq/array-utils@^2.1.0":
version "2.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@ultraq/array-utils/-/array-utils-2.1.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-TKO1zE6foqs5HG3+QH32yKwJ0zhZrm6J3UmltscveQmxCdbgIPXhNf3A8C9HakjyZDHVRK5pYZOU0tTl28YGFg==
"@ultraq/function-utils@^0.3.0":
version "0.3.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@ultraq/function-utils/-/function-utils-0.3.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-AwFCYorRn0GE34hfgxaCmfnReHqcwWE6QwWPQf/1Zj7k3Zi0FATSJhbtDA+6ayV8p6AnhEntntXaMWMkK17tEQ==
"@ultraq/icu-message-formatter@^0.12.0":
version "0.12.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@ultraq/icu-message-formatter/-/icu-message-formatter-0.12.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-ebd/ZyC1lCVPPrX3AQ9h77NDK4d1nor0Grmv43e97+omWvJB29lbuT+9yM3sq4Ri1QKwTvKG1BUhXBz0oAAR2w==
dependencies:
"@babel/runtime" "^7.11.2"
"@ultraq/array-utils" "^2.1.0"
"@ultraq/function-utils" "^0.3.0"
"@webassemblyjs/ast@1.11.1":
version "1.11.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@webassemblyjs/ast/-/ast-1.11.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-ukBh14qFLjxTQNTXocdyksN5QdM28S1CxHt2rdskFyL+xFV7VremuBLVbmCePj+URalXBENx/9Lm7lnhihtCSw==
dependencies:
"@webassemblyjs/helper-numbers" "1.11.1"
"@webassemblyjs/helper-wasm-bytecode" "1.11.1"
"@webassemblyjs/floating-point-hex-parser@1.11.1":
version "1.11.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@webassemblyjs/floating-point-hex-parser/-/floating-point-hex-parser-1.11.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-iGRfyc5Bq+NnNuX8b5hwBrRjzf0ocrJPI6GWFodBFzmFnyvrQ83SHKhmilCU/8Jv67i4GJZBMhEzltxzcNagtQ==
"@webassemblyjs/helper-api-error@1.11.1":
version "1.11.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@webassemblyjs/helper-api-error/-/helper-api-error-1.11.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-RlhS8CBCXfRUR/cwo2ho9bkheSXG0+NwooXcc3PAILALf2QLdFyj7KGsKRbVc95hZnhnERon4kW/D3SZpp6Tcg==
"@webassemblyjs/helper-buffer@1.11.1":
version "1.11.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@webassemblyjs/helper-buffer/-/helper-buffer-1.11.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-gwikF65aDNeeXa8JxXa2BAk+REjSyhrNC9ZwdT0f8jc4dQQeDQ7G4m0f2QCLPJiMTTO6wfDmRmj/pW0PsUvIcA==
"@webassemblyjs/helper-numbers@1.11.1":
version "1.11.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@webassemblyjs/helper-numbers/-/helper-numbers-1.11.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-vDkbxiB8zfnPdNK9Rajcey5C0w+QJugEglN0of+kmO8l7lDb77AnlKYQF7aarZuCrv+l0UvqL+68gSDr3k9LPQ==
dependencies:
"@webassemblyjs/floating-point-hex-parser" "1.11.1"
"@webassemblyjs/helper-api-error" "1.11.1"
"@xtuc/long" "4.2.2"
"@webassemblyjs/helper-wasm-bytecode@1.11.1":
version "1.11.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@webassemblyjs/helper-wasm-bytecode/-/helper-wasm-bytecode-1.11.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-PvpoOGiJwXeTrSf/qfudJhwlvDQxFgelbMqtq52WWiXC6Xgg1IREdngmPN3bs4RoO83PnL/nFrxucXj1+BX62Q==
"@webassemblyjs/helper-wasm-section@1.11.1":
version "1.11.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@webassemblyjs/helper-wasm-section/-/helper-wasm-section-1.11.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-10P9No29rYX1j7F3EVPX3JvGPQPae+AomuSTPiF9eBQeChHI6iqjMIwR9JmOJXwpnn/oVGDk7I5IlskuMwU/pg==
dependencies:
"@webassemblyjs/ast" "1.11.1"
"@webassemblyjs/helper-buffer" "1.11.1"
"@webassemblyjs/helper-wasm-bytecode" "1.11.1"
"@webassemblyjs/wasm-gen" "1.11.1"
"@webassemblyjs/ieee754@1.11.1":
version "1.11.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@webassemblyjs/ieee754/-/ieee754-1.11.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-hJ87QIPtAMKbFq6CGTkZYJivEwZDbQUgYd3qKSadTNOhVY7p+gfP6Sr0lLRVTaG1JjFj+r3YchoqRYxNH3M0GQ==
dependencies:
"@xtuc/ieee754" "^1.2.0"
"@webassemblyjs/leb128@1.11.1":
version "1.11.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@webassemblyjs/leb128/-/leb128-1.11.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-BJ2P0hNZ0u+Th1YZXJpzW6miwqQUGcIHT1G/sf72gLVD9DZ5AdYTqPNbHZh6K1M5VmKvFXwGSWZADz+qBWxeRw==
dependencies:
"@xtuc/long" "4.2.2"
"@webassemblyjs/utf8@1.11.1":
version "1.11.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@webassemblyjs/utf8/-/utf8-1.11.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-9kqcxAEdMhiwQkHpkNiorZzqpGrodQQ2IGrHHxCy+Ozng0ofyMA0lTqiLkVs1uzTRejX+/O0EOT7KxqVPuXosQ==
"@webassemblyjs/wasm-edit@1.11.1":
version "1.11.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@webassemblyjs/wasm-edit/-/wasm-edit-1.11.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-g+RsupUC1aTHfR8CDgnsVRVZFJqdkFHpsHMfJuWQzWU3tvnLC07UqHICfP+4XyL2tnr1amvl1Sdp06TnYCmVkA==
dependencies:
"@webassemblyjs/ast" "1.11.1"
"@webassemblyjs/helper-buffer" "1.11.1"
"@webassemblyjs/helper-wasm-bytecode" "1.11.1"
"@webassemblyjs/helper-wasm-section" "1.11.1"
"@webassemblyjs/wasm-gen" "1.11.1"
"@webassemblyjs/wasm-opt" "1.11.1"
"@webassemblyjs/wasm-parser" "1.11.1"
"@webassemblyjs/wast-printer" "1.11.1"
"@webassemblyjs/wasm-gen@1.11.1":
version "1.11.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@webassemblyjs/wasm-gen/-/wasm-gen-1.11.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-F7QqKXwwNlMmsulj6+O7r4mmtAlCWfO/0HdgOxSklZfQcDu0TpLiD1mRt/zF25Bk59FIjEuGAIyn5ei4yMfLhA==
dependencies:
"@webassemblyjs/ast" "1.11.1"
"@webassemblyjs/helper-wasm-bytecode" "1.11.1"
"@webassemblyjs/ieee754" "1.11.1"
"@webassemblyjs/leb128" "1.11.1"
"@webassemblyjs/utf8" "1.11.1"
"@webassemblyjs/wasm-opt@1.11.1":
version "1.11.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@webassemblyjs/wasm-opt/-/wasm-opt-1.11.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-VqnkNqnZlU5EB64pp1l7hdm3hmQw7Vgqa0KF/KCNO9sIpI6Fk6brDEiX+iCOYrvMuBWDws0NkTOxYEb85XQHHw==
dependencies:
"@webassemblyjs/ast" "1.11.1"
"@webassemblyjs/helper-buffer" "1.11.1"
"@webassemblyjs/wasm-gen" "1.11.1"
"@webassemblyjs/wasm-parser" "1.11.1"
"@webassemblyjs/wasm-parser@1.11.1":
version "1.11.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@webassemblyjs/wasm-parser/-/wasm-parser-1.11.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-rrBujw+dJu32gYB7/Lup6UhdkPx9S9SnobZzRVL7VcBH9Bt9bCBLEuX/YXOOtBsOZ4NQrRykKhffRWHvigQvOA==
dependencies:
"@webassemblyjs/ast" "1.11.1"
"@webassemblyjs/helper-api-error" "1.11.1"
"@webassemblyjs/helper-wasm-bytecode" "1.11.1"
"@webassemblyjs/ieee754" "1.11.1"
"@webassemblyjs/leb128" "1.11.1"
"@webassemblyjs/utf8" "1.11.1"
"@webassemblyjs/wast-printer@1.11.1":
version "1.11.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@webassemblyjs/wast-printer/-/wast-printer-1.11.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-IQboUWM4eKzWW+N/jij2sRatKMh99QEelo3Eb2q0qXkvPRISAj8Qxtmw5itwqK+TTkBuUIE45AxYPToqPtL5gg==
dependencies:
"@webassemblyjs/ast" "1.11.1"
"@xtuc/long" "4.2.2"
perf(statistics): rewrite for performance on very large communities (#3531) Co-authored-by: Sami Mazouz <ilyasmazouz@gmail.com>
2022-07-19 02:07:38 +08:00
"@webpack-cli/configtest@^1.2.0":
version "1.2.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@webpack-cli/configtest/-/configtest-1.2.0.tgz"
perf(statistics): rewrite for performance on very large communities (#3531) Co-authored-by: Sami Mazouz <ilyasmazouz@gmail.com>
2022-07-19 02:07:38 +08:00
integrity sha512-4FB8Tj6xyVkyqjj1OaTqCjXYULB9FMkqQ8yGrZjRDrYh0nOE+7Lhs45WioWQQMV+ceFlE368Ukhe6xdvJM9Egg==
"@webpack-cli/info@^1.5.0":
version "1.5.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@webpack-cli/info/-/info-1.5.0.tgz"
perf(statistics): rewrite for performance on very large communities (#3531) Co-authored-by: Sami Mazouz <ilyasmazouz@gmail.com>
2022-07-19 02:07:38 +08:00
integrity sha512-e8tSXZpw2hPl2uMJY6fsMswaok5FdlGNRTktvFk2sD8RjH0hE2+XistawJx1vmKteh4NmGmNUrp+Tb2w+udPcQ==
dependencies:
envinfo "^7.7.3"
"@webpack-cli/serve@^1.7.0":
version "1.7.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@webpack-cli/serve/-/serve-1.7.0.tgz"
perf(statistics): rewrite for performance on very large communities (#3531) Co-authored-by: Sami Mazouz <ilyasmazouz@gmail.com>
2022-07-19 02:07:38 +08:00
integrity sha512-oxnCNGj88fL+xzV+dacXs44HcDwf1ovs3AuEzvP7mqXw7fQntqIhQ1BRmynh4qEKQSSSRSWVyXRjmTbZIX9V2Q==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"@xtuc/ieee754@^1.2.0":
version "1.2.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@xtuc/ieee754/-/ieee754-1.2.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-DX8nKgqcGwsc0eJSqYt5lwP4DH5FlHnmuWWBRy7X0NcaGR0ZtuyeESgMwTYVEtxmsNGY+qit4QYT/MIYTOTPeA==
"@xtuc/long@4.2.2":
version "4.2.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/@xtuc/long/-/long-4.2.2.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-NuHqBY1PB/D8xU6s/thBgOAiAP7HOYDQ32+BFZILJ8ivkUkAHQnWfn6WhL79Owj1qmUnoN/YPhktdIoucipkAQ==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
abab@^2.0.6:
version "2.0.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/abab/-/abab-2.0.6.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-j2afSsaIENvHZN2B8GOpF566vZ5WVk5opAiMTvWgaQT8DkbOqsTfvNAvHoRGU2zzP8cPoqys+xHTRDWW8L+/BA==
acorn-globals@^7.0.0:
version "7.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/acorn-globals/-/acorn-globals-7.0.1.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-umOSDSDrfHbTNPuNpC2NSnnA3LUrqpevPb4T9jRx4MagXNS0rs+gwiTcAvqCRmsD6utzsrzNt+ebm00SNWiC3Q==
dependencies:
acorn "^8.1.0"
acorn-walk "^8.0.2"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
acorn-import-assertions@^1.7.6:
version "1.8.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/acorn-import-assertions/-/acorn-import-assertions-1.8.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-m7VZ3jwz4eK6A4Vtt8Ew1/mNbP24u0FhdyfA7fSvnJR6LMdfOYnmuIrrJAgrYfYJ10F/otaHTtrtrtmHdMNzEw==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
acorn-walk@^8.0.0, acorn-walk@^8.0.2:
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "8.2.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/acorn-walk/-/acorn-walk-8.2.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-k+iyHEuPgSw6SbuDpGQM+06HQUa04DZ3o+F6CSzXMvvI5KMvnaEqXe+YVe555R9nn6GPt404fos4wcgpw12SDA==
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
acorn@^8, acorn@^8.0.4, acorn@^8.1.0, acorn@^8.5.0, acorn@^8.7.1, acorn@^8.8.1:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "8.8.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/acorn/-/acorn-8.8.1.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-7zFpHzhnqYKrkYdUjF1HI1bzd0VygEGX8lFk4k5zVMqHEoES+P+7TKI+EvLO9WVMJ8eekdO0aDEK044xTXwPPA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
agent-base@6:
version "6.0.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/agent-base/-/agent-base-6.0.2.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-RZNwNclF7+MS/8bDg70amg32dyeZGZxiDuQmZxKLAlQjr3jGyLx+4Kkk58UO7D2QdgFIQCovuSuZESne6RG6XQ==
dependencies:
debug "4"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
ajv-keywords@^3.5.2:
version "3.5.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/ajv-keywords/-/ajv-keywords-3.5.2.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-5p6WTN0DdTGVQk6VjcEju19IgaHudalcfabD7yhDGeA6bcQnmL+CpveLJq/3hvfwd1aof6L386Ougkx6RfyMIQ==
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
ajv@^6.12.4, ajv@^6.12.5, ajv@^6.9.1:
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "6.12.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/ajv/-/ajv-6.12.6.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-j3fVLgvTo527anyYyJOGTYJbG+vnnQYvE0m5mmkc1TK+nxAppkCLMIL0aZ4dblVCNoGShhm+kzE4ZUykBoMg4g==
dependencies:
fast-deep-equal "^3.1.1"
fast-json-stable-stringify "^2.0.0"
json-schema-traverse "^0.4.1"
uri-js "^4.2.2"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
ansi-escapes@^4.2.1:
version "4.3.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/ansi-escapes/-/ansi-escapes-4.3.2.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-gKXj5ALrKWQLsYG9jlTRmR/xKluxHV+Z9QEwNIgCfM1/uwPMCuzVVnh5mwTd+OuBZcwSIMbqssNWRm1lE51QaQ==
dependencies:
type-fest "^0.21.3"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
ansi-regex@^5.0.1:
version "5.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==
ansi-styles@^3.2.1:
version "3.2.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/ansi-styles/-/ansi-styles-3.2.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-VT0ZI6kZRdTh8YyJw3SMbYm/u+NqfsAxEpWO0Pf9sq8/e94WxxOpPKx9FR1FlyCtOVDNOQ+8ntlqFxiRc+r5qA==
dependencies:
color-convert "^1.9.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
ansi-styles@^4.0.0, ansi-styles@^4.1.0:
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "4.3.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/ansi-styles/-/ansi-styles-4.3.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==
dependencies:
color-convert "^2.0.1"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
ansi-styles@^5.0.0:
version "5.2.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/ansi-styles/-/ansi-styles-5.2.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-Cxwpt2SfTzTtXcfOlzGEee8O+c+MmUgGrNiBcXnuWxuFJHe6a5Hz7qwhwe5OgaSYI0IJvkLqWX1ASG+cJOkEiA==
anymatch@^3.0.3:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
version "3.1.3"
resolved "https://registry.npmjs.org/anymatch/-/anymatch-3.1.3.tgz"
integrity sha512-KMReFUr0B4t+D+OBkjR3KYqvocp2XaSzO55UcB6mgQMd3KbcE+mWTyvVV7D/zsdEbNnV6acZUutkiHQXvTr1Rw==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
normalize-path "^3.0.0"
picomatch "^2.0.4"
argparse@^1.0.7:
version "1.0.10"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/argparse/-/argparse-1.0.10.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-o5Roy6tNG4SL/FOkCAN6RzjiakZS25RLYFrcMttJqbdd8BWrnA+fGz57iN5Pb06pvBGvl5gQ0B48dJlslXvoTg==
dependencies:
sprintf-js "~1.0.2"
argparse@^2.0.1:
version "2.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/argparse/-/argparse-2.0.1.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-8+9WqebbFzpX9OR+Wa6O29asIogeRMzcGtAINdpMHHyAg10f05aSFVBbcEqGf/PXw1EjAZ+q2/bEBg3DvurK3Q==
asynckit@^0.4.0:
version "0.4.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/asynckit/-/asynckit-0.4.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-Oei9OH4tRh0YqU3GxhX79dM/mwVgvbZJaSNaRk+bshkj0S5cfHcgYakreBjrHwatXKbz+IoIdYLxrKim2MjW0Q==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
axios@^0.24.0:
version "0.24.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/axios/-/axios-0.24.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-Q6cWsys88HoPgAaFAVUb0WpPk0O8iTeisR9IMqy9G8AbO4NlpVknrnQS03zzF9PGAWgO3cgletO3VjV/P7VztA==
dependencies:
follow-redirects "^1.14.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
babel-jest@^29.0.0, babel-jest@^29.5.0:
version "29.5.0"
resolved "https://registry.npmjs.org/babel-jest/-/babel-jest-29.5.0.tgz"
integrity sha512-mA4eCDh5mSo2EcA9xQjVTpmbbNk32Zb3Q3QFQsNhaK56Q+yoXowzFodLux30HRgyOho5rsQ6B0P9QpMkvvnJ0Q==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/transform" "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@types/babel__core" "^7.1.14"
babel-plugin-istanbul "^6.1.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
babel-preset-jest "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
chalk "^4.0.0"
graceful-fs "^4.2.9"
slash "^3.0.0"
fix: Assorted Typing Fixes (#3348) With all the commits below, we resolve all outstanding typing issues in the repo, and CI jobs run green. * fix: Convert DashboardPage and DashboardWidget to TypeScript * fix: fix type errors in package manager ext * fix: Convert Post component to TypeScript * fix: avatar typings should accept null user * fix: convert Notification component to TypeScript * fix: properly use `typeof` in ForumApplication * feat: make Notification content attr generic * chore: format Notification component * fix: Convert DiscussionRenamedNotification to TypeScript * fix(pusher) move shims to a location where they get applied * fix(pusher): fix some typing errors * fix(akismet): fix some typing issues * chore: update core dist typings * chore(pusher): format * fix: anchorScroll should accept string selectors * fix: more accurately represent ApiQueryParamsPlural * fix: convert PostStreamState to TypeScript * chore(core): rebuild typings * feat: allow extending app.routes * fix: more flexible typings for highlight.ts * fix: use primitive `number` type for Discussion typings * fix: convert DiscussionListItem to TypeScript * chore: rebuild core typings * fix: final pusher type fixes * feat: start tags TypeScript conversion * fix: require-dev tags in pusher for CI TypeScript purposes. * chore(core): format * chore(tags): build dist typings * feat(pusher): use dist types from tags. * feat: convert flags to TypeScript * chore(flags): generate dist typings * fix(akismet): last type errors * chore: update .yarn-integrity * chore: partially run flarum-cli audit infra --fix The tsconfig changes from that command are ignored, since we don't yet support "replacable sections" that would let us add custom config. * chore: use type imports * fix: broader gitattributes * chore: run flarum-cli audit infra --monorepo --fix * feat: make `app.data` typings extensible * chore(core): format * chore: boost tags TypeScript coverage * fix(tags): further increase type coverage.
2022-03-23 23:43:14 +08:00
babel-loader@^8.2.3:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "8.3.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/babel-loader/-/babel-loader-8.3.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-H8SvsMF+m9t15HNLMipppzkC+Y2Yq+v3SonZyU70RBL/h1gxPkH08Ot8pEE9Z4Kd+czyWJClmFS8qzIP9OZ04Q==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
find-cache-dir "^3.3.1"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
loader-utils "^2.0.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
make-dir "^3.1.0"
schema-utils "^2.6.5"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
babel-plugin-istanbul@^6.1.1:
version "6.1.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/babel-plugin-istanbul/-/babel-plugin-istanbul-6.1.1.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-Y1IQok9821cC9onCx5otgFfRm7Lm+I+wwxOx738M/WLPZ9Q42m4IG5W0FNX8WLL2gYMZo3JkuXIH2DOpWM+qwA==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@istanbuljs/load-nyc-config" "^1.0.0"
"@istanbuljs/schema" "^0.1.2"
istanbul-lib-instrument "^5.0.4"
test-exclude "^6.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
babel-plugin-jest-hoist@^29.5.0:
version "29.5.0"
resolved "https://registry.npmjs.org/babel-plugin-jest-hoist/-/babel-plugin-jest-hoist-29.5.0.tgz"
integrity sha512-zSuuuAlTMT4mzLj2nPnUm6fsE6270vdOfnpbJ+RmruU75UhLFvL0N2NgI7xpeS7NaB6hGqmd5pVpGTDYvi4Q3w==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
"@babel/template" "^7.3.3"
"@babel/types" "^7.3.3"
"@types/babel__core" "^7.1.14"
"@types/babel__traverse" "^7.0.6"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
babel-plugin-polyfill-corejs2@^0.3.3:
version "0.3.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/babel-plugin-polyfill-corejs2/-/babel-plugin-polyfill-corejs2-0.3.3.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-8hOdmFYFSZhqg2C/JgLUQ+t52o5nirNwaWM2B9LWteozwIvM14VSwdsCAUET10qT+kmySAlseadmfeeSWFCy+Q==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/compat-data" "^7.17.7"
"@babel/helper-define-polyfill-provider" "^0.3.3"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
semver "^6.1.1"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
babel-plugin-polyfill-corejs3@^0.6.0:
version "0.6.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/babel-plugin-polyfill-corejs3/-/babel-plugin-polyfill-corejs3-0.6.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-+eHqR6OPcBhJOGgsIar7xoAB1GcSwVUA3XjAd7HJNzOXT4wv6/H7KIdA/Nc60cvUlDbKApmqNvD1B1bzOt4nyA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-define-polyfill-provider" "^0.3.3"
core-js-compat "^3.25.1"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
babel-plugin-polyfill-regenerator@^0.4.1:
version "0.4.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/babel-plugin-polyfill-regenerator/-/babel-plugin-polyfill-regenerator-0.4.1.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-NtQGmyQDXjQqQ+IzRkBVwEOz9lQ4zxAQZgoAYEtU9dJjnl1Oc98qnN7jcp+bE7O7aYzVpavXE3/VKXNzUbh7aw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@babel/helper-define-polyfill-provider" "^0.3.3"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
babel-preset-current-node-syntax@^1.0.0:
version "1.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/babel-preset-current-node-syntax/-/babel-preset-current-node-syntax-1.0.1.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-M7LQ0bxarkxQoN+vz5aJPsLBn77n8QgTFmo8WK0/44auK2xlCXrYcUxHFxgU7qW5Yzw/CjmLRK2uJzaCd7LvqQ==
dependencies:
"@babel/plugin-syntax-async-generators" "^7.8.4"
"@babel/plugin-syntax-bigint" "^7.8.3"
"@babel/plugin-syntax-class-properties" "^7.8.3"
"@babel/plugin-syntax-import-meta" "^7.8.3"
"@babel/plugin-syntax-json-strings" "^7.8.3"
"@babel/plugin-syntax-logical-assignment-operators" "^7.8.3"
"@babel/plugin-syntax-nullish-coalescing-operator" "^7.8.3"
"@babel/plugin-syntax-numeric-separator" "^7.8.3"
"@babel/plugin-syntax-object-rest-spread" "^7.8.3"
"@babel/plugin-syntax-optional-catch-binding" "^7.8.3"
"@babel/plugin-syntax-optional-chaining" "^7.8.3"
"@babel/plugin-syntax-top-level-await" "^7.8.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
babel-preset-jest@^29.5.0:
version "29.5.0"
resolved "https://registry.npmjs.org/babel-preset-jest/-/babel-preset-jest-29.5.0.tgz"
integrity sha512-JOMloxOqdiBSxMAzjRaH023/vvcaSaec49zvg+2LmNsktC7ei39LTJGw02J+9uUtTZUq6xbLyJ4dxe9sSmIuAg==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
babel-plugin-jest-hoist "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
babel-preset-current-node-syntax "^1.0.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
balanced-match@^1.0.0:
version "1.0.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/balanced-match/-/balanced-match-1.0.2.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-3oSeUO0TMV67hN1AmbXsK4yaqU7tjiHlbxRDZOpH0KW9+CeX4bRAaX0Anxt0tx2MrpRpWwQaPwIlISEJhYU5Pw==
big.js@^5.2.2:
version "5.2.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/big.js/-/big.js-5.2.2.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-vyL2OymJxmarO8gxMr0mhChsO9QGwhynfuu4+MHTAW6czfq9humCB7rKpUjDd9YUiDPU4mzpyupFSvOClAwbmQ==
feat(modals): support stacking modals, remove bootstrap modals dependency (#3456) * Feature: Stackable modals * Processed feedback * fix: use position in modal stack rather than key for modal number * fix: use correct base z-index * chore: simplify `className` to `class` * chore: add `key` attribute to ModalManager element * fix: backdrop flashing as modals are stacked/unstacked * chore: simplify modal close process * docs: add TS overload to indicate deprecated modal opening syntax Require explicit values for `attrs` and `stackModal` from Flarum 2.0, beginning deprecation from now. * feat: use stackable modal for forgot password modal above sign in * chore: explicitly check if modal is open before trying to focus trap * fix(a11y): add missing `aria-hidden` on main content when modal open * fix(a11y): add missing `aria-modal` on modal * chore: remove test code * chore: remove dead CSS * chore: remove overload * fix: lock page scrolling when modal is open * fix: strange scrolling behaviour * chore: convert to JSX * fix: event listener memory leak * chore: remove unneeded optional chaining * fix: incorrect return types * chore: rewrite backdrop system - use one backdrop for all modals * docs: typos in comment block * fix: show backdrop directly below top-most modal Co-authored-by: Sami Mazouz <sychocouldy@gmail.com> * chore: format * fix: use an invisible backdrop for each modal to exit Signed-off-by: Sami Mazouz <ilyasmazouz@gmail.com> * chore: remove debugging code Signed-off-by: Sami Mazouz <ilyasmazouz@gmail.com> * chore: remove forgotten debug code Co-authored-by: David Wheatley <david@davwheat.dev> Co-authored-by: Sami Mazouz <sychocouldy@gmail.com>
2022-08-08 20:29:14 +08:00
body-scroll-lock@^4.0.0-beta.0:
version "4.0.0-beta.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/body-scroll-lock/-/body-scroll-lock-4.0.0-beta.0.tgz"
feat(modals): support stacking modals, remove bootstrap modals dependency (#3456) * Feature: Stackable modals * Processed feedback * fix: use position in modal stack rather than key for modal number * fix: use correct base z-index * chore: simplify `className` to `class` * chore: add `key` attribute to ModalManager element * fix: backdrop flashing as modals are stacked/unstacked * chore: simplify modal close process * docs: add TS overload to indicate deprecated modal opening syntax Require explicit values for `attrs` and `stackModal` from Flarum 2.0, beginning deprecation from now. * feat: use stackable modal for forgot password modal above sign in * chore: explicitly check if modal is open before trying to focus trap * fix(a11y): add missing `aria-hidden` on main content when modal open * fix(a11y): add missing `aria-modal` on modal * chore: remove test code * chore: remove dead CSS * chore: remove overload * fix: lock page scrolling when modal is open * fix: strange scrolling behaviour * chore: convert to JSX * fix: event listener memory leak * chore: remove unneeded optional chaining * fix: incorrect return types * chore: rewrite backdrop system - use one backdrop for all modals * docs: typos in comment block * fix: show backdrop directly below top-most modal Co-authored-by: Sami Mazouz <sychocouldy@gmail.com> * chore: format * fix: use an invisible backdrop for each modal to exit Signed-off-by: Sami Mazouz <ilyasmazouz@gmail.com> * chore: remove debugging code Signed-off-by: Sami Mazouz <ilyasmazouz@gmail.com> * chore: remove forgotten debug code Co-authored-by: David Wheatley <david@davwheat.dev> Co-authored-by: Sami Mazouz <sychocouldy@gmail.com>
2022-08-08 20:29:14 +08:00
integrity sha512-a7tP5+0Mw3YlUJcGAKUqIBkYYGlYxk2fnCasq/FUph1hadxlTRjF+gAcZksxANnaMnALjxEddmSi/H3OR8ugcQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
bootstrap@^3.4.1:
version "3.4.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/bootstrap/-/bootstrap-3.4.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-yN5oZVmRCwe5aKwzRj6736nSmKDX7pLYwsXiCj/EYmo16hODaBiT4En5btW/jhBF/seV+XMx3aYwukYC3A49DA==
brace-expansion@^1.1.7:
version "1.1.11"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==
dependencies:
balanced-match "^1.0.0"
concat-map "0.0.1"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
brace-expansion@^2.0.1:
version "2.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/brace-expansion/-/brace-expansion-2.0.1.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-XnAIvQ8eM+kC6aULx6wuQiwVsnzsi9d3WxzV3FpWTGA19F621kwdbsAcFKXgKUHZWsy+mY6iL1sHTxWEFCytDA==
dependencies:
balanced-match "^1.0.0"
braces@^3.0.2:
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "3.0.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/braces/-/braces-3.0.2.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-b8um+L1RzM3WDSzvhm6gIz1yfTbBt6YTlcEKAvsmqCZZFw46z626lVj9j1yEPW33H5H+lBQpZMP1k8l+78Ha0A==
dependencies:
fill-range "^7.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
browserslist@^4.14.5, browserslist@^4.21.3, browserslist@^4.21.4, "browserslist@>= 4.21.0":
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "4.21.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/browserslist/-/browserslist-4.21.4.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-CBHJJdDmgjl3daYjN5Cp5kbTf1mUhZoS+beLklHIvkOWscs83YAhLlF3Wsh/lciQYAcbBJgTOD44VtG31ZM4Hw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
caniuse-lite "^1.0.30001400"
electron-to-chromium "^1.4.251"
node-releases "^2.0.6"
update-browserslist-db "^1.0.9"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
bs-logger@0.x:
version "0.2.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/bs-logger/-/bs-logger-0.2.6.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-pd8DCoxmbgc7hyPKOvxtqNcjYoOsABPQdcCUjGp3d42VR2CX1ORhk2A87oqqu5R1kk+76nsxZupkmyd+MVtCog==
dependencies:
fast-json-stable-stringify "2.x"
bser@2.1.1:
version "2.1.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/bser/-/bser-2.1.1.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-gQxTNE/GAfIIrmHLUE3oJyp5FO6HRBfhjnw4/wMmA63ZGDJnWBmgY/lyQBpnDUkGmAhbSe39tx2d/iTOAfglwQ==
dependencies:
node-int64 "^0.4.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
buffer-from@^1.0.0:
version "1.1.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/buffer-from/-/buffer-from-1.1.2.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-E+XQCRwSbaaiChtv6k6Dwgc+bx+Bs6vuKJHHl5kox/BaKbhiXzqQOwK4cO22yElGp2OCmjwVhT3HmxgyPGnJfQ==
bundlewatch@^0.3.2:
version "0.3.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/bundlewatch/-/bundlewatch-0.3.3.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-qzSVWrZyyWXa546JpAPRPTFmnXms9YNVnfzB05DRJKmN6wRRa7SkxE4OgKQmbAY74Z6CM2mKAc6vwvd2R+1lUQ==
dependencies:
axios "^0.24.0"
bytes "^3.1.1"
chalk "^4.0.0"
ci-env "^1.17.0"
commander "^5.0.0"
glob "^7.1.2"
gzip-size "^6.0.0"
jsonpack "^1.1.5"
lodash.merge "^4.6.1"
read-pkg-up "^7.0.1"
bytes@^3.1.1:
version "3.1.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/bytes/-/bytes-3.1.2.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-/Nf7TyzTx6S3yRJObOAV7956r8cr2+Oj8AC5dt8wSP3BQAoeX58NoHyCU8P8zGkNXStjTSi6fzO6F0pBdcYbEg==
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
call-bind@^1.0.2:
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "1.0.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/call-bind/-/call-bind-1.0.2.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-7O+FbCihrB5WGbFYesctwmTKae6rOiIzmz1icreWJ+0aA7LJfuqhEso2T9ncpcFtzMQtzXf2QGGueWJGTYsqrA==
dependencies:
function-bind "^1.1.1"
get-intrinsic "^1.0.2"
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
callsites@^3.0.0:
version "3.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/callsites/-/callsites-3.1.0.tgz"
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
integrity sha512-P8BjAsXvZS+VIDUI11hHCQEv74YT67YUi5JJFNWIqL235sBmjX4+qx9Muvls5ivyNENctx46xQLQ3aTuE7ssaQ==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
camelcase@^5.3.1:
version "5.3.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/camelcase/-/camelcase-5.3.1.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-L28STB170nwWS63UjtlEOE3dldQApaJXZkOI1uMFfzf3rRuPegHaHesyee+YxQ+W6SvRDQV6UrdOdRiR153wJg==
camelcase@^6.2.0:
version "6.3.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/camelcase/-/camelcase-6.3.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-Gmy6FhYlCY7uOElZUSbxo2UCDH8owEk996gkbrpsgGtrJLM3J7jGxl9Ic7Qwwj4ivOE5AWZWRMecDdF7hqGjFA==
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
caniuse-lite@^1.0.30001400:
feat(jest): mithril component testing (#3679) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * feat(jest): mithril component testing * fix: use separate `tsconfig.test.json` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-11 06:02:50 +08:00
version "1.0.30001431"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30001431.tgz"
feat(jest): mithril component testing (#3679) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * feat(jest): mithril component testing * fix: use separate `tsconfig.test.json` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-11 06:02:50 +08:00
integrity sha512-zBUoFU0ZcxpvSt9IU66dXVT/3ctO1cy4y9cscs1szkPlcWb6pasYM144GqrUygUbT+k7cmUCW61cvskjcv0enQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
chalk@^2.0.0:
version "2.4.2"
resolved "https://registry.npmjs.org/chalk/-/chalk-2.4.2.tgz"
integrity sha512-Mti+f9lpJNcwF4tWV8/OrTTtF1gZi+f8FqlyAdouralcFWFQWF2+NgCHShjkCb+IFBLq9buZwE1xckQU4peSuQ==
dependencies:
ansi-styles "^3.2.1"
escape-string-regexp "^1.0.5"
supports-color "^5.3.0"
chalk@^2.4.2:
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "2.4.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/chalk/-/chalk-2.4.2.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-Mti+f9lpJNcwF4tWV8/OrTTtF1gZi+f8FqlyAdouralcFWFQWF2+NgCHShjkCb+IFBLq9buZwE1xckQU4peSuQ==
dependencies:
ansi-styles "^3.2.1"
escape-string-regexp "^1.0.5"
supports-color "^5.3.0"
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
chalk@^4.0.0, chalk@^4.1.0, chalk@^4.1.2:
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "4.1.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/chalk/-/chalk-4.1.2.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-oKnbhFyRIXpUuez8iBMmyEa4nbj4IOQyuhc/wy9kY7/WVPcwIO9VA668Pu8RkO7+0G76SLROeyw9CpQ061i4mA==
dependencies:
ansi-styles "^4.1.0"
supports-color "^7.1.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
char-regex@^1.0.2:
version "1.0.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/char-regex/-/char-regex-1.0.2.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-kWWXztvZ5SBQV+eRgKFeh8q5sLuZY2+8WUIzlxWVTg+oGwY14qylx1KbKzHd8P6ZYkAg0xyIDU9JMHhyJMZ1jw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chrome-trace-event@^1.0.2:
version "1.0.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/chrome-trace-event/-/chrome-trace-event-1.0.3.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-p3KULyQg4S7NIHixdwbGX+nFHkoBiA4YQmyWtjb8XngSKV124nJmRysgAeujbUVb15vh+RvFUfCPqU7rXk+hZg==
ci-env@^1.17.0:
version "1.17.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/ci-env/-/ci-env-1.17.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-NtTjhgSEqv4Aj90TUYHQLxHdnCPXnjdtuGG1X8lTfp/JqeXTdw0FTWl/vUAPuvbWZTF8QVpv6ASe/XacE+7R2A==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
ci-info@^3.2.0:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
version "3.8.0"
resolved "https://registry.npmjs.org/ci-info/-/ci-info-3.8.0.tgz"
integrity sha512-eXTggHWSooYhq49F2opQhuHWgzucfF2YgODK4e1566GQs5BIfP30B0oenwBJHfWxAs2fyPB1s7Mg949zLf61Yw==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
cjs-module-lexer@^1.0.0:
version "1.2.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/cjs-module-lexer/-/cjs-module-lexer-1.2.2.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-cOU9usZw8/dXIXKtwa8pM0OTJQuJkxMN6w30csNRUerHfeQ5R6U3kkU/FtJeIf3M202OHfY2U8ccInBG7/xogA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
classnames@^2.2.6:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "2.3.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/classnames/-/classnames-2.3.2.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-CSbhY4cFEJRe6/GQzIk5qXZ4Jeg5pcsP7b5peFSDpffpe1cqjASH/n9UTjBwOp6XpMSTwQ8Za2K5V02ueA7Tmw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
cli-table3@^0.6.1:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "0.6.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/cli-table3/-/cli-table3-0.6.3.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-w5Jac5SykAeZJKntOxJCrm63Eg5/4dhMWIcuTbo9rpE+brgaSZo0RuNJZeOyMgsUdhDeojvgyQLmjI+K50ZGyg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
string-width "^4.2.0"
optionalDependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@colors/colors" "1.5.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
cliui@^8.0.1:
version "8.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/cliui/-/cliui-8.0.1.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-BSeNnyus75C4//NQ9gQt1/csTXyo/8Sb+afLAkzAptFuMsod9HFokGNudZpi/oQV73hnVK+sR+5PVRMd+Dr7YQ==
dependencies:
string-width "^4.2.0"
strip-ansi "^6.0.1"
wrap-ansi "^7.0.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
clone-deep@^4.0.1:
version "4.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/clone-deep/-/clone-deep-4.0.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-neHB9xuzh/wk0dIHweyAXv2aPGZIVk3pLMe+/RNzINf17fe0OG96QroktYAUm7SM1PBnzTabaLboqqxDyMU+SQ==
dependencies:
is-plain-object "^2.0.4"
kind-of "^6.0.2"
shallow-clone "^3.0.0"
clsx@^1.1.1:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "1.2.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/clsx/-/clsx-1.2.1.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-EcR6r5a8bj6pu3ycsa/E/cKVGuTgZJZdsyUYHOksG/UHIiKfjxzRxYJpyVBwYaQeOvghal9fcc4PidlgzugAQg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
co@^4.6.0:
version "4.6.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/co/-/co-4.6.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-QVb0dM5HvG+uaxitm8wONl7jltx8dqhfU33DcqtOZcLSVIKSDDLDi7+0LbAKiyI8hD9u42m2YxXSkMGWThaecQ==
collect-v8-coverage@^1.0.0:
version "1.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/collect-v8-coverage/-/collect-v8-coverage-1.0.1.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-iBPtljfCNcTKNAto0KEtDfZ3qzjJvqE3aTGZsbhjSBlorqpXJlaWWtPO35D+ZImoC3KWejX64o+yPGxhWSTzfg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
color-convert@^1.9.0:
version "1.9.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/color-convert/-/color-convert-1.9.3.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-QfAUtd+vFdAtFQcC8CCyYt1fYWxSqAiK2cSD6zDB8N3cpsEBAvRxp9zOGg6G/SHHJYAT88/az/IuDGALsNVbGg==
dependencies:
color-name "1.1.3"
color-convert@^2.0.1:
version "2.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/color-convert/-/color-convert-2.0.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ==
dependencies:
color-name "~1.1.4"
color-name@~1.1.4:
version "1.1.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/color-name/-/color-name-1.1.4.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA==
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
color-name@1.1.3:
version "1.1.3"
resolved "https://registry.npmjs.org/color-name/-/color-name-1.1.3.tgz"
integrity sha512-72fSenhMw2HZMTVHeCA9KCmpEIbzWiQsjN+BHcBbS9vr1mtt+vJjPdksIBNUmKAW8TFUDPJK5SUU3QhE9NEXDw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
color-thief-browser@^2.0.2:
version "2.0.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/color-thief-browser/-/color-thief-browser-2.0.2.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-dXHq3ytLWEN7Nbu+oZAbtBP/TRd3uNT1Ll38idklwgr8Cng3XGI7bzMz6xWYID+zPd7AupdHpyNYVacQ8uhK0w==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
colorette@^2.0.14:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "2.0.19"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/colorette/-/colorette-2.0.19.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-3tlv/dIP7FWvj3BsbHrGLJ6l/oKh1O3TcgBqMn+yyCagOxc23fyzDS6HypQbgxWbkpDnf52p1LuR4eWDQ/K9WQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
combined-stream@^1.0.8:
version "1.0.8"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/combined-stream/-/combined-stream-1.0.8.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-FQN4MRfuJeHf7cBbBMJFXhKSDq+2kAArBlmRBvcvFE5BB1HZKXtSFASDhdlz9zOYwxh8lDdnvmMOe/+5cdoEdg==
dependencies:
delayed-stream "~1.0.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
commander@^2.20.0:
version "2.20.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/commander/-/commander-2.20.3.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-GpVkmM8vF2vQUkj2LvZmD35JxeJOLCwJ9cUkugyk2nuhbv3+mJvpLYYt+0+USMxE+oj+ey/lJEnhZw75x/OMcQ==
feat(jest): mithril component testing (#3679) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * feat(jest): mithril component testing * fix: use separate `tsconfig.test.json` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-11 06:02:50 +08:00
commander@^3.0.2:
version "3.0.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/commander/-/commander-3.0.2.tgz"
feat(jest): mithril component testing (#3679) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * feat(jest): mithril component testing * fix: use separate `tsconfig.test.json` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-11 06:02:50 +08:00
integrity sha512-Gar0ASD4BDyKC4hl4DwHqDrmvjoxWKZigVnAbn5H1owvm4CxCPdb0HQDehwNYMJpla5+M2tPmPARzhtYuwpHow==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
commander@^5.0.0:
version "5.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/commander/-/commander-5.1.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-P0CysNDQ7rtVw4QIQtm+MRxV66vKFSvlsQvGYXZWR3qFU0jlMKHZZZgw8e+8DSah4UDKMqnknRDQz+xuQXQ/Zg==
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
commander@^7.0.0:
version "7.2.0"
resolved "https://registry.npmjs.org/commander/-/commander-7.2.0.tgz"
integrity sha512-QrWXB+ZQSVPmIWIhtEO9H+gwHaMGYiF5ChvoJ+K9ZGHG/sVsa6yiesAD1GC/x46sET00Xlwo1u49RVVVzvcSkw==
commander@^7.2.0:
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "7.2.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/commander/-/commander-7.2.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-QrWXB+ZQSVPmIWIhtEO9H+gwHaMGYiF5ChvoJ+K9ZGHG/sVsa6yiesAD1GC/x46sET00Xlwo1u49RVVVzvcSkw==
commondir@^1.0.1:
version "1.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/commondir/-/commondir-1.0.1.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-W9pAhw0ja1Edb5GVdIF1mjZw/ASI0AlShXM83UUGe2DVr5TdAPEA1OA8m/g8zWp9x6On7gqufY+FatDbC3MDQg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
concat-map@0.0.1:
version "0.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-/Srv4dswyQNBfohGpz9o6Yb3Gz3SrUDqBH5rTuhGR7ahtlbYKnVxw2bCFMRljaA7EXHaXZ8wsHdodFvbkhKmqg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
convert-source-map@^1.6.0, convert-source-map@^1.7.0:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "1.9.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/convert-source-map/-/convert-source-map-1.9.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-ASFBup0Mz1uyiIjANan1jzLQami9z1PoYSZCiiYW2FczPbenXc45FZdBZLzOT+r6+iciuEModtmCti+hjaAk0A==
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
convert-source-map@^2.0.0:
version "2.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/convert-source-map/-/convert-source-map-2.0.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-Kvp459HrV2FEJ1CAsi1Ku+MY3kasH19TFykTz2xWmMeq6bk2NU3XXvfJ+Q61m0xktWwt+1HSYf3JZsTms3aRJg==
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
core-js-compat@^3.25.1:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
version "3.26.1"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
browserslist "^4.21.4"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
cosmiconfig@^7.0.1:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
version "7.1.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
"@types/parse-json" "^4.0.0"
import-fresh "^3.2.1"
parse-json "^5.0.0"
path-type "^4.0.0"
yaml "^1.10.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
cross-env@^7.0.3:
version "7.0.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/cross-env/-/cross-env-7.0.3.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-+/HKd6EgcQCJGh2PSjZuUitQBQynKor4wrFbRg4DtAgS1aWO+gU52xpH7M9ScGgXSYmAVS9bIJ8EzuaGw0oNAw==
dependencies:
cross-spawn "^7.0.1"
cross-spawn@^7.0.1, cross-spawn@^7.0.3:
version "7.0.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/cross-spawn/-/cross-spawn-7.0.3.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-iRDPJKUPVEND7dHPO8rkbOnPpyDygcDFtWjpeWNCgy8WP2rXcxXL8TskReQl6OrB2G7+UJrags1q15Fudc7G6w==
dependencies:
path-key "^3.1.0"
shebang-command "^2.0.0"
which "^2.0.1"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
cssom@^0.5.0:
version "0.5.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/cssom/-/cssom-0.5.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-iKuQcq+NdHqlAcwUY0o/HL69XQrUaQdMjmStJ8JFmUaiiQErlhrmuigkg/CU4E2J0IyUKUrMAgl36TvN67MqTw==
cssom@~0.3.6:
version "0.3.8"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/cssom/-/cssom-0.3.8.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-b0tGHbfegbhPJpxpiBPU2sCkigAqtM9O121le6bbOlgyV+NyGyCmVfJ6QW9eRjz8CpNfWEOYBIMIGRYkLwsIYg==
cssstyle@^2.3.0:
version "2.3.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/cssstyle/-/cssstyle-2.3.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-AZL67abkUzIuvcHqk7c09cezpGNcxUxU4Ioi/05xHk4DQeTkWmGYftIE6ctU6AEt+Gn4n1lDStOtj7FKycP71A==
dependencies:
cssom "~0.3.6"
data-urls@^3.0.2:
version "3.0.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/data-urls/-/data-urls-3.0.2.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-Jy/tj3ldjZJo63sVAvg6LHt2mHvl4V6AgRAmNDtLdm7faqtsx+aJG42rsyCo9JCoRVKwPFzKlIPx3DIibwSIaQ==
dependencies:
abab "^2.0.6"
whatwg-mimetype "^3.0.0"
whatwg-url "^11.0.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dayjs@^1.10.4, dayjs@^1.10.7:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "1.11.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/dayjs/-/dayjs-1.11.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-zZbY5giJAinCG+7AGaw0wIhNZ6J8AhWuSXKvuc1KAyMiRsvGQWqh4L+MomvhdAYjN+lqvVCMq1I41e3YHvXkyQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
debug@^4.1.0, debug@^4.1.1, debug@4:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "4.3.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/debug/-/debug-4.3.4.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-PRWFHuSU3eDtQJPvnNY7Jcket1j0t5OuOsFzPPzsekD52Zl8qUfFIPEiswXqIvHWGVHOgX+7G/vCNNhehwxfkQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
ms "2.1.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
decimal.js@^10.4.2:
version "10.4.3"
resolved "https://registry.npmjs.org/decimal.js/-/decimal.js-10.4.3.tgz"
integrity sha512-VBBaLc1MgL5XpzgIP7ny5Z6Nx3UrRkIViUkPUdtl9aya5amy3De1gsUUSB1g3+3sExYNjCAsAznmukyxCb1GRA==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dedent@^0.7.0:
version "0.7.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/dedent/-/dedent-0.7.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-Q6fKUPqnAHAyhiUgFU7BUzLiv0kd8saH9al7tnu5Q/okj6dnupxyTgFIBjVzJATdfIAm9NAsvXNzjaKa+bxVyA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
deep-equal@^1.1.1:
version "1.1.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/deep-equal/-/deep-equal-1.1.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-yd9c5AdiqVcR+JjcwUQb9DkhJc8ngNr0MahEBGvDiJw8puWab2yZlh+nkasOnZP+EGTAP6rRp2JzJhJZzvNF8g==
dependencies:
is-arguments "^1.0.4"
is-date-object "^1.0.1"
is-regex "^1.0.4"
object-is "^1.0.1"
object-keys "^1.1.1"
regexp.prototype.flags "^1.2.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
deep-is@~0.1.3:
version "0.1.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/deep-is/-/deep-is-0.1.4.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-oIPzksmTg4/MriiaYGO+okXDT7ztn/w3Eptv/+gSIdMdKsJo0u4CfYNFJPy+4SKMuCqGw2wxnA+URMg3t8a/bQ==
deepmerge@^4.2.2:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
version "4.3.1"
resolved "https://registry.npmjs.org/deepmerge/-/deepmerge-4.3.1.tgz"
integrity sha512-3sUqbMEc77XqpdNO7FRyRog+eW3ph+GYCbj+rK+uYyRMuwsVy0rMiVtPn+QJlKFvWP/1PYpapqYn0Me2knFn+A==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
define-properties@^1.1.3:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "1.1.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/define-properties/-/define-properties-1.1.4.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-uckOqKcfaVvtBdsVkdPv3XjveQJsNQqmhXgRi8uhvWWuPYZCNlzT8qAyblUgNoXdHdjMTzAqeGjAoli8f+bzPA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
has-property-descriptors "^1.0.0"
object-keys "^1.1.1"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
delayed-stream@~1.0.0:
version "1.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/delayed-stream/-/delayed-stream-1.0.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-ZySD7Nf91aLB0RxL4KGrKHBXl7Eds1DAmEdcoVawXnLD7SDhpNgtuII2aAkg7a7QS41jxPSZ17p4VdGnMHk3MQ==
detect-newline@^3.0.0:
version "3.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/detect-newline/-/detect-newline-3.1.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-TLz+x/vEXm/Y7P7wn1EJFNLxYpUD4TgMosxY6fAVJUnJMbupHBOncxyWUG9OpTaH9EBD7uFI5LfEgmMOc54DsA==
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
diff-sequences@^29.4.3:
version "29.4.3"
resolved "https://registry.npmjs.org/diff-sequences/-/diff-sequences-29.4.3.tgz"
integrity sha512-ofrBgwpPhCD85kMKtE9RYFFq6OC1A89oW2vvgWZNCwxrUpRUILopY7lsYyMDSjc8g6U6aiO0Qubg6r4Wgt5ZnA==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
domexception@^4.0.0:
version "4.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/domexception/-/domexception-4.0.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-A2is4PLG+eeSfoTMA95/s4pvAoSo2mKtiM5jlHkAVewmiO8ISFTFKZjH7UAM1Atli/OT/7JHOrJRJiMKUZKYBw==
dependencies:
webidl-conversions "^7.0.0"
feat(jest): mithril component testing (#3679) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * feat(jest): mithril component testing * fix: use separate `tsconfig.test.json` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-11 06:02:50 +08:00
domino@2.1.6:
version "2.1.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/domino/-/domino-2.1.6.tgz"
feat(jest): mithril component testing (#3679) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * feat(jest): mithril component testing * fix: use separate `tsconfig.test.json` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-11 06:02:50 +08:00
integrity sha512-3VdM/SXBZX2omc9JF9nOPCtDaYQ67BGp5CoLpIQlO2KCAPETs8TcDHacF26jXadGbvUteZzRTeos2fhID5+ucQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
duplexer@^0.1.2:
version "0.1.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/duplexer/-/duplexer-0.1.2.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-jtD6YG370ZCIi/9GTaJKQxWTZD045+4R4hTk/x1UyoqadyJ9x9CgSi1RlVDQF8U2sxLLSnFkCaMihqljHIWgMg==
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
electron-to-chromium@^1.4.251:
version "1.4.284"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/electron-to-chromium/-/electron-to-chromium-1.4.284.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-M8WEXFuKXMYMVr45fo8mq0wUrrJHheiKZf6BArTKk9ZBYCKJEOU5H8cdWgDT+qCVZf7Na4lVUaZsA+h6uA9+PA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
emittery@^0.13.1:
version "0.13.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/emittery/-/emittery-0.13.1.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-DeWwawk6r5yR9jFgnDKYt4sLS0LmHJJi3ZOnb5/JdbYwj3nW+FxQnHIjhBKz8YLC7oRNPVM9NQ47I3CVx34eqQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
emoji-regex@^8.0.0:
version "8.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/emoji-regex/-/emoji-regex-8.0.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-MSjYzcWNOA0ewAHpz0MxpYFvwg6yjy1NG3xteoqz644VCo/RPgnr1/GGt+ic3iJTzQ8Eu3TdM14SawnVUmGE6A==
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
emojibase-data@^7.0.1:
version "7.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/emojibase-data/-/emojibase-data-7.0.1.tgz"
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
integrity sha512-BLZpOdwyFpZ7lzBWyDtnxmKVm/SJMYgAfp1if3o6n1TVUMSXAf0nikONXl90LZuJ/m3XWPBkkubgCet2BsCGGQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
emojis-list@^3.0.0:
version "3.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/emojis-list/-/emojis-list-3.0.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-/kyM18EfinwXZbno9FyUGeFh87KC8HRQBQGildHZbEuRyWFOmv1U10o9BBp8XVZDVNNuQKyIGIu5ZYAAXJ0V2Q==
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
enhanced-resolve@^5.10.0:
feat(jest): mithril component testing (#3679) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * feat(jest): mithril component testing * fix: use separate `tsconfig.test.json` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-11 06:02:50 +08:00
version "5.10.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/enhanced-resolve/-/enhanced-resolve-5.10.0.tgz"
feat(jest): mithril component testing (#3679) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * feat(jest): mithril component testing * fix: use separate `tsconfig.test.json` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-11 06:02:50 +08:00
integrity sha512-T0yTFjdpldGY8PmuXXR0PyQ1ufZpEGiHVrp7zHKB7jdR4qlmZHhONVM5AQOAWXuF/w3dnHbEQVrNptJgt7F+cQ==
perf(statistics): rewrite for performance on very large communities (#3531) Co-authored-by: Sami Mazouz <ilyasmazouz@gmail.com>
2022-07-19 02:07:38 +08:00
dependencies:
graceful-fs "^4.2.4"
tapable "^2.2.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
entities@^4.4.0:
version "4.4.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/entities/-/entities-4.4.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-oYp7156SP8LkeGD0GF85ad1X9Ai79WtRsZ2gxJqtBuzH+98YUV6jkHEKlZkMbcrjJjIVJNIDP/3WL9wQkoPbWA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
envinfo@^7.7.3:
version "7.8.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/envinfo/-/envinfo-7.8.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-/o+BXHmB7ocbHEAs6F2EnG0ogybVVUdkRunTT2glZU9XAaGmhqskrvKwqXuDfNjEO0LZKWdejEEpnq8aM0tOaw==
error-ex@^1.3.1:
version "1.3.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/error-ex/-/error-ex-1.3.2.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-7dFHNmqeFSEt2ZBsCriorKnn3Z2pj+fd9kmI6QoWw4//DL+icEBfc0U7qJCisqrTsKTjw4fNFy2pW9OqStD84g==
dependencies:
is-arrayish "^0.2.1"
es-module-lexer@^0.9.0:
version "0.9.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/es-module-lexer/-/es-module-lexer-0.9.3.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-1HQ2M2sPtxwnvOvT1ZClHyQDiggdNjURWpY2we6aMKCQiUVxTmVs2UYPLIrD84sS+kMdUwfBSylbJPwNnBrnHQ==
escalade@^3.1.1:
version "3.1.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/escalade/-/escalade-3.1.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-k0er2gUkLf8O0zKJiAhmkTnJlTvINGv7ygDNPbeIsX/TJjGJZHuh9B2UxbsaEkmlEo9MfhrSzmhIlhRlI2GXnw==
escape-string-regexp@^1.0.5:
version "1.0.5"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.5.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-vbRorB5FUQWvla16U8R/qgaFIya2qGzwDrNmCZuYKrbdSUMG6I1ZCGQRefkRVhuOkIGVne7BQ35DSfo1qvJqFg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
escape-string-regexp@^2.0.0:
version "2.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-2.0.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-UpzcLCXolUWcNu5HtVMHYdXJjArjsF9C0aNnquZYY4uW/Vu0miy5YoWvbV345HauVvcAUnpRuhMMcqTcGOY2+w==
escodegen@^2.0.0:
version "2.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/escodegen/-/escodegen-2.0.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-mmHKys/C8BFUGI+MAWNcSYoORYLMdPzjrknd2Vc+bUsjN5bXcr8EhrNB+UTqfL1y3I9c4fw2ihgtMPQLBRiQxw==
dependencies:
esprima "^4.0.1"
estraverse "^5.2.0"
esutils "^2.0.2"
optionator "^0.8.1"
optionalDependencies:
source-map "~0.6.1"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
eslint-scope@5.1.1:
version "5.1.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/eslint-scope/-/eslint-scope-5.1.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-2NxwbF/hZ0KpepYN0cNbo+FN6XoK7GaHlQhgx/hIZl6Va0bF45RQOOwhLIy8lQDbuCiadSLCBnH2CFYquit5bw==
dependencies:
esrecurse "^4.3.0"
estraverse "^4.1.1"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
esprima@^4.0.0, esprima@^4.0.1:
version "4.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/esprima/-/esprima-4.0.1.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-eGuFFw7Upda+g4p+QHvnW0RyTX/SVeJBDM/gCtMARO0cLuT2HcEKnTPvhjV6aGeqrCB/sbNop0Kszm0jsaWU4A==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
esrecurse@^4.3.0:
version "4.3.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/esrecurse/-/esrecurse-4.3.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-KmfKL3b6G+RXvP8N1vr3Tq1kL/oCFgn2NYXEtqP8/L3pKapUA4G8cFVaoF3SU323CD4XypR/ffioHmkti6/Tag==
dependencies:
estraverse "^5.2.0"
estraverse@^4.1.1:
version "4.3.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/estraverse/-/estraverse-4.3.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-39nnKffWz8xN1BU/2c79n9nB9HDzo0niYUqx6xyqUnyoAnQyyWpOTdZEeiCch8BBu515t4wp9ZmgVfVhn9EBpw==
estraverse@^5.2.0:
version "5.3.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/estraverse/-/estraverse-5.3.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-MMdARuVEQziNTeJD8DgMqmhwR11BRQ/cBP+pLtYdSTnf3MIO8fFeiINEbX36ZdNlfU/7A9f3gUw49B3oQsvwBA==
esutils@^2.0.2:
version "2.0.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/esutils/-/esutils-2.0.3.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-kVscqXk4OCp68SZ0dkgEKVi6/8ij300KBWTJq32P/dYeWTSwK41WyTxalN1eRmA5Z9UU/LX9D7FWSmV9SAYx6g==
events@^3.2.0:
version "3.3.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/events/-/events-3.3.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-mQw+2fkQbALzQ7V0MY0IqdnXNOeTtP4r0lN9z7AAawCXgqea7bDii20AYrIBrFd/Hx0M2Ocz6S111CaFkUcb0Q==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
execa@^5.0.0:
version "5.1.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/execa/-/execa-5.1.1.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-8uSpZZocAZRBAPIEINJj3Lo9HyGitllczc27Eh5YYojjMFMn8yHMDMaUHE2Jqfq05D/wucwI4JGURyXt1vchyg==
dependencies:
cross-spawn "^7.0.3"
get-stream "^6.0.0"
human-signals "^2.1.0"
is-stream "^2.0.0"
merge-stream "^2.0.0"
npm-run-path "^4.0.1"
onetime "^5.1.2"
signal-exit "^3.0.3"
strip-final-newline "^2.0.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
exenv@^1.2.2:
version "1.2.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/exenv/-/exenv-1.2.2.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-Z+ktTxTwv9ILfgKCk32OX3n/doe+OcLTRtqK9pcL+JsP3J1/VW8Uvl4ZjLlKqeW4rzK4oesDOGMEMRIZqtP4Iw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
exit@^0.1.2:
version "0.1.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/exit/-/exit-0.1.2.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-Zk/eNKV2zbjpKzrsQ+n1G6poVbErQxJ0LBOJXaKZ1EViLzH+hrLu9cdXI4zw9dBQJslwBEpbQ2P1oS7nDxs6jQ==
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
expect@^29.0.0, expect@^29.5.0:
version "29.5.0"
resolved "https://registry.npmjs.org/expect/-/expect-29.5.0.tgz"
integrity sha512-yM7xqUrCO2JdpFo4XpM82t+PJBFybdqoQuJLDGeDX2ij8NZzqRHyu3Hp188/JX7SWqud+7t4MUdvcgGBICMHZg==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/expect-utils" "^29.5.0"
jest-get-type "^29.4.3"
jest-matcher-utils "^29.5.0"
jest-message-util "^29.5.0"
jest-util "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
expose-loader@^3.1.0:
version "3.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/expose-loader/-/expose-loader-3.1.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-2RExSo0yJiqP+xiUue13jQa2IHE8kLDzTI7b6kn+vUlBVvlzNSiLDzo4e5Pp5J039usvTUnxZ8sUOhv0Kg15NA==
fast-deep-equal@^3.1.1:
version "3.1.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/fast-deep-equal/-/fast-deep-equal-3.1.3.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-f3qQ9oQy9j2AhBe/H9VC91wLmKBCCU/gDOnKNAYG5hswO7BLKj09Hc5HYNz9cGI++xlpDCIgDaitVs03ATR84Q==
fast-glob@3:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "3.2.12"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/fast-glob/-/fast-glob-3.2.12.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-DVj4CQIYYow0BlaelwK1pHl5n5cRSJfM60UA0zK891sVInoPri2Ekj7+e1CT3/3qxXenpI+nBBmQAcJPJgaj4w==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
"@nodelib/fs.stat" "^2.0.2"
"@nodelib/fs.walk" "^1.2.3"
glob-parent "^5.1.2"
merge2 "^1.3.0"
micromatch "^4.0.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
fast-json-stable-stringify@^2.0.0, fast-json-stable-stringify@^2.1.0, fast-json-stable-stringify@2.x:
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "2.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/fast-json-stable-stringify/-/fast-json-stable-stringify-2.1.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-lhd/wF+Lk98HZoTCtlVraHtfh5XYijIjalXck7saUtuanSDyLMxnHhSXEDJqHxD7msR8D0uCmqlkwjCV8xvwHw==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
fast-levenshtein@~2.0.6:
version "2.0.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/fast-levenshtein/-/fast-levenshtein-2.0.6.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-DCXu6Ifhqcks7TZKY3Hxp3y6qphY5SJZmrWMDrKcERSOXWQdMhU9Ig/PYrzyw/ul9jOIyh0N4M0tbC5hodg8dw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
fastest-levenshtein@^1.0.12:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "1.0.16"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/fastest-levenshtein/-/fastest-levenshtein-1.0.16.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-eRnCtTTtGZFpQCwhJiUOuxPQWRXVKYDn0b2PeHfXL6/Zi53SLAzAHfVhVWK2AryC/WH05kGfxhFIPvTF0SXQzg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
fastq@^1.6.0:
version "1.13.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/fastq/-/fastq-1.13.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-YpkpUnK8od0o1hmeSc7UUs/eB/vIPWJYjKck2QKIzAf71Vm1AAQ3EbuZB3g2JIy+pg+ERD0vqI79KyZiB2e2Nw==
dependencies:
reusify "^1.0.4"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
fb-watchman@^2.0.0:
version "2.0.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/fb-watchman/-/fb-watchman-2.0.2.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-p5161BqbuCaSnB8jIbzQHOlpgsPmK5rJVDfDKO91Axs5NC1uu3HRQm6wt9cd9/+GtQQIO53JdGXXoyDpTAsgYA==
dependencies:
bser "2.1.1"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
fill-range@^7.0.1:
version "7.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/fill-range/-/fill-range-7.0.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-qOo9F+dMUmC2Lcb4BbVvnKJxTPjCm+RRpe4gDuGrzkL7mEVl/djYSu2OdQ2Pa302N4oqkSg9ir6jaLWJ2USVpQ==
dependencies:
to-regex-range "^5.0.1"
find-cache-dir@^3.3.1:
version "3.3.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/find-cache-dir/-/find-cache-dir-3.3.2.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-wXZV5emFEjrridIgED11OoUKLxiYjAcqot/NJdAkOhlJ+vGzwhOAfcG5OX1jP+S0PcjEn8bdMJv+g2jwQ3Onig==
dependencies:
commondir "^1.0.1"
make-dir "^3.0.2"
pkg-dir "^4.1.0"
find-up@^4.0.0, find-up@^4.1.0:
version "4.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/find-up/-/find-up-4.1.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-PpOwAdQ/YlXQ2vj8a3h8IipDuYRi3wceVQQGYWxNINccq40Anw7BlsEXCMbt1Zt+OLA6Fq9suIpIWD0OsnISlw==
dependencies:
locate-path "^5.0.0"
path-exists "^4.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
flarum-tsconfig@^1.0.0, flarum-tsconfig@^1.0.2, "flarum-tsconfig@file:/home/luceos/code/flarum/framework/js-packages/tsconfig":
version "1.0.2"
resolved "file:js-packages/tsconfig"
dependencies:
"@types/jquery" "^3.5.5"
"@types/mithril" "^2.0.7"
"@types/throttle-debounce" "^2.1.0"
dayjs "^1.10.4"
flarum-webpack-config@^2.0.0, flarum-webpack-config@^2.0.1, "flarum-webpack-config@file:/home/luceos/code/flarum/framework/js-packages/webpack-config":
version "2.0.1"
resolved "file:js-packages/webpack-config"
dependencies:
"@babel/core" "^7.16.0"
"@babel/plugin-proposal-class-properties" "^7.16.0"
"@babel/plugin-proposal-private-methods" "^7.16.0"
"@babel/plugin-transform-object-assign" "^7.16.0"
"@babel/plugin-transform-react-jsx" "^7.16.0"
"@babel/plugin-transform-runtime" "^7.16.0"
"@babel/preset-env" "^7.16.0"
"@babel/preset-react" "^7.16.0"
"@babel/preset-typescript" "^7.16.0"
"@babel/runtime" "^7.16.0"
babel-loader "^8.2.3"
typescript "^4.4.4"
webpack "^5.0.0"
webpack-bundle-analyzer "^4.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
flat@^5.0.2:
version "5.0.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/flat/-/flat-5.0.2.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-b6suED+5/3rTpUBdG1gupIl8MPFCAMA0QXwmljLhvCUKcUvdE4gWky9zpuGCcXHOsz4J9wPGNWq6OKpmIzz3hQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
focus-trap@^6.7.1:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "6.9.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/focus-trap/-/focus-trap-6.9.4.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-v2NTsZe2FF59Y+sDykKY+XjqZ0cPfhq/hikWVL88BqLivnNiEffAsac6rP6H45ff9wG9LL5ToiDqrLEP9GX9mw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
tabbable "^5.3.3"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
follow-redirects@^1.14.4:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "1.15.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/follow-redirects/-/follow-redirects-1.15.2.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-VQLG33o04KaQ8uYi2tVNbdrWp1QWxNNea+nmIB4EVM28v0hmP17z7aG1+wAkNzVq4KeXTq3221ye5qTJP91JwA==
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
form-data@^4.0.0:
version "4.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/form-data/-/form-data-4.0.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-ETEklSGi5t0QMZuiXoA/Q6vcnxcLQP5vdugSpuAyi6SVGi2clPPp+xgEhuMaHC+zGgn31Kd235W35f7Hykkaww==
dependencies:
asynckit "^0.4.0"
combined-stream "^1.0.8"
mime-types "^2.1.12"
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
frappe-charts@^1.6.2:
version "1.6.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/frappe-charts/-/frappe-charts-1.6.2.tgz"
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
integrity sha512-9TC3/+YVUi84yYoEbxFiSqu+1FQ5If/ydUNj6i8FRpwynd08t6a7RkS+IRJozAk6NfdL8/LVTTE1DUOjjKZZxg==
fs-extra@^8.0.1:
version "8.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/fs-extra/-/fs-extra-8.1.0.tgz"
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
integrity sha512-yhlQgA6mnOJUKOsRUFsgJdQCvkKhcz8tlZG5HBQfReYZy46OwLcY+Zia0mtdHsOo9y/hP+CxMN0TU9QxoOtG4g==
dependencies:
graceful-fs "^4.2.0"
jsonfile "^4.0.0"
universalify "^0.1.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
fs.realpath@^1.0.0:
version "1.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/fs.realpath/-/fs.realpath-1.0.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-OO0pH2lK6a0hZnAdau5ItzHPI6pUlvI7jMVnxUQRtw4owF2wk8lOSabtGDCTP4Ggrg2MbGnWO9X8K1t4+fGMDw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
function-bind@^1.1.1:
version "1.1.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/function-bind/-/function-bind-1.1.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-yIovAzMX49sF8Yl58fSCWJ5svSLuaibPxXQJFLmBObTuCr0Mf1KiPopGM9NiFjiYBCbfaa2Fh6breQ6ANVTI0A==
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
functions-have-names@^1.2.2:
version "1.2.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/functions-have-names/-/functions-have-names-1.2.3.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-xckBUXyTIqT97tq2x2AMb+g163b5JFysYk0x4qxNFwbfQkmNZoiRHb6sPzI9/QV33WeuvVYBUIiD4NzNIyqaRQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
gensync@^1.0.0-beta.2:
version "1.0.0-beta.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/gensync/-/gensync-1.0.0-beta.2.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-3hN7NaskYvMDLQY55gnW3NQ+mesEAepTqlg+VEbj7zzqEMBVNhzcGYYeqFo/TlYz6eQiFcp1HcsCZO+nGgS8zg==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
get-caller-file@^2.0.5:
version "2.0.5"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/get-caller-file/-/get-caller-file-2.0.5.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-DyFP3BM/3YHTQOCUL/w0OZHR0lpKeGrxotcHWcqNEdnltqFwXVfhEBQ94eIo34AfQpo0rGki4cyIiftY06h2Fg==
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
get-intrinsic@^1.0.2, get-intrinsic@^1.1.1:
version "1.1.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/get-intrinsic/-/get-intrinsic-1.1.3.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-QJVz1Tj7MS099PevUG5jvnt9tSkXN8K14dxQlikJuPt4uD9hHAHjLyLBiLR5zELelBdD9QNRAXZzsJx0WaDL9A==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
function-bind "^1.1.1"
has "^1.0.3"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
has-symbols "^1.0.3"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
get-package-type@^0.1.0:
version "0.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/get-package-type/-/get-package-type-0.1.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-pjzuKtY64GYfWizNAJ0fr9VqttZkNiK2iS430LtIHzjBEr6bX8Am2zm4sW4Ro5wjWW5cAlRL1qAMTcXbjNAO2Q==
get-stream@^6.0.0:
version "6.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/get-stream/-/get-stream-6.0.1.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-ts6Wi+2j3jQjqi70w5AlN8DFnkSwC+MqmxEzdEALB2qXZYV3X/b1CTfgPLGJNMeAWxdPfU8FO1ms3NUfaHCPYg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
glob-parent@^5.1.2:
version "5.1.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-AOIgSQCepiJYwP3ARnGx+5VnTu2HBYdzbGP45eLw1vr3zB3vZLeyed1sC9hnbcOc9/SrMyM5RPQrkGz4aS9Zow==
dependencies:
is-glob "^4.0.1"
glob-to-regexp@^0.4.1:
version "0.4.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/glob-to-regexp/-/glob-to-regexp-0.4.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-lkX1HJXwyMcprw/5YUZc2s7DrpAiHB21/V+E1rHUrVNokkvB6bqMzT0VfV6/86ZNabt1k14YOIaT7nDvOX3Iiw==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
glob@^7.1.2, glob@^7.1.3, glob@^7.1.4:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "7.2.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/glob/-/glob-7.2.3.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-nFR0zLpU2YCaRxwoCJvL6UvCH2JFyFVIvwTLsIf21AuHlMskA1hhTdk+LlYJtOlYt9v6dvszD2BGRqBL+iQK9Q==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
fs.realpath "^1.0.0"
inflight "^1.0.4"
inherits "2"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
minimatch "^3.1.1"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
once "^1.3.0"
path-is-absolute "^1.0.0"
globals@^11.1.0:
version "11.12.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/globals/-/globals-11.12.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-WOBp/EEGUiIsJSp7wcv/y6MO+lV9UoncWqxuFfm8eBwzWNgyfBd6Gz+IeKQ9jCmyhoH99g15M3T+QaVHFjizVA==
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
graceful-fs@^4.1.2, graceful-fs@^4.1.6, graceful-fs@^4.2.0, graceful-fs@^4.2.4, graceful-fs@^4.2.9:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "4.2.10"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.2.10.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-9ByhssR2fPVsNZj478qUUbKfmL0+t5BDVyjShtyZZLiK7ZDAArFFfopyOTj0M05wE2tJPisA4iTnnXl2YoPvOA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
gud@^1.0.0:
version "1.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/gud/-/gud-1.0.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-zGEOVKFM5sVPPrYs7J5/hYEw2Pof8KCyOwyhG8sAF26mCAeUFAcYPu1mwB7hhpIP29zOIBaDqwuHdLp0jvZXjw==
gzip-size@^6.0.0:
version "6.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/gzip-size/-/gzip-size-6.0.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-ax7ZYomf6jqPTQ4+XCpUGyXKHk5WweS+e05MBO4/y3WJ5RkmPXNKvX+bx1behVILVwr6JSQvZAku021CHPXG3Q==
dependencies:
duplexer "^0.1.2"
has-flag@^3.0.0:
version "3.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/has-flag/-/has-flag-3.0.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-sKJf1+ceQBr4SMkvQnBDNDtf4TXpVhVGateu0t918bl30FnbE2m4vNLX+VWe/dpjlb+HugGYzW7uQXH98HPEYw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
has-flag@^4.0.0:
version "4.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/has-flag/-/has-flag-4.0.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
has-property-descriptors@^1.0.0:
version "1.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/has-property-descriptors/-/has-property-descriptors-1.0.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-62DVLZGoiEBDHQyqG4w9xCuZ7eJEwNmJRWw2VY84Oedb7WFcA27fiEVe8oUQx9hAUJ4ekurquucTGwsyO1XGdQ==
dependencies:
get-intrinsic "^1.1.1"
has-symbols@^1.0.2, has-symbols@^1.0.3:
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "1.0.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/has-symbols/-/has-symbols-1.0.3.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-l3LCuF6MgDNwTDKkdYGEihYjt5pRPbEg46rtlmnSPlUbgmB8LOIrKJbYYFBSbnPaJexMKtiPO8hmeRjRz2Td+A==
has-tostringtag@^1.0.0:
version "1.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/has-tostringtag/-/has-tostringtag-1.0.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-kFjcSNhnlGV1kyoGk7OXKSawH5JOb/LzUc5w9B02hOTO0dfFRjbHQKvg1d6cf3HbeUmtU9VbbV3qzZ2Teh97WQ==
dependencies:
has-symbols "^1.0.2"
has@^1.0.3:
version "1.0.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/has/-/has-1.0.3.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-f2dvO0VU6Oej7RkWJGrehjbzMAjFp5/VKPp5tTpWIV4JHHZK1/BxbFRtf/siA2SWTe09caDmVtYYzWEIbBS4zw==
dependencies:
function-bind "^1.1.1"
hosted-git-info@^2.1.4:
version "2.8.9"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.8.9.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-mxIDAb9Lsm6DoOJ7xH+5+X4y1LU/4Hi50L9C5sIswK3JzULS4bwk1FvjdBgvYR4bzT4tuUQiC15FE2f5HbLvYw==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
html-encoding-sniffer@^3.0.0:
version "3.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/html-encoding-sniffer/-/html-encoding-sniffer-3.0.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-oWv4T4yJ52iKrufjnyZPkrN0CH3QnrUqdB6In1g5Fe1mia8GmF36gnfNySxoZtxD5+NmYw1EElVXiBk93UeskA==
dependencies:
whatwg-encoding "^2.0.0"
html-escaper@^2.0.0:
version "2.0.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/html-escaper/-/html-escaper-2.0.2.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-H2iMtd0I4Mt5eYiapRdIDjp+XzelXQ0tFE4JS7YFwFevXXMmOp9myNrUvCg0D6ws8iqkRPBfKHgbwig1SmlLfg==
http-proxy-agent@^5.0.0:
version "5.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/http-proxy-agent/-/http-proxy-agent-5.0.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-n2hY8YdoRE1i7r6M0w9DIw5GgZN0G25P8zLCRQ8rjXtTU3vsNFBI/vWK/UIeE6g5MUUz6avwAPXmL6Fy9D/90w==
dependencies:
"@tootallnate/once" "2"
agent-base "6"
debug "4"
https-proxy-agent@^5.0.1:
version "5.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/https-proxy-agent/-/https-proxy-agent-5.0.1.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-dFcAjpTQFgoLMzC2VwU+C/CbS7uRL0lWmxDITmqm7C+7F0Odmj6s9l6alZc6AELXhrnggM2CeWSXHGOdX2YtwA==
dependencies:
agent-base "6"
debug "4"
human-signals@^2.1.0:
version "2.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/human-signals/-/human-signals-2.1.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-B4FFZ6q/T2jhhksgkbEW3HBvWIfDW85snkQgawt07S7J5QXTk6BkNV+0yAeZrM5QpMAdYlocGoljn0sJ/WQkFw==
iconv-lite@0.6.3:
version "0.6.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/iconv-lite/-/iconv-lite-0.6.3.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-4fCk79wshMdzMp2rH06qWrJE4iolqLhCUH+OiuIgU++RB0+94NlDL81atO7GX55uUKueo0txHNtvEyI6D7WdMw==
dependencies:
safer-buffer ">= 2.1.2 < 3.0.0"
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
iframe-resizer@^4.3.2:
version "4.3.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/iframe-resizer/-/iframe-resizer-4.3.2.tgz"
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
integrity sha512-gOWo2hmdPjMQsQ+zTKbses08mDfDEMh4NneGQNP4qwePYujY1lguqP6gnbeJkf154gojWlBhIltlgnMfYjGHWA==
import-fresh@^3.2.1:
version "3.3.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/import-fresh/-/import-fresh-3.3.0.tgz"
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
integrity sha512-veYYhQa+D1QBKznvhUHxb8faxlrwUnxseDAbAp457E0wLNio2bOSKnjYDhMj+YiAq61xrMGhQk9iXVk5FzgQMw==
dependencies:
parent-module "^1.0.0"
resolve-from "^4.0.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
import-local@^3.0.2:
version "3.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/import-local/-/import-local-3.1.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-ASB07uLtnDs1o6EHjKpX34BKYDSqnFerfTOJL2HvMqF70LnxpjkzDB8J44oT9pu4AMPkQwf8jl6szgvNd2tRIg==
dependencies:
pkg-dir "^4.2.0"
resolve-cwd "^3.0.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
imurmurhash@^0.1.4:
version "0.1.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/imurmurhash/-/imurmurhash-0.1.4.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-JmXMZ6wuvDmLiHEml9ykzqO6lwFbof0GG4IkcGaENdCRDDmMVnny7s5HsIgHCbaq0w2MyPhDqkhTUgS2LU2PHA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
inflight@^1.0.4:
version "1.0.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/inflight/-/inflight-1.0.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-k92I/b08q4wvFscXCLvqfsHCrjrF7yiXsQuIVvVE7N82W3+aqpzuUdBbfhWcy/FZR3/4IgflMgKLOsvPDrGCJA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
once "^1.3.0"
wrappy "1"
inherits@2:
version "2.0.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/inherits/-/inherits-2.0.4.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-k/vGaX4/Yla3WzyMCvTQOXYeIHvqOKtnqBduzTHpzpQZzAskKMhZ2K+EnBiSM9zGSoIFeMpXKxa4dYeZIQqewQ==
interpret@^2.2.0:
version "2.2.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/interpret/-/interpret-2.2.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-Ju0Bz/cEia55xDwUWEa8+olFpCiQoypjnQySseKtmjNrnps3P+xfpUmGr90T7yjlVJmOtybRvPXhKMbHr+fWnw==
is-arguments@^1.0.4:
version "1.1.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/is-arguments/-/is-arguments-1.1.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-8Q7EARjzEnKpt/PCD7e1cgUS0a6X8u5tdSiMqXhojOdoV9TsMsiO+9VLC5vAmO8N7/GmXn7yjR8qnA6bVAEzfA==
dependencies:
call-bind "^1.0.2"
has-tostringtag "^1.0.0"
is-arrayish@^0.2.1:
version "0.2.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/is-arrayish/-/is-arrayish-0.2.1.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-zz06S8t0ozoDXMG+ube26zeCTNXcKIPJZJi8hBrF4idCLms4CG9QtK7qBl1boi5ODzFpjswb5JPmHCbMpjaYzg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
is-core-module@^2.9.0:
version "2.11.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/is-core-module/-/is-core-module-2.11.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-RRjxlvLDkD1YJwDbroBHMb+cukurkDWNyHx7D3oNB5x9rb5ogcksMC5wHCadcXoo67gVr/+3GFySh3134zi6rw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
has "^1.0.3"
is-date-object@^1.0.1:
version "1.0.5"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/is-date-object/-/is-date-object-1.0.5.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-9YQaSxsAiSwcvS33MBk3wTCVnWK+HhF8VZR2jRxehM16QcVOdHqPn4VPHmRK4lSr38n9JriurInLcP90xsYNfQ==
dependencies:
has-tostringtag "^1.0.0"
is-extglob@^2.1.1:
version "2.1.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/is-extglob/-/is-extglob-2.1.1.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-SbKbANkN603Vi4jEZv49LeVJMn4yGwsbzZworEoyEiutsN3nJYdbO36zfhGJ6QEDpOZIFkDtnq5JRxmvl3jsoQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
is-fullwidth-code-point@^3.0.0:
version "3.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/is-fullwidth-code-point/-/is-fullwidth-code-point-3.0.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-zymm5+u+sCsSWyD9qNaejV3DFvhCKclKdizYaJUuHA83RLjb7nSuGnddCHGv0hk+KY7BMAlsWeK4Ueg6EV6XQg==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
is-generator-fn@^2.0.0:
version "2.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/is-generator-fn/-/is-generator-fn-2.1.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-cTIB4yPYL/Grw0EaSzASzg6bBy9gqCofvWN8okThAYIxKJZC+udlRAmGbM0XLeniEJSs8uEgHPGuHSe1XsOLSQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
is-glob@^4.0.1:
version "4.0.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/is-glob/-/is-glob-4.0.3.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-xelSayHH36ZgE7ZWhli7pW34hNbNl8Ojv5KVmkJD4hBdD3th8Tfk9vYasLM+mXWOZhFkgZfxhLSnrwRr4elSSg==
dependencies:
is-extglob "^2.1.1"
is-number@^7.0.0:
version "7.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/is-number/-/is-number-7.0.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-41Cifkg6e8TylSpdtTpeLVMqvSBEVzTttHvERD741+pnZ8ANv0004MRL43QKPDlK9cGvNp6NZWZUBlbGXYxxng==
is-plain-object@^2.0.4:
version "2.0.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/is-plain-object/-/is-plain-object-2.0.4.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-h5PpgXkWitc38BBMYawTYMWJHFZJVnBquFE57xFpjB8pJFiF6gZ+bU+WyI/yqXiFR5mdLsgYNaPe8uao6Uv9Og==
dependencies:
isobject "^3.0.1"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
is-potential-custom-element-name@^1.0.1:
version "1.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/is-potential-custom-element-name/-/is-potential-custom-element-name-1.0.1.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-bCYeRA2rVibKZd+s2625gGnGF/t7DSqDs4dP7CrLA1m7jKWz6pps0LpYLJN8Q64HtmPKJ1hrN3nzPNKFEKOUiQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
is-regex@^1.0.4:
version "1.1.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/is-regex/-/is-regex-1.1.4.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-kvRdxDsxZjhzUX07ZnLydzS1TU/TJlTUHHY4YLL87e37oUA49DfkLqgy+VjFocowy29cKvcSiu+kIv728jTTVg==
dependencies:
call-bind "^1.0.2"
has-tostringtag "^1.0.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
is-stream@^2.0.0:
version "2.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/is-stream/-/is-stream-2.0.1.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-hFoiJiTl63nn+kstHGBtewWSKnQLpyb155KHheA1l39uvtO9nWIop1p3udqPcUd/xbF1VLMO4n7OI6p7RbngDg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
isexe@^2.0.0:
version "2.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/isexe/-/isexe-2.0.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-RHxMLp9lnKHGHRng9QFhRCMbYAcVpn69smSGcq3f36xjgVVWThj4qqLbTLlq7Ssj8B+fIQ1EuCEGI2lKsyQeIw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
isobject@^3.0.1:
version "3.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/isobject/-/isobject-3.0.1.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-WhB9zCku7EGTj/HQQRz5aUQEUeoQZH2bWcltRErOpymJ4boYE6wL9Tbr23krRPSZ+C5zqNSrSw+Cc7sZZ4b7vg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
istanbul-lib-coverage@^3.0.0, istanbul-lib-coverage@^3.2.0:
version "3.2.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/istanbul-lib-coverage/-/istanbul-lib-coverage-3.2.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-eOeJ5BHCmHYvQK7xt9GkdHuzuCGS1Y6g9Gvnx3Ym33fz/HpLRYxiS0wHNr+m/MBC8B647Xt608vCDEvhl9c6Mw==
istanbul-lib-instrument@^5.0.4, istanbul-lib-instrument@^5.1.0:
version "5.2.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/istanbul-lib-instrument/-/istanbul-lib-instrument-5.2.1.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-pzqtp31nLv/XFOzXGuvhCb8qhjmTVo5vjVk19XE4CRlSWz0KoeJ3bw9XsA7nOp9YBf4qHjwBxkDzKcME/J29Yg==
dependencies:
"@babel/core" "^7.12.3"
"@babel/parser" "^7.14.7"
"@istanbuljs/schema" "^0.1.2"
istanbul-lib-coverage "^3.2.0"
semver "^6.3.0"
istanbul-lib-report@^3.0.0:
version "3.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/istanbul-lib-report/-/istanbul-lib-report-3.0.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-wcdi+uAKzfiGT2abPpKZ0hSU1rGQjUQnLvtY5MpQ7QCTahD3VODhcu4wcfY1YtkGaDD5yuydOLINXsfbus9ROw==
dependencies:
istanbul-lib-coverage "^3.0.0"
make-dir "^3.0.0"
supports-color "^7.1.0"
istanbul-lib-source-maps@^4.0.0:
version "4.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/istanbul-lib-source-maps/-/istanbul-lib-source-maps-4.0.1.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-n3s8EwkdFIJCG3BPKBYvskgXGoy88ARzvegkitk60NxRdwltLOTaH7CUiMRXvwYorl0Q712iEjcWB+fK/MrWVw==
dependencies:
debug "^4.1.1"
istanbul-lib-coverage "^3.0.0"
source-map "^0.6.1"
istanbul-reports@^3.1.3:
version "3.1.5"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/istanbul-reports/-/istanbul-reports-3.1.5.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-nUsEMa9pBt/NOHqbcbeJEgqIlY/K7rVWUX6Lql2orY5e9roQOthbR3vtY4zzf2orPELg80fnxxk9zUyPlgwD1w==
dependencies:
html-escaper "^2.0.0"
istanbul-lib-report "^3.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-changed-files@^29.5.0:
version "29.5.0"
resolved "https://registry.npmjs.org/jest-changed-files/-/jest-changed-files-29.5.0.tgz"
integrity sha512-IFG34IUMUaNBIxjQXF/iu7g6EcdMrGRRxaUSw92I/2g2YC6vCdTltl4nHvt7Ci5nSJwXIkCu8Ka1DKF+X7Z1Ag==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
execa "^5.0.0"
p-limit "^3.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-circus@^29.5.0:
version "29.5.0"
resolved "https://registry.npmjs.org/jest-circus/-/jest-circus-29.5.0.tgz"
integrity sha512-gq/ongqeQKAplVxqJmbeUOJJKkW3dDNPY8PjhJ5G0lBRvu0e3EWGxGy5cI4LAGA7gV2UHCtWBI4EMXK8c9nQKA==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/environment" "^29.5.0"
"@jest/expect" "^29.5.0"
"@jest/test-result" "^29.5.0"
"@jest/types" "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@types/node" "*"
chalk "^4.0.0"
co "^4.6.0"
dedent "^0.7.0"
is-generator-fn "^2.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-each "^29.5.0"
jest-matcher-utils "^29.5.0"
jest-message-util "^29.5.0"
jest-runtime "^29.5.0"
jest-snapshot "^29.5.0"
jest-util "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
p-limit "^3.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
pretty-format "^29.5.0"
pure-rand "^6.0.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
slash "^3.0.0"
stack-utils "^2.0.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-cli@^29.5.0:
version "29.5.0"
resolved "https://registry.npmjs.org/jest-cli/-/jest-cli-29.5.0.tgz"
integrity sha512-L1KcP1l4HtfwdxXNFCL5bmUbLQiKrakMUriBEcc1Vfz6gx31ORKdreuWvmQVBit+1ss9NNR3yxjwfwzZNdQXJw==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/core" "^29.5.0"
"@jest/test-result" "^29.5.0"
"@jest/types" "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
chalk "^4.0.0"
exit "^0.1.2"
graceful-fs "^4.2.9"
import-local "^3.0.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-config "^29.5.0"
jest-util "^29.5.0"
jest-validate "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
prompts "^2.0.1"
yargs "^17.3.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-config@^29.5.0:
version "29.5.0"
resolved "https://registry.npmjs.org/jest-config/-/jest-config-29.5.0.tgz"
integrity sha512-kvDUKBnNJPNBmFFOhDbm59iu1Fii1Q6SxyhXfvylq3UTHbg6o7j/g8k2dZyXWLvfdKB1vAPxNZnMgtKJcmu3kA==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
"@babel/core" "^7.11.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/test-sequencer" "^29.5.0"
"@jest/types" "^29.5.0"
babel-jest "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
chalk "^4.0.0"
ci-info "^3.2.0"
deepmerge "^4.2.2"
glob "^7.1.3"
graceful-fs "^4.2.9"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-circus "^29.5.0"
jest-environment-node "^29.5.0"
jest-get-type "^29.4.3"
jest-regex-util "^29.4.3"
jest-resolve "^29.5.0"
jest-runner "^29.5.0"
jest-util "^29.5.0"
jest-validate "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
micromatch "^4.0.4"
parse-json "^5.2.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
pretty-format "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
slash "^3.0.0"
strip-json-comments "^3.1.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-diff@^29.5.0:
version "29.5.0"
resolved "https://registry.npmjs.org/jest-diff/-/jest-diff-29.5.0.tgz"
integrity sha512-LtxijLLZBduXnHSniy0WMdaHjmQnt3g5sa16W4p0HqukYTTsyTW3GD1q41TyGl5YFXj/5B2U6dlh5FM1LIMgxw==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
chalk "^4.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
diff-sequences "^29.4.3"
jest-get-type "^29.4.3"
pretty-format "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-docblock@^29.4.3:
version "29.4.3"
resolved "https://registry.npmjs.org/jest-docblock/-/jest-docblock-29.4.3.tgz"
integrity sha512-fzdTftThczeSD9nZ3fzA/4KkHtnmllawWrXO69vtI+L9WjEIuXWs4AmyME7lN5hU7dB0sHhuPfcKofRsUb/2Fg==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
detect-newline "^3.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-each@^29.5.0:
version "29.5.0"
resolved "https://registry.npmjs.org/jest-each/-/jest-each-29.5.0.tgz"
integrity sha512-HM5kIJ1BTnVt+DQZ2ALp3rzXEl+g726csObrW/jpEGl+CDSSQpOJJX2KE/vEg8cxcMXdyEPu6U4QX5eruQv5hA==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/types" "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
chalk "^4.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-get-type "^29.4.3"
jest-util "^29.5.0"
pretty-format "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
jest-environment-jsdom@^29.3.1:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
version "29.5.0"
resolved "https://registry.npmjs.org/jest-environment-jsdom/-/jest-environment-jsdom-29.5.0.tgz"
integrity sha512-/KG8yEK4aN8ak56yFVdqFDzKNHgF4BAymCx2LbPNPsUshUlfAl0eX402Xm1pt+eoG9SLZEUVifqXtX8SK74KCw==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/environment" "^29.5.0"
"@jest/fake-timers" "^29.5.0"
"@jest/types" "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@types/jsdom" "^20.0.0"
"@types/node" "*"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-mock "^29.5.0"
jest-util "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
jsdom "^20.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-environment-node@^29.5.0:
version "29.5.0"
resolved "https://registry.npmjs.org/jest-environment-node/-/jest-environment-node-29.5.0.tgz"
integrity sha512-ExxuIK/+yQ+6PRGaHkKewYtg6hto2uGCgvKdb2nfJfKXgZ17DfXjvbZ+jA1Qt9A8EQSfPnt5FKIfnOO3u1h9qw==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/environment" "^29.5.0"
"@jest/fake-timers" "^29.5.0"
"@jest/types" "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@types/node" "*"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-mock "^29.5.0"
jest-util "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-get-type@^29.4.3:
version "29.4.3"
resolved "https://registry.npmjs.org/jest-get-type/-/jest-get-type-29.4.3.tgz"
integrity sha512-J5Xez4nRRMjk8emnTpWrlkyb9pfRQQanDrvWHhsR1+VUfbwxi30eVcZFlcdGInRibU4G5LwHXpI7IRHU0CY+gg==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-haste-map@^29.5.0:
version "29.5.0"
resolved "https://registry.npmjs.org/jest-haste-map/-/jest-haste-map-29.5.0.tgz"
integrity sha512-IspOPnnBro8YfVYSw6yDRKh/TiCdRngjxeacCps1cQ9cgVN6+10JUcuJ1EabrgYLOATsIAigxA0rLR9x/YlrSA==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/types" "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@types/graceful-fs" "^4.1.3"
"@types/node" "*"
anymatch "^3.0.3"
fb-watchman "^2.0.0"
graceful-fs "^4.2.9"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-regex-util "^29.4.3"
jest-util "^29.5.0"
jest-worker "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
micromatch "^4.0.4"
walker "^1.0.8"
optionalDependencies:
fsevents "^2.3.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-leak-detector@^29.5.0:
version "29.5.0"
resolved "https://registry.npmjs.org/jest-leak-detector/-/jest-leak-detector-29.5.0.tgz"
integrity sha512-u9YdeeVnghBUtpN5mVxjID7KbkKE1QU4f6uUwuxiY0vYRi9BUCLKlPEZfDGR67ofdFmDz9oPAy2G92Ujrntmow==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-get-type "^29.4.3"
pretty-format "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-matcher-utils@^29.5.0:
version "29.5.0"
resolved "https://registry.npmjs.org/jest-matcher-utils/-/jest-matcher-utils-29.5.0.tgz"
integrity sha512-lecRtgm/rjIK0CQ7LPQwzCs2VwW6WAahA55YBuI+xqmhm7LAaxokSB8C97yJeYyT+HvQkH741StzpU41wohhWw==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
chalk "^4.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-diff "^29.5.0"
jest-get-type "^29.4.3"
pretty-format "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-message-util@^29.5.0:
version "29.5.0"
resolved "https://registry.npmjs.org/jest-message-util/-/jest-message-util-29.5.0.tgz"
integrity sha512-Kijeg9Dag6CKtIDA7O21zNTACqD5MD/8HfIV8pdD94vFyFuer52SigdC3IQMhab3vACxXMiFk+yMHNdbqtyTGA==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
"@babel/code-frame" "^7.12.13"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/types" "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@types/stack-utils" "^2.0.0"
chalk "^4.0.0"
graceful-fs "^4.2.9"
micromatch "^4.0.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
pretty-format "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
slash "^3.0.0"
stack-utils "^2.0.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-mock@^29.5.0:
version "29.5.0"
resolved "https://registry.npmjs.org/jest-mock/-/jest-mock-29.5.0.tgz"
integrity sha512-GqOzvdWDE4fAV2bWQLQCkujxYWL7RxjCnj71b5VhDAGOevB3qj3Ovg26A5NI84ZpODxyzaozXLOh2NCgkbvyaw==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/types" "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@types/node" "*"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-util "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
jest-pnp-resolver@^1.2.2:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
version "1.2.3"
resolved "https://registry.npmjs.org/jest-pnp-resolver/-/jest-pnp-resolver-1.2.3.tgz"
integrity sha512-+3NpwQEnRoIBtx4fyhblQDPgJI0H1IEIkX7ShLUjPGA7TtUTvI1oiKi3SR4oBR0hQhQR80l4WAe5RrXBwWMA8w==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-regex-util@^29.4.3:
version "29.4.3"
resolved "https://registry.npmjs.org/jest-regex-util/-/jest-regex-util-29.4.3.tgz"
integrity sha512-O4FglZaMmWXbGHSQInfXewIsd1LMn9p3ZXB/6r4FOkyhX2/iP/soMG98jGvk/A3HAN78+5VWcBGO0BJAPRh4kg==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-resolve-dependencies@^29.5.0:
version "29.5.0"
resolved "https://registry.npmjs.org/jest-resolve-dependencies/-/jest-resolve-dependencies-29.5.0.tgz"
integrity sha512-sjV3GFr0hDJMBpYeUuGduP+YeCRbd7S/ck6IvL3kQ9cpySYKqcqhdLLC2rFwrcL7tz5vYibomBrsFYWkIGGjOg==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-regex-util "^29.4.3"
jest-snapshot "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-resolve@*, jest-resolve@^29.5.0:
version "29.5.0"
resolved "https://registry.npmjs.org/jest-resolve/-/jest-resolve-29.5.0.tgz"
integrity sha512-1TzxJ37FQq7J10jPtQjcc+MkCkE3GBpBecsSUWJ0qZNJpmg6m0D9/7II03yJulm3H/fvVjgqLh/k2eYg+ui52w==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
chalk "^4.0.0"
graceful-fs "^4.2.9"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-haste-map "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
jest-pnp-resolver "^1.2.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-util "^29.5.0"
jest-validate "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
resolve "^1.20.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolve.exports "^2.0.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
slash "^3.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-runner@^29.5.0:
version "29.5.0"
resolved "https://registry.npmjs.org/jest-runner/-/jest-runner-29.5.0.tgz"
integrity sha512-m7b6ypERhFghJsslMLhydaXBiLf7+jXy8FwGRHO3BGV1mcQpPbwiqiKUR2zU2NJuNeMenJmlFZCsIqzJCTeGLQ==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/console" "^29.5.0"
"@jest/environment" "^29.5.0"
"@jest/test-result" "^29.5.0"
"@jest/transform" "^29.5.0"
"@jest/types" "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@types/node" "*"
chalk "^4.0.0"
emittery "^0.13.1"
graceful-fs "^4.2.9"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-docblock "^29.4.3"
jest-environment-node "^29.5.0"
jest-haste-map "^29.5.0"
jest-leak-detector "^29.5.0"
jest-message-util "^29.5.0"
jest-resolve "^29.5.0"
jest-runtime "^29.5.0"
jest-util "^29.5.0"
jest-watcher "^29.5.0"
jest-worker "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
p-limit "^3.1.0"
source-map-support "0.5.13"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-runtime@^29.5.0:
version "29.5.0"
resolved "https://registry.npmjs.org/jest-runtime/-/jest-runtime-29.5.0.tgz"
integrity sha512-1Hr6Hh7bAgXQP+pln3homOiEZtCDZFqwmle7Ew2j8OlbkIu6uE3Y/etJQG8MLQs3Zy90xrp2C0BRrtPHG4zryw==
dependencies:
"@jest/environment" "^29.5.0"
"@jest/fake-timers" "^29.5.0"
"@jest/globals" "^29.5.0"
"@jest/source-map" "^29.4.3"
"@jest/test-result" "^29.5.0"
"@jest/transform" "^29.5.0"
"@jest/types" "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@types/node" "*"
chalk "^4.0.0"
cjs-module-lexer "^1.0.0"
collect-v8-coverage "^1.0.0"
glob "^7.1.3"
graceful-fs "^4.2.9"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-haste-map "^29.5.0"
jest-message-util "^29.5.0"
jest-mock "^29.5.0"
jest-regex-util "^29.4.3"
jest-resolve "^29.5.0"
jest-snapshot "^29.5.0"
jest-util "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
slash "^3.0.0"
strip-bom "^4.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-snapshot@^29.5.0:
version "29.5.0"
resolved "https://registry.npmjs.org/jest-snapshot/-/jest-snapshot-29.5.0.tgz"
integrity sha512-x7Wolra5V0tt3wRs3/ts3S6ciSQVypgGQlJpz2rsdQYoUKxMxPNaoHMGJN6qAuPJqS+2iQ1ZUn5kl7HCyls84g==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
"@babel/core" "^7.11.6"
"@babel/generator" "^7.7.2"
"@babel/plugin-syntax-jsx" "^7.7.2"
"@babel/plugin-syntax-typescript" "^7.7.2"
"@babel/traverse" "^7.7.2"
"@babel/types" "^7.3.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/expect-utils" "^29.5.0"
"@jest/transform" "^29.5.0"
"@jest/types" "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@types/babel__traverse" "^7.0.6"
"@types/prettier" "^2.1.5"
babel-preset-current-node-syntax "^1.0.0"
chalk "^4.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
expect "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
graceful-fs "^4.2.9"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-diff "^29.5.0"
jest-get-type "^29.4.3"
jest-matcher-utils "^29.5.0"
jest-message-util "^29.5.0"
jest-util "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
natural-compare "^1.4.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
pretty-format "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
semver "^7.3.5"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-util@^29.0.0, jest-util@^29.5.0:
version "29.5.0"
resolved "https://registry.npmjs.org/jest-util/-/jest-util-29.5.0.tgz"
integrity sha512-RYMgG/MTadOr5t8KdhejfvUU82MxsCu5MF6KuDUHl+NuwzUt+Sm6jJWxTJVrDR1j5M/gJVCPKQEpWXY+yIQ6lQ==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/types" "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@types/node" "*"
chalk "^4.0.0"
ci-info "^3.2.0"
graceful-fs "^4.2.9"
picomatch "^2.2.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-validate@^29.5.0:
version "29.5.0"
resolved "https://registry.npmjs.org/jest-validate/-/jest-validate-29.5.0.tgz"
integrity sha512-pC26etNIi+y3HV8A+tUGr/lph9B18GnzSRAkPaaZJIE1eFdiYm6/CewuiJQ8/RlfHd1u/8Ioi8/sJ+CmbA+zAQ==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/types" "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
camelcase "^6.2.0"
chalk "^4.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-get-type "^29.4.3"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
leven "^3.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
pretty-format "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-watcher@^29.5.0:
version "29.5.0"
resolved "https://registry.npmjs.org/jest-watcher/-/jest-watcher-29.5.0.tgz"
integrity sha512-KmTojKcapuqYrKDpRwfqcQ3zjMlwu27SYext9pt4GlF5FUgB+7XE1mcCnSm6a4uUpFyQIkb6ZhzZvHl+jiBCiA==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/test-result" "^29.5.0"
"@jest/types" "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"@types/node" "*"
ansi-escapes "^4.2.1"
chalk "^4.0.0"
emittery "^0.13.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-util "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
string-length "^4.0.1"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
jest-worker@^27.4.5:
version "27.5.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/jest-worker/-/jest-worker-27.5.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-7vuh85V5cdDofPyxn58nrPjBktZo0u9x1g8WtjQol+jZDaE+fhN+cIvTj11GndBnMnyfrUOG1sZQxCdjKh+DKg==
dependencies:
"@types/node" "*"
merge-stream "^2.0.0"
supports-color "^8.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-worker@^29.5.0:
version "29.5.0"
resolved "https://registry.npmjs.org/jest-worker/-/jest-worker-29.5.0.tgz"
integrity sha512-NcrQnevGoSp4b5kg+akIpthoAFHxPBcb5P6mYPY0fUNT+sSvmtu6jlkEle3anczUKIKEbMxFimk9oTP/tpIPgA==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
"@types/node" "*"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-util "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
merge-stream "^2.0.0"
supports-color "^8.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest@^29.0.0, jest@^29.3.1:
version "29.5.0"
resolved "https://registry.npmjs.org/jest/-/jest-29.5.0.tgz"
integrity sha512-juMg3he2uru1QoXX078zTa7pO85QyB9xajZc6bU+d9yEGwrKX6+vGmJQ3UdVZsvTEUARIdObzH68QItim6OSSQ==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/core" "^29.5.0"
"@jest/types" "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
import-local "^3.0.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
jest-cli "^29.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
jquery.hotkeys@^0.1.0:
version "0.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/jquery.hotkeys/-/jquery.hotkeys-0.1.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-7qPojy/67vjvQxoeOgzPJ3/0t5p7cdnfIKs+f2r+4GlY2ISzknawjXiWUrz8R/N2iRi8A+sNYpkC5+EpAOggtA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
jquery@^3.6.0:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "3.6.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/jquery/-/jquery-3.6.1.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-opJeO4nCucVnsjiXOE+/PcCgYw9Gwpvs/a6B1LL/lQhwWwpbVEVYDZ1FokFr8PRc7ghYlrFPuyHuiiDNTQxmcw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"js-tokens@^3.0.0 || ^4.0.0", js-tokens@^4.0.0:
version "4.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/js-tokens/-/js-tokens-4.0.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-RdJUflcE3cUzKiMqQgsCu06FPu9UdIJO0beYbPhHN4k6apgJtifcoCtT9bcxOpYBtpD2kCM6Sbzg4CausW/PKQ==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
js-yaml@^3.13.1:
version "3.14.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/js-yaml/-/js-yaml-3.14.1.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-okMH7OXXJ7YrN9Ok3/SXrnu4iX9yOk+25nqX4imS2npuvTYDmo/QEZoqwZkYaIDk3jVvBOTOIEgEhaLOynBS9g==
dependencies:
argparse "^1.0.7"
esprima "^4.0.0"
js-yaml@^4.1.0:
version "4.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/js-yaml/-/js-yaml-4.1.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-wpxZs9NoxZaJESJGIZTyDEaYpl0FKSA+FB9aJiyemKhMwkxQg63h4T1KJgUGHpTqPDNRcmmYLugrRjJlBtWvRA==
dependencies:
argparse "^2.0.1"
jsdom@^20.0.0:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
version "20.0.3"
resolved "https://registry.npmjs.org/jsdom/-/jsdom-20.0.3.tgz"
integrity sha512-SYhBvTh89tTfCD/CRdSOm13mOBa42iTaTyfyEWBdKcGdPxPtLFBXuHR8XHb33YNYaP+lLbmSvBTsnoesCNJEsQ==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
abab "^2.0.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
acorn "^8.8.1"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
acorn-globals "^7.0.0"
cssom "^0.5.0"
cssstyle "^2.3.0"
data-urls "^3.0.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
decimal.js "^10.4.2"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
domexception "^4.0.0"
escodegen "^2.0.0"
form-data "^4.0.0"
html-encoding-sniffer "^3.0.0"
http-proxy-agent "^5.0.0"
https-proxy-agent "^5.0.1"
is-potential-custom-element-name "^1.0.1"
nwsapi "^2.2.2"
parse5 "^7.1.1"
saxes "^6.0.0"
symbol-tree "^3.2.4"
tough-cookie "^4.1.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
w3c-xmlserializer "^4.0.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
webidl-conversions "^7.0.0"
whatwg-encoding "^2.0.0"
whatwg-mimetype "^3.0.0"
whatwg-url "^11.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
ws "^8.11.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
xml-name-validator "^4.0.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
jsesc@^2.5.1:
version "2.5.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/jsesc/-/jsesc-2.5.2.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-OYu7XEzjkCQ3C5Ps3QIZsQfNpqoJyZZA99wd9aWd05NCtC5pWOkShK2mkL6HXQR6/Cy2lbNdPlZBpuQHXE63gA==
jsesc@~0.5.0:
version "0.5.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/jsesc/-/jsesc-0.5.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-uZz5UnB7u4T9LvwmFqXii7pZSouaRPorGs5who1Ip7VO0wxanFvBL7GkM6dTHlgX+jhBApRetaWpnDabOeTcnA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
perf(statistics): rewrite for performance on very large communities (#3531) Co-authored-by: Sami Mazouz <ilyasmazouz@gmail.com>
2022-07-19 02:07:38 +08:00
json-parse-even-better-errors@^2.3.0, json-parse-even-better-errors@^2.3.1:
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "2.3.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/json-parse-even-better-errors/-/json-parse-even-better-errors-2.3.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-xyFwyhro/JEof6Ghe2iz2NcXoj2sloNsWr/XsERDK/oiPCfaNhl5ONfp+jQdAZRQQ0IJWNzH9zIZF7li91kh2w==
json-schema-traverse@^0.4.1:
version "0.4.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/json-schema-traverse/-/json-schema-traverse-0.4.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-xbbCH5dCYU5T8LcEhhuh7HJ88HXuW3qsI3Y0zOZFKfZEHcpWiHU/Jxzk629Brsab/mMiHQti9wMP+845RPe3Vg==
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
json5@^2.1.2, json5@^2.2.1, json5@^2.2.3:
chore: `yarn audit-fix` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-03-01 19:35:59 +08:00
version "2.2.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/json5/-/json5-2.2.3.tgz"
chore: `yarn audit-fix` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-03-01 19:35:59 +08:00
integrity sha512-XmOWe7eyHYH14cLdVPoyg+GOH3rYX++KpzrylJwSW98t3Nk+U8XOl8FWKOgwtzdb8lXGf6zYwDUzeHMWfxasyg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
jsonfile@^4.0.0:
version "4.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/jsonfile/-/jsonfile-4.0.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-m6F1R3z8jjlf2imQHS2Qez5sjKWQzbuuhuJ/FKYFRZvPE3PuHcSMVZzfsLhGVOkfd20obL5SWEBew5ShlquNxg==
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
optionalDependencies:
graceful-fs "^4.1.6"
jsonfile@^5.0.0:
version "5.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/jsonfile/-/jsonfile-5.0.0.tgz"
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
integrity sha512-NQRZ5CRo74MhMMC3/3r5g2k4fjodJ/wh8MxjFbCViWKFjxrnudWSY5vomh+23ZaXzAS7J3fBZIR2dV6WbmfM0w==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
universalify "^0.1.2"
optionalDependencies:
graceful-fs "^4.1.6"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
jsonpack@^1.1.5:
version "1.1.5"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/jsonpack/-/jsonpack-1.1.5.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-d2vwomK605ks7Q+uCpbwGyoIF5j+UZuJjlYcugISBt3CxM+eBo/W6y63yVPIyIvbYON+pvJYsYZjCYbzqJj/xQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
keyboard-key@^1.0.4:
version "1.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/keyboard-key/-/keyboard-key-1.1.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-qkBzPTi3rlAKvX7k0/ub44sqOfXeLc/jcnGGmj5c7BJpU8eDrEVPyhCvNYAaoubbsLm9uGWwQJO1ytQK1a9/dQ==
kind-of@^6.0.2:
version "6.0.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/kind-of/-/kind-of-6.0.3.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-dcS1ul+9tmeD95T+x28/ehLgd9mENa3LsvDTtzm3vyBEO7RPptvAD+t44WVXaUjTBRcrpFeFlC8WCruUR456hw==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
kleur@^3.0.3:
version "3.0.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/kleur/-/kleur-3.0.3.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-eTIzlVOSUR+JxdDFepEYcBMtZ9Qqdef+rnzWdRZuMbOywu5tO2w2N7rqjoANZ5k9vywhL6Br1VRjUIgTQx4E8w==
leven@^3.1.0:
version "3.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/leven/-/leven-3.1.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-qsda+H8jTaUaN/x5vzW2rzc+8Rw4TAQ/4KjB46IwK5VH+IlVeeeje/EoZRpiXvIqjFgK84QffqPztGI3VBLG1A==
levn@~0.3.0:
version "0.3.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/levn/-/levn-0.3.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-0OO4y2iOHix2W6ujICbKIaEQXvFQHue65vUG3pb5EUomzPI90z9hsA1VsO/dbIIpC53J8gxM9Q4Oho0jrCM/yA==
dependencies:
prelude-ls "~1.1.2"
type-check "~0.3.2"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
lines-and-columns@^1.1.6:
version "1.2.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/lines-and-columns/-/lines-and-columns-1.2.4.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-7ylylesZQ/PV29jhEDl3Ufjo6ZX7gCqJr5F7PKrqc93v7fzSymt1BpwEU8nAUXs8qzzvqhbjhK5QZg6Mt/HkBg==
loader-runner@^4.2.0:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "4.3.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/loader-runner/-/loader-runner-4.3.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-3R/1M+yS3j5ou80Me59j7F9IMs4PXs3VqRrm0TU3AbKPxlmpoY1TNscJV/oGJXo8qCatFGTfDbY6W6ipGOYXfg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
loader-utils@^2.0.0:
chore: `yarn audit-fix` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-03-01 19:35:59 +08:00
version "2.0.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/loader-utils/-/loader-utils-2.0.4.tgz"
chore: `yarn audit-fix` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-03-01 19:35:59 +08:00
integrity sha512-xXqpXoINfFhgua9xiqD8fPFHgkoq1mmmpE92WlDbm9rNRd/EbRb+Gqf908T2DMfuHjjJlksiK2RbHVOdD/MqSw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
big.js "^5.2.2"
emojis-list "^3.0.0"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
json5 "^2.1.2"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
locate-path@^5.0.0:
version "5.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/locate-path/-/locate-path-5.0.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-t7hw9pI+WvuwNJXwk5zVHpyhIqzg2qTlklJOf0mVxGSbe3Fp2VieZcduNYjaLDoy6p9uGpQEGWG87WpMKlNq8g==
dependencies:
p-locate "^4.1.0"
lodash.debounce@^4.0.8:
version "4.0.8"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/lodash.debounce/-/lodash.debounce-4.0.8.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-FT1yDzDYEoYWhnSGnpE/4Kj1fLZkDFyqRb7fNt6FdYOSxlUWAtp42Eh6Wb0rGIv/m9Bgo7x4GhQbm5Ys4SG5ow==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
lodash.memoize@4.x:
version "4.1.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/lodash.memoize/-/lodash.memoize-4.1.2.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-t7j+NzmgnQzTAYXcsHYLgimltOV1MXHtlOWf6GjL9Kj8GK5FInw5JotxvbOs+IvV1/Dzo04/fCGfLVs7aXb4Ag==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
lodash.merge@^4.6.1:
version "4.6.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/lodash.merge/-/lodash.merge-4.6.2.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-0KpjqXRVvrYyCsX1swR/XTK0va6VQkQM6MNo7PqW77ByjAhoARA8EfrP1N4+KlKj8YS0ZUCtRT/YUuhyYDujIQ==
lodash@^4.17.15, lodash@^4.17.20:
version "4.17.21"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/lodash/-/lodash-4.17.21.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-v2kDEe57lecTulaDIuNTPy3Ry4gLGJ6Z1O3vE1krgXZNrsQ+LFTGHVxVjcXPs17LhbZVGedAJv8XZ1tvj5FvSg==
loose-envify@^1.0.0, loose-envify@^1.1.0, loose-envify@^1.4.0:
version "1.4.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/loose-envify/-/loose-envify-1.4.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-lyuxPGr/Wfhrlem2CL/UcnUc1zcqKAImBDzukY7Y5F/yQiNdko6+fRLevlw1HgMySw7f611UIY408EtxRSoK3Q==
dependencies:
js-tokens "^3.0.0 || ^4.0.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
lru-cache@^6.0.0:
version "6.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/lru-cache/-/lru-cache-6.0.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-Jo6dJ04CmSjuznwJSS3pUeWmd/H0ffTlkXXgwZi+eq1UCmqQwCh+eLsYOYCwY991i2Fah4h1BEMCx4qThGbsiA==
dependencies:
yallist "^4.0.0"
make-dir@^3.0.0, make-dir@^3.0.2, make-dir@^3.1.0:
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "3.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/make-dir/-/make-dir-3.1.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-g3FeP20LNwhALb/6Cz6Dd4F2ngze0jz7tbzrD2wAV+o9FeNHe4rL+yK2md0J/fiSf1sa1ADhXqi5+oVwOM/eGw==
dependencies:
semver "^6.0.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
make-error@1.x:
version "1.3.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/make-error/-/make-error-1.3.6.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-s8UhlNe7vPKomQhC1qFelMokr/Sc3AgNbso3n74mVPA5LTZwkB9NlXf4XPamLxJE8h0gh73rM94xvwRT2CVInw==
makeerror@1.0.12:
version "1.0.12"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/makeerror/-/makeerror-1.0.12.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-JmqCvUhmt43madlpFzG4BQzG2Z3m6tvQDNKdClZnO3VbIudJYmxsT0FNJMeiB2+JTSlTQTSbU8QdesVmwJcmLg==
dependencies:
tmpl "1.0.5"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
merge-stream@^2.0.0:
version "2.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/merge-stream/-/merge-stream-2.0.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-abv/qOcuPfk3URPfDzmZU1LKmuw8kT+0nIHvKrKgFrwifol/doWcdA4ZqsWQ8ENrFKkd67Mfpo/LovbIUsbt3w==
merge2@^1.3.0:
version "1.4.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/merge2/-/merge2-1.4.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-8q7VEgMJW4J8tcfVPy8g09NcQwZdbwFEqhe/WZkoIzjn/3TGDwtOCYtXGxA3O8tPzpczCCDgv+P2P5y00ZJOOg==
micromatch@^4.0.4:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "4.0.5"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/micromatch/-/micromatch-4.0.5.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-DMy+ERcEW2q8Z2Po+WNXuw3c5YaUSFjAO5GsJqfEl7UjvtIuFKO6ZrKvcItdy98dwFI2N1tg3zNIdKaQT+aNdA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
braces "^3.0.2"
picomatch "^2.3.1"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
mime-db@1.52.0:
version "1.52.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/mime-db/-/mime-db-1.52.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-sPU4uV7dYlvtWJxwwxHD0PuihVNiE7TyAbQ5SWxDCB9mUYvOgroQOwYQQOKPJ8CIbE+1ETVlOoK1UC2nU3gYvg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
mime-types@^2.1.12, mime-types@^2.1.27:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "2.1.35"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/mime-types/-/mime-types-2.1.35.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-ZDY+bPm5zTTF+YpCrAU9nK0UgICYPT0QtT1NZWFv4s++TNkcgVaT0g6+4R2uI4MjQjzysHB1zxuWL50hzaeXiw==
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
mime-db "1.52.0"
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
mimic-fn@^2.1.0:
version "2.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/mimic-fn/-/mimic-fn-2.1.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-OqbOk5oEQeAZ8WXWydlu9HJjz9WVdEIvamMCcXmuqUYjTknH/sqsWvhQ3vgwKFRR1HpjvNBKQ37nbJgYzGqGcg==
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
minimatch@^3.0.4:
version "3.1.2"
resolved "https://registry.npmjs.org/minimatch/-/minimatch-3.1.2.tgz"
integrity sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw==
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
brace-expansion "^1.1.7"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
minimatch@^3.1.1:
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "3.1.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/minimatch/-/minimatch-3.1.2.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw==
dependencies:
brace-expansion "^1.1.7"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"minimatch@3 || 4 || 5":
version "5.1.0"
resolved "https://registry.npmjs.org/minimatch/-/minimatch-5.1.0.tgz"
integrity sha512-9TPBGGak4nHfGZsPBohm9AWg6NoT7QTCehS3BIJABslyZbzxfV78QM2Y6+i741OPZIafFAaiiEMh5OyIrJPgtg==
dependencies:
brace-expansion "^2.0.1"
feat(jest): mithril component testing (#3679) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * feat(jest): mithril component testing * fix: use separate `tsconfig.test.json` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-11 06:02:50 +08:00
mithril-query@^4.0.1:
version "4.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/mithril-query/-/mithril-query-4.0.1.tgz"
feat(jest): mithril component testing (#3679) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * feat(jest): mithril component testing * fix: use separate `tsconfig.test.json` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-11 06:02:50 +08:00
integrity sha512-OWbR6a7SsDqrlbNUsXnoiiZr62JF+oG9msOY9Xqf708dNiyBDHDtaxlTDiTKBM0uFd/yCJd6pHNMG5IViCri6A==
dependencies:
domino "2.1.6"
pretty-html-log "1.1.1"
yields-keycode "1.1.0"
chore: `yarn` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-11 06:20:14 +08:00
mithril@~2.0.4:
version "2.0.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/mithril/-/mithril-2.0.4.tgz"
chore: `yarn` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-11 06:20:14 +08:00
integrity sha512-mgw+DMZlhMS4PpprF6dl7ZoeZq5GGcAuWnrg5e12MvaGauc4jzWsDZtVGRCktsiQczOEUr2K5teKbE5k44RlOg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
mrmime@^1.0.0:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "1.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/mrmime/-/mrmime-1.0.1.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-hzzEagAgDyoU1Q6yg5uI+AorQgdvMCur3FcKf7NhMKWsaYg+RnbTyHRa/9IlLF9rf455MOCtcqqrQQ83pPP7Uw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
ms@2.1.2:
version "2.1.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==
nanoid@^3.1.30:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "3.3.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/nanoid/-/nanoid-3.3.4.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-MqBkQh/OHTS2egovRtLk45wEyNXwF+cokD+1YPf9u5VfJiRdAiRwB2froX5Co9Rh20xs4siNPm8naNotSD6RBw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
natural-compare@^1.4.0:
version "1.4.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/natural-compare/-/natural-compare-1.4.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-OWND8ei3VtNC9h7V60qff3SVobHr996CTwgxubgyQYEpg290h9J0buyECNNJexkFm5sOajh5G116RYA1c8ZMSw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
ncp@^2.0.0:
version "2.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/ncp/-/ncp-2.0.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-zIdGUrPRFTUELUvr3Gmc7KZ2Sw/h1PiVM0Af/oHB6zgnV1ikqSfRk+TOufi79aHYCW3NiOXmr1BP5nWbzojLaA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
neo-async@^2.6.2:
version "2.6.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/neo-async/-/neo-async-2.6.2.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-Yd3UES5mWCSqR+qNT93S3UoYUkqAZ9lLg8a7g9rimsWmYGK8cVToA4/sF3RrshdyV3sAGMXVUmpMYOw+dLpOuw==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
node-int64@^0.4.0:
version "0.4.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/node-int64/-/node-int64-0.4.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-O5lz91xSOeoXP6DulyHfllpq+Eg00MWitZIbtPfoSEvqIHdl5gfcY6hYzDWnj0qD5tz52PI08u9qUvSVeUBeHw==
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
node-releases@^2.0.6:
version "2.0.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/node-releases/-/node-releases-2.0.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-PiVXnNuFm5+iYkLBNeq5211hvO38y63T0i2KKh2KnUs3RpzJ+JtODFjkD8yjLwnDkTYF1eKXheUwdssR+NRZdg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
normalize-package-data@^2.5.0:
version "2.5.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.5.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-/5CMN3T0R4XTj4DcGaexo+roZSdSFW/0AOOTROrjxzCG1wrWXEsGbRKevjlIL+ZDE4sZlJr5ED4YW0yqmkK+eA==
dependencies:
hosted-git-info "^2.1.4"
resolve "^1.10.0"
semver "2 || 3 || 4 || 5"
validate-npm-package-license "^3.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
normalize-path@^3.0.0, normalize-path@3:
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "3.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/normalize-path/-/normalize-path-3.0.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-6eZs5Ls3WtCisHWp9S2GUy8dqkpGi4BVSz3GaqiE6ezub0512ESztXUwUB6C6IKbQkY2Pnb/mD4WYojCRwcwLA==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
npm-run-path@^4.0.1:
version "4.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/npm-run-path/-/npm-run-path-4.0.1.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-S48WzZW777zhNIrn7gxOlISNAqi9ZC/uQFnRdbeIHhZhCA6UqpkOT8T1G7BvfdgP4Er8gF4sUbaS0i7QvIfCWw==
dependencies:
path-key "^3.0.0"
nwsapi@^2.2.2:
version "2.2.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/nwsapi/-/nwsapi-2.2.2.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-90yv+6538zuvUMnN+zCr8LuV6bPFdq50304114vJYJ8RDyK8D5O9Phpbd6SZWgI7PwzmmfN1upeOJlvybDSgCw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
object-assign@^4.1.1:
version "4.1.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/object-assign/-/object-assign-4.1.1.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-rJgTQnkUnH1sFw8yT6VSU3zD3sWmu6sZhIseY8VX+GRu3P6F7Fu+JNDoXfklElbLJSnc3FUQHVe4cU5hj+BcUg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
object-is@^1.0.1:
version "1.1.5"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/object-is/-/object-is-1.1.5.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-3cyDsyHgtmi7I7DfSSI2LDp6SK2lwvtbg0p0R1e0RvTqF5ceGx+K2dfSjm1bKDMVCFEDAQvy+o8c6a7VujOddw==
dependencies:
call-bind "^1.0.2"
define-properties "^1.1.3"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
object-keys@^1.1.1:
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "1.1.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/object-keys/-/object-keys-1.1.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-NuAESUOUMrlIXOfHKzD6bpPu3tYt3xvjNdRIQ+FeT0lNb4K8WR70CaDxhuNguS2XG+GjkyMwOzsN5ZktImfhLA==
once@^1.3.0:
version "1.4.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/once/-/once-1.4.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-lNaJgI+2Q5URQBkccEKHTQOPaXdUxnZZElQTZY0MFUAuaEqe1E+Nyvgdz/aIyNi6Z9MzO5dv1H8n58/GELp3+w==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
wrappy "1"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
onetime@^5.1.2:
version "5.1.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/onetime/-/onetime-5.1.2.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-kbpaSSGJTWdAY5KPVeMOKXSrPtr8C8C7wodJbcsd51jRnmD+GZu8Y0VoU6Dm5Z4vWr0Ig/1NKuWRKf7j5aaYSg==
dependencies:
mimic-fn "^2.1.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
opener@^1.5.2:
version "1.5.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/opener/-/opener-1.5.2.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-ur5UIdyw5Y7yEj9wLzhqXiy6GZ3Mwx0yGI+5sMn2r0N0v3cKJvUmFH5yPP+WXh9e0xfyzyJX95D8l088DNFj7A==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
optionator@^0.8.1:
version "0.8.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/optionator/-/optionator-0.8.3.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-+IW9pACdk3XWmmTXG8m3upGUJst5XRGzxMRjXzAuJ1XnIFNvfhjjIuYkDvysnPQ7qzqVzLt78BCruntqRhWQbA==
dependencies:
deep-is "~0.1.3"
fast-levenshtein "~2.0.6"
levn "~0.3.0"
prelude-ls "~1.1.2"
type-check "~0.3.2"
word-wrap "~1.2.3"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
p-limit@^2.2.0:
version "2.3.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/p-limit/-/p-limit-2.3.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-//88mFWSJx8lxCzwdAABTJL2MyWB12+eIY7MDL2SqLmAkeKU9qxRvWuSyTjm3FUmpBEMuFfckAIqEaVGUDxb6w==
dependencies:
p-try "^2.0.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
p-limit@^3.1.0:
version "3.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/p-limit/-/p-limit-3.1.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-TYOanM3wGwNGsZN2cVTYPArw454xnXj5qmWF1bEoAc4+cU/ol7GVh7odevjp1FNHduHc3KZMcFduxU5Xc6uJRQ==
dependencies:
yocto-queue "^0.1.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
p-locate@^4.1.0:
version "4.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/p-locate/-/p-locate-4.1.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-R79ZZ/0wAxKGu3oYMlz8jy/kbhsNrS7SKZ7PxEHBgJ5+F2mtFW2fK2cOtBh1cHYkQsbzFV7I+EoRKe6Yt0oK7A==
dependencies:
p-limit "^2.2.0"
p-try@^2.0.0:
version "2.2.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/p-try/-/p-try-2.2.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-R4nPAVTAU0B9D35/Gk3uJf/7XYbQcyohSKdvAxIRSNghFl4e71hVoGnBNQz9cWaXxO2I10KTC+3jMdvvoKw6dQ==
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
parent-module@^1.0.0:
version "1.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/parent-module/-/parent-module-1.0.1.tgz"
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
integrity sha512-GQ2EWRpQV8/o+Aw8YqtfZZPfNRWZYkbidE9k5rpl/hC3vtHHBfGm2Ifi6qWV+coDGkrUKZAxE3Lot5kcsRlh+g==
dependencies:
callsites "^3.0.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
parse-json@^5.0.0, parse-json@^5.2.0:
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "5.2.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/parse-json/-/parse-json-5.2.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-ayCKvm/phCGxOkYRSCM82iDwct8/EonSEgCSxWxD7ve6jHggsFl4fZVQBPRNgQoKiuV/odhFrGzQXZwbifC8Rg==
dependencies:
"@babel/code-frame" "^7.0.0"
error-ex "^1.3.1"
json-parse-even-better-errors "^2.3.0"
lines-and-columns "^1.1.6"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
parse5@^7.0.0, parse5@^7.1.1:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
version "7.1.2"
resolved "https://registry.npmjs.org/parse5/-/parse5-7.1.2.tgz"
integrity sha512-Czj1WaSVpaoj0wbhMzLmWD69anp2WH7FXMB9n1Sy8/ZFF9jolSQVMu1Ij5WIyGmcBmhk7EOndpO4mIpihVqAXw==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
entities "^4.4.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
path-exists@^4.0.0:
version "4.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/path-exists/-/path-exists-4.0.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-ak9Qy5Q7jYb2Wwcey5Fpvg2KoAc/ZIhLSLOSBmRmygPsGwkVVt0fZa0qrtMz+m6tJTAHfZQ8FnmB4MG4LWy7/w==
path-is-absolute@^1.0.0:
version "1.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.1.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-AVbw3UJ2e9bq64vSaS9Am0fje1Pa8pbGqTTsmXfaIiMpnr5DlDhfJOuLj9Sf95ZPVDAUerDfEk88MPmPe7UCQg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
path-key@^3.0.0, path-key@^3.1.0:
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "3.1.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/path-key/-/path-key-3.1.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-ojmeN0qd+y0jszEtoY48r0Peq5dwMEkIlCOu6Q5f41lfkswXuKtYrhgoTpLnyIcHm24Uhqx+5Tqm2InSwLhE6Q==
path-parse@^1.0.7:
version "1.0.7"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/path-parse/-/path-parse-1.0.7.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-LDJzPVEEEPR+y48z93A0Ed0yXb8pAByGWo/k5YYdYgpY2/2EsOsksJrq7lOHxryrVOn1ejG6oAp8ahvOIQD8sw==
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
path-type@^4.0.0:
version "4.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/path-type/-/path-type-4.0.0.tgz"
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
integrity sha512-gDKb8aZMDeD/tZWs9P6+q0J9Mwkdl6xMV8TjnGP3qJVJ06bdMgkbBlLU8IdfOsIsFz2BW1rNVT3XuNEl8zPAvw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
picocolors@^1.0.0:
version "1.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/picocolors/-/picocolors-1.0.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-1fygroTLlHu66zi26VoTDv8yRgm0Fccecssto+MhsZ0D/DGW2sm8E8AjW7NU5VVTRt5GxbeZ5qBuJr+HyLYkjQ==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
picomatch@^2.0.4, picomatch@^2.2.3, picomatch@^2.3.1:
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "2.3.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/picomatch/-/picomatch-2.3.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-JU3teHTNjmE2VCGFzuY8EXzCDVwEqB2a8fsIvwaStHhAWJEeVd1o1QD80CU6+ZdEXXSLbSsuLwJjkCBWqRQUVA==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
pirates@^4.0.4:
version "4.0.5"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/pirates/-/pirates-4.0.5.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-8V9+HQPupnaXMA23c5hvl69zXvTwTzyAYasnkb0Tts4XvO4CliqONMOnvlq26rkhLC3nWDFBJf73LU1e1VZLaQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
pkg-dir@^4.1.0, pkg-dir@^4.2.0:
version "4.2.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/pkg-dir/-/pkg-dir-4.2.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-HRDzbaKjC+AOWVXxAU/x54COGeIv9eb+6CkDSQoNTt4XyWoIJvuPsXizxu/Fr23EiekbtZwmh1IcIG/l/a10GQ==
dependencies:
find-up "^4.0.0"
popper.js@^1.14.4:
version "1.16.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/popper.js/-/popper.js-1.16.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-Wb4p1J4zyFTbM+u6WuO4XstYx4Ky9Cewe4DWrel7B0w6VVICvPwdOpotjzcf6eD8TsckVnIMNONQyPIUFOUbCQ==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
prelude-ls@~1.1.2:
version "1.1.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/prelude-ls/-/prelude-ls-1.1.2.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-ESF23V4SKG6lVSGZgYNpbsiaAkdab6ZgOxe52p7+Kid3W3u3bxR4Vfd/o21dmN7jSt0IwgZ4v5MUd26FEtXE9w==
feat(jest): mithril component testing (#3679) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * feat(jest): mithril component testing * fix: use separate `tsconfig.test.json` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-11 06:02:50 +08:00
prettier@^1.18.2:
version "1.19.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/prettier/-/prettier-1.19.1.tgz"
feat(jest): mithril component testing (#3679) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * feat(jest): mithril component testing * fix: use separate `tsconfig.test.json` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-11 06:02:50 +08:00
integrity sha512-s7PoyDv/II1ObgQunCbB9PdLmUcBZcnWOcxDh7O0N/UwDEsHyqkW+Qh28jW+mVuCdx7gLB0BotYI1Y6uI9iyew==
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
prettier@^2.4.1, prettier@^2.5.1, prettier@^2.7.1:
feat(jest): mithril component testing (#3679) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * feat(jest): mithril component testing * fix: use separate `tsconfig.test.json` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-11 06:02:50 +08:00
version "2.7.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/prettier/-/prettier-2.7.1.tgz"
feat(jest): mithril component testing (#3679) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * feat(jest): mithril component testing * fix: use separate `tsconfig.test.json` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-11 06:02:50 +08:00
integrity sha512-ujppO+MkdPqoVINuDFDRLClm7D78qbDt0/NR+wp5FqEZOoTNAjPHWj17QRhu7geIHJfcNhRk1XVQmF8Bp3ye+g==
chore: enable and set up prettier for `flarum/tags` (#3496)
2022-06-20 20:00:01 +08:00
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
pretty-bytes@^6.0.0:
version "6.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/pretty-bytes/-/pretty-bytes-6.0.0.tgz"
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
integrity sha512-6UqkYefdogmzqAZWzJ7laYeJnaXDy2/J+ZqiiMtS7t7OfpXWTlaeGMwX8U6EFvPV/YWWEKRkS8hKS4k60WHTOg==
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
pretty-format@^29.0.0, pretty-format@^29.5.0:
version "29.5.0"
resolved "https://registry.npmjs.org/pretty-format/-/pretty-format-29.5.0.tgz"
integrity sha512-V2mGkI31qdttvTFX7Mt4efOqHXqJWMu4/r66Xh3Z3BwZaPfPJgp6/gbwoujRpPUtfEF6AUUWx3Jim3GCw5g/Qw==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"@jest/schemas" "^29.4.3"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
ansi-styles "^5.0.0"
react-is "^18.0.0"
feat(jest): mithril component testing (#3679) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * feat(jest): mithril component testing * fix: use separate `tsconfig.test.json` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-11 06:02:50 +08:00
pretty-html-log@1.1.1:
version "1.1.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/pretty-html-log/-/pretty-html-log-1.1.1.tgz"
feat(jest): mithril component testing (#3679) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * feat(jest): mithril component testing * fix: use separate `tsconfig.test.json` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-11 06:02:50 +08:00
integrity sha512-7Ai/cBk764SmU9vmJL/B7wzcWu7MIQflJ0Yx1cL/kPHZXkyn7AY1Tqtfgrjo9P750G7nsSDfk12FQ+mQKqQUvg==
dependencies:
chalk "^2.4.2"
commander "^3.0.2"
prettier "^1.18.2"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
prompts@^2.0.1:
version "2.4.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/prompts/-/prompts-2.4.2.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-NxNv/kLguCA7p3jE8oL2aEBsrJWgAakBpgmgK6lpPWV+WuOmY6r2/zbAVnP+T8bQlA0nzHXSJSJW0Hq7ylaD2Q==
dependencies:
kleur "^3.0.3"
sisteransi "^1.0.5"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
prop-types@^15.0.0, prop-types@^15.6.1, prop-types@^15.6.2, prop-types@^15.7.2:
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "15.8.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/prop-types/-/prop-types-15.8.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-oj87CgZICdulUohogVAR7AjlC0327U4el4L6eAvOqCeudMDVU0NThNaV+b9Df4dXgSP1gXMTnPdhfe/2qDH5cg==
dependencies:
loose-envify "^1.4.0"
object-assign "^4.1.1"
react-is "^16.13.1"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
psl@^1.1.33:
version "1.9.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/psl/-/psl-1.9.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-E/ZsdU4HLs/68gYzgGTkMicWTLPdAftJLfJFlLUAAKZGkStNU72sZjT66SnMDVOfOWY/YAoiD7Jxa9iHvngcag==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
punycode@^2.1.0, punycode@^2.1.1:
version "2.1.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/punycode/-/punycode-2.1.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-XRsRjdf+j5ml+y/6GKHPZbrF/8p2Yga0JPtdqTIY2Xe5ohJPD9saDJJLPvp9+NSBprVvevdXZybnj2cv8OEd0A==
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
pure-rand@^6.0.0:
version "6.0.1"
resolved "https://registry.npmjs.org/pure-rand/-/pure-rand-6.0.1.tgz"
integrity sha512-t+x1zEHDjBwkDGY5v5ApnZ/utcd4XYDiJsaQQoptTXgUXX95sDg1elCdJghzicm7n2mbCBJ3uYWr6M22SO19rg==
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
pusher-js@*:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
version "7.5.0"
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@types/node" "^14.14.31"
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
tweetnacl "^1.0.3"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
querystringify@^2.1.1:
version "2.2.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/querystringify/-/querystringify-2.2.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-FIqgj2EUvTa7R50u0rGsyTftzjYmv/a3hO345bZNrqabNqjtgiDMgmo4mkUjd+nzU5oF3dClKqFIPUKybUyqoQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
queue-microtask@^1.2.2:
version "1.2.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/queue-microtask/-/queue-microtask-1.2.3.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-NuaNSa6flKT5JaSYQzJok04JzTL1CA6aGhv5rfLW3PgqA+M2ChpZQnAC8h8i4ZFkBS8X5RqkDBHA7r4hej3K9A==
randombytes@^2.1.0:
version "2.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/randombytes/-/randombytes-2.1.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-vYl3iOX+4CKUWuxGi9Ukhie6fsqXqS9FE2Zaic4tNFD2N2QQaXOMFbuKK4QmDHC0JO6B1Zp41J0LpT0oR68amQ==
dependencies:
safe-buffer "^5.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"react-dom@^16.0.0 || ^17.0.0 || ^18.0.0", react-dom@^16.13.1, react-dom@^16.8.0:
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "16.14.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/react-dom/-/react-dom-16.14.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-1gCeQXDLoIqMgqD3IO2Ah9bnf0w9kzhwN5q4FGnHZ67hBm9yePzB5JJAIQCc8x3pFnNlwFq4RidZggNAAkzWWw==
dependencies:
loose-envify "^1.1.0"
object-assign "^4.1.1"
prop-types "^15.6.2"
scheduler "^0.19.1"
react-is@^16.13.1, react-is@^16.6.3, react-is@^16.8.6:
version "16.13.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/react-is/-/react-is-16.13.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-24e6ynE2H+OKt4kqsOvNd8kBpV65zoxbA4BVsEOB3ARVWQki/DHzaUoC5KuON/BiccDaCCTZBuOcfZs70kR8bQ==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
react-is@^18.0.0:
version "18.2.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/react-is/-/react-is-18.2.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-xWGDIW6x921xtzPkhiULtthJHoJvBbF3q26fzloPCK0hsvxtPVelvftw3zjbHWSkR2km9Z+4uxbDDK/6Zw9B8w==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
react-popper@^1.3.4:
version "1.3.11"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/react-popper/-/react-popper-1.3.11.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-VSA/bS+pSndSF2fiasHK/PTEEAyOpX60+H5EPAjoArr8JGm+oihu4UbrqcEBpQibJxBVCpYyjAX7abJ+7DoYVg==
dependencies:
"@babel/runtime" "^7.1.2"
"@hypnosphi/create-react-context" "^0.3.1"
deep-equal "^1.1.1"
popper.js "^1.14.4"
prop-types "^15.6.1"
typed-styles "^0.0.7"
warning "^4.0.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"react@^16.0.0 || ^17.0.0 || ^18.0.0", react@^16.13.1, react@^16.14.0, react@^16.8.0, react@>=0.14.0, "react@0.14.x || ^15.0.0 || ^16.0.0 || ^17.0.0":
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "16.14.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/react/-/react-16.14.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-0X2CImDkJGApiAlcf0ODKIneSwBPhqJawOa5wCtKbu7ZECrmS26NvtSILynQ66cgkT/RJ4LidJOc3bUESwmU8g==
dependencies:
loose-envify "^1.1.0"
object-assign "^4.1.1"
prop-types "^15.6.2"
read-pkg-up@^7.0.1:
version "7.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-7.0.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-zK0TB7Xd6JpCLmlLmufqykGE+/TlOePD6qKClNW7hHDKFh/J7/7gCWGR7joEQEW1bKq3a3yUZSObOoWLFQ4ohg==
dependencies:
find-up "^4.1.0"
read-pkg "^5.2.0"
type-fest "^0.8.1"
read-pkg@^5.2.0:
version "5.2.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/read-pkg/-/read-pkg-5.2.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-Ug69mNOpfvKDAc2Q8DRpMjjzdtrnv9HcSMX+4VsZxD1aZ6ZzrIE7rlzXBtWTyhULSMKg076AW6WR5iZpD0JiOg==
dependencies:
"@types/normalize-package-data" "^2.4.0"
normalize-package-data "^2.5.0"
parse-json "^5.0.0"
type-fest "^0.6.0"
rechoir@^0.7.0:
version "0.7.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/rechoir/-/rechoir-0.7.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-/njmZ8s1wVeR6pjTZ+0nCnv8SpZNRMT2D1RLOJQESlYFDBvwpTA4KWJpZ+sBJ4+vhjILRcK7JIFdGCdxEAAitg==
dependencies:
resolve "^1.9.0"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
regenerate-unicode-properties@^10.1.0:
version "10.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/regenerate-unicode-properties/-/regenerate-unicode-properties-10.1.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-d1VudCLoIGitcU/hEg2QqvyGZQmdC0Lf8BqdOMXGFSvJP4bNV1+XqbPQeHHLD51Jh4QJJ225dlIFvY4Ly6MXmQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
regenerate "^1.4.2"
regenerate@^1.4.2:
version "1.4.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/regenerate/-/regenerate-1.4.2.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-zrceR/XhGYU/d/opr2EKO7aRHUeiBI8qjtfHqADTwZd6Szfy16la6kqD0MIUs5z5hx6AaKa+PixpPrR289+I0A==
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
regenerator-runtime@^0.13.10:
feat(jest): mithril component testing (#3679) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * feat(jest): mithril component testing * fix: use separate `tsconfig.test.json` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-11 06:02:50 +08:00
version "0.13.10"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/regenerator-runtime/-/regenerator-runtime-0.13.10.tgz"
feat(jest): mithril component testing (#3679) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * feat(jest): mithril component testing * fix: use separate `tsconfig.test.json` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-11 06:02:50 +08:00
integrity sha512-KepLsg4dU12hryUO7bp/axHAKvwGOCV0sGloQtpagJ12ai+ojVDqkeGSiRX1zlq+kjIMZ1t7gpze+26QqtdGqw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
regenerator-transform@^0.15.0:
feat(jest): mithril component testing (#3679) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * feat(jest): mithril component testing * fix: use separate `tsconfig.test.json` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-11 06:02:50 +08:00
version "0.15.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/regenerator-transform/-/regenerator-transform-0.15.0.tgz"
feat(jest): mithril component testing (#3679) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * feat(jest): mithril component testing * fix: use separate `tsconfig.test.json` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-11 06:02:50 +08:00
integrity sha512-LsrGtPmbYg19bcPHwdtmXwbW+TqNvtY4riE3P83foeHRroMbH6/2ddFBfab3t7kbzc7v7p4wbkIecHImqt0QNg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
"@babel/runtime" "^7.8.4"
regexp.prototype.flags@^1.2.0:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "1.4.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/regexp.prototype.flags/-/regexp.prototype.flags-1.4.3.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-fjggEOO3slI6Wvgjwflkc4NFRCTZAu5CnNfBd5qOMYhWdn67nJBBu34/TkD++eeFmd8C9r9jfXJ27+nSiRkSUA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
call-bind "^1.0.2"
define-properties "^1.1.3"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
functions-have-names "^1.2.2"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
regexpu-core@^5.1.0:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
version "5.2.2"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
regenerate "^1.4.2"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
regenerate-unicode-properties "^10.1.0"
regjsgen "^0.7.1"
regjsparser "^0.9.1"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
unicode-match-property-ecmascript "^2.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
unicode-match-property-value-ecmascript "^2.1.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
regjsgen@^0.7.1:
version "0.7.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/regjsgen/-/regjsgen-0.7.1.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-RAt+8H2ZEzHeYWxZ3H2z6tF18zyyOnlcdaafLrm21Bguj7uZy6ULibiAFdXEtKQY4Sy7wDTwDiOazasMLc4KPA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
regjsparser@^0.9.1:
version "0.9.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/regjsparser/-/regjsparser-0.9.1.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-dQUtn90WanSNl+7mQKcXAgZxvUe7Z0SqXlgzv0za4LwiUhyzBC58yQO3liFoUgu8GiJVInAhJjkj1N0EtQ5nkQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
jsesc "~0.5.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
require-directory@^2.1.1:
version "2.1.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/require-directory/-/require-directory-2.1.1.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-fGxEI7+wsG9xrvdjsrlmL22OMTTiHRwAMroiEeMgq8gzoLC/PQr7RsRDSTLUg/bZAZtF+TVIkHc6/4RIKrui+Q==
requires-port@^1.0.0:
version "1.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/requires-port/-/requires-port-1.0.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-KigOCHcocU3XODJxsu8i/j8T9tzT4adHiecwORRQ0ZZFcp7ahwXuRU1m+yuO90C5ZUyGeGfocHDI14M3L3yDAQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
resolve-cwd@^3.0.0:
version "3.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/resolve-cwd/-/resolve-cwd-3.0.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-OrZaX2Mb+rJCpH/6CpSqt9xFVpN++x01XnN2ie9g6P5/3xelLAkXWVADpdz1IHD/KFfEXyE6V0U01OQ3UO2rEg==
dependencies:
resolve-from "^5.0.0"
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
resolve-from@^4.0.0:
version "4.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/resolve-from/-/resolve-from-4.0.0.tgz"
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
integrity sha512-pb/MYmXstAkysRFx8piNI1tGFNQIFA3vkE3Gq4EuA1dF6gHp/+vgZqsCGJapvy8N3Q+4o7FwvquPJcnZ7RYy4g==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
resolve-from@^5.0.0:
version "5.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/resolve-from/-/resolve-from-5.0.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-qYg9KP24dD5qka9J47d0aVky0N+b4fTU89LN9iDnjB5waksiC49rvMB0PrUJQGoTmH50XPiqOvAjDfaijGxYZw==
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolve.exports@^2.0.0:
version "2.0.1"
resolved "https://registry.npmjs.org/resolve.exports/-/resolve.exports-2.0.1.tgz"
integrity sha512-OEJWVeimw8mgQuj3HfkNl4KqRevH7lzeQNaWRPfx0PPse7Jk6ozcsG4FKVgtzDsC1KUF+YlTHh17NcgHOPykLw==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
resolve@^1.10.0, resolve@^1.14.2, resolve@^1.20.0, resolve@^1.9.0:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "1.22.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/resolve/-/resolve-1.22.1.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-nBpuuYuY5jFsli/JIs1oldw6fOQCBioohqWZg/2hiaOybXOft4lonv85uDOKXdf8rhyK159cxU5cDcK/NKk8zw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
is-core-module "^2.9.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
path-parse "^1.0.7"
supports-preserve-symlinks-flag "^1.0.0"
reusify@^1.0.4:
version "1.0.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/reusify/-/reusify-1.0.4.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-U9nH88a3fc/ekCF1l0/UP1IosiuIjyTh7hBvXVMHYgVcfGvt897Xguj2UOLDeI5BG2m7/uwyaLVT6fbtCwTyzw==
rimraf@^3.0.2:
version "3.0.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/rimraf/-/rimraf-3.0.2.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-JZkJMZkAGFFPP2YqXZXPbMlMBgsxzE8ILs4lMIX/2o0L9UBw9O/Y3o6wFw/i9YLapcUJWwqbi3kdxIPdC62TIA==
dependencies:
glob "^7.1.3"
run-parallel@^1.1.9:
version "1.2.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/run-parallel/-/run-parallel-1.2.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-5l4VyZR86LZ/lDxZTR6jqL8AFE2S0IFLMP26AbjsLVADxHdhB/c0GUsH+y39UfCi3dzz8OlQuPmnaJOMoDHQBA==
dependencies:
queue-microtask "^1.2.2"
safe-buffer@^5.1.0:
version "5.2.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/safe-buffer/-/safe-buffer-5.2.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-rp3So07KcdmmKbGvgaNxQSJr7bGVSVk5S9Eq1F+ppbRo70+YeaDxkw5Dd8NPN+GD6bjnYm2VuPuCXmpuYvmCXQ==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
"safer-buffer@>= 2.1.2 < 3.0.0":
version "2.1.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/safer-buffer/-/safer-buffer-2.1.2.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-YZo3K82SD7Riyi0E1EQPojLz7kpepnSQI9IyPbHHg1XXXevb5dJI7tpyN2ADxGcQbHG7vcyRHk0cbwqcQriUtg==
saxes@^6.0.0:
version "6.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/saxes/-/saxes-6.0.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-xAg7SOnEhrm5zI3puOOKyy1OMcMlIJZYNJY7xLBwSze0UjhPLnWfj2GF2EpT0jmzaJKIWKHLsaSSajf35bcYnA==
dependencies:
xmlchars "^2.2.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
scheduler@^0.19.1:
version "0.19.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/scheduler/-/scheduler-0.19.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-n/zwRWRYSUj0/3g/otKDRPMh6qv2SYMWNq85IEa8iZyAv8od9zDYpGSnpBEjNgcMNq6Scbu5KfIPxNF72R/2EA==
dependencies:
loose-envify "^1.1.0"
object-assign "^4.1.1"
schema-utils@^2.6.5:
version "2.7.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/schema-utils/-/schema-utils-2.7.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-SHiNtMOUGWBQJwzISiVYKu82GiV4QYGePp3odlY1tuKO7gPtphAT5R/py0fA6xtbgLL/RvtJZnU9b8s0F1q0Xg==
dependencies:
"@types/json-schema" "^7.0.5"
ajv "^6.12.4"
ajv-keywords "^3.5.2"
schema-utils@^3.1.0, schema-utils@^3.1.1:
version "3.1.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/schema-utils/-/schema-utils-3.1.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-Y5PQxS4ITlC+EahLuXaY86TXfR7Dc5lw294alXOq86JAHCihAIZfqv8nNCWvaEJvaC51uN9hbLGeV0cFBdH+Fw==
dependencies:
"@types/json-schema" "^7.0.8"
ajv "^6.12.5"
ajv-keywords "^3.5.2"
semantic-ui-react@^0.88.2:
version "0.88.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/semantic-ui-react/-/semantic-ui-react-0.88.2.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-+02kN2z8PuA/cMdvDUsHhbJmBzxxgOXVHMFr9XK7zGb0wkW9A6OPQMFokWz7ozlVtKjN6r7zsb+Qvjk/qq1OWw==
dependencies:
"@babel/runtime" "^7.1.2"
"@semantic-ui-react/event-stack" "^3.1.0"
"@stardust-ui/react-component-event-listener" "~0.38.0"
"@stardust-ui/react-component-ref" "~0.38.0"
classnames "^2.2.6"
keyboard-key "^1.0.4"
lodash "^4.17.15"
prop-types "^15.7.2"
react-is "^16.8.6"
react-popper "^1.3.4"
shallowequal "^1.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
semver@^6.0.0, semver@^6.1.1, semver@^6.1.2, semver@^6.3.0:
version "6.3.0"
resolved "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz"
integrity sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==
semver@^7.3.5:
version "7.3.8"
resolved "https://registry.npmjs.org/semver/-/semver-7.3.8.tgz"
integrity sha512-NB1ctGL5rlHrPJtFDVIVzTyQylMLu9N9VICA6HSFJo8MCGVTMW6gfpicwKmmK/dAjTOrqu5l63JJOpDSrAis3A==
dependencies:
lru-cache "^6.0.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
"semver@2 || 3 || 4 || 5":
version "5.7.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/semver/-/semver-5.7.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-sauaDf/PZdVgrLTNYHRtpXa1iRiKcaebiKQ1BJdpQlWH2lCvexQdX55snPFyK7QzpudqbCI0qXFfOasHdyNDGQ==
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
semver@7.x:
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
version "7.3.8"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/semver/-/semver-7.3.8.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-NB1ctGL5rlHrPJtFDVIVzTyQylMLu9N9VICA6HSFJo8MCGVTMW6gfpicwKmmK/dAjTOrqu5l63JJOpDSrAis3A==
dependencies:
lru-cache "^6.0.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
serialize-javascript@^6.0.0:
version "6.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/serialize-javascript/-/serialize-javascript-6.0.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-Qr3TosvguFt8ePWqsvRfrKyQXIiW+nGbYpy8XK24NQHE83caxWt+mIymTT19DGFbNWNLfEwsrkSmN64lVWB9ag==
dependencies:
randombytes "^2.1.0"
shallow-clone@^3.0.0:
version "3.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/shallow-clone/-/shallow-clone-3.0.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-/6KqX+GVUdqPuPPd2LxDDxzX6CAbjJehAAOKlNpqqUpAqPM6HeL8f+o3a+JsyGjn2lv0WY8UsTgUJjU9Ok55NA==
dependencies:
kind-of "^6.0.2"
shallowequal@^1.1.0:
version "1.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/shallowequal/-/shallowequal-1.1.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-y0m1JoUZSlPAjXVtPPW70aZWfIL/dSP7AFkRnniLCrK/8MDKog3TySTBmckD+RObVxH0v4Tox67+F14PdED2oQ==
shebang-command@^2.0.0:
version "2.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/shebang-command/-/shebang-command-2.0.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-kHxr2zZpYtdmrN1qDjrrX/Z1rR1kG8Dx+gkpK1G4eXmvXswmcE1hTWBWYUzlraYw1/yZp6YuDY77YtvbN0dmDA==
dependencies:
shebang-regex "^3.0.0"
shebang-regex@^3.0.0:
version "3.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/shebang-regex/-/shebang-regex-3.0.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-7++dFhtcx3353uBaq8DDR4NuxBetBzC7ZQOhmTQInHEd6bSrXdiEyzCvG07Z44UYdLShWUyXt5M/yhz8ekcb1A==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
signal-exit@^3.0.3, signal-exit@^3.0.7:
version "3.0.7"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/signal-exit/-/signal-exit-3.0.7.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-wnD2ZE+l+SPC/uoS0vXeE9L1+0wuaMqKlfz9AMUo38JsyLSBWSFcHR1Rri62LZc12vLr1gb3jl7iwQhgwpAbGQ==
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
simple-emoji-map@^0.5.1:
version "0.5.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/simple-emoji-map/-/simple-emoji-map-0.5.1.tgz"
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
integrity sha512-IBi769OaG3BjXCu0WnweB50OcRgQ18HJMZ1bFdzWits8lepmbgGgCdKF+preHiIAqa+wQyff1nAVVydOXrIhng==
dependencies:
chalk "^4.1.2"
cosmiconfig "^7.0.1"
emojibase-data "^7.0.1"
twemoji "^14.0.2"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
sirv@^1.0.7:
version "1.0.19"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/sirv/-/sirv-1.0.19.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-JuLThK3TnZG1TAKDwNIqNq6QA2afLOCcm+iE8D1Kj3GA40pSPsxQjjJl0J8X3tsR7T+CP1GavpzLwYkgVLWrZQ==
dependencies:
"@polka/url" "^1.0.0-next.20"
mrmime "^1.0.0"
totalist "^1.0.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
sisteransi@^1.0.5:
version "1.0.5"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/sisteransi/-/sisteransi-1.0.5.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-bLGGlR1QxBcynn2d5YmDX4MGjlZvy2MRBDRNHLJ8VI6l6+9FUiyTFNJ0IveOSP0bcXgVDPRcfGqA0pjaqUpfVg==
slash@^3.0.0:
version "3.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/slash/-/slash-3.0.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-g9Q1haeby36OSStwb4ntCGGGaKsaVSjQ68fBxoQcutl5fS1vuY18H3wSt3jFyFtrkx+Kz0V1G85A4MyAdDMi2Q==
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
sortablejs@^1.14.0:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "1.15.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/sortablejs/-/sortablejs-1.15.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-bv9qgVMjUMf89wAvM6AxVvS/4MX3sPeN0+agqShejLU5z5GX4C75ow1O2e5k4L6XItUyAK3gH6AxSbXrOM5e8w==
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
source-map-support@~0.5.20:
version "0.5.21"
resolved "https://registry.npmjs.org/source-map-support/-/source-map-support-0.5.21.tgz"
integrity sha512-uBHU3L3czsIyYXKX88fdrGovxdSCoTGDRZ6SYXtSRxLZUzHg5P/66Ht6uoUlHu9EZod+inXhKo3qQgwXUT/y1w==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
buffer-from "^1.0.0"
source-map "^0.6.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
source-map-support@0.5.13:
version "0.5.13"
resolved "https://registry.npmjs.org/source-map-support/-/source-map-support-0.5.13.tgz"
integrity sha512-SHSKFHadjVA5oR4PPqhtAVdcBWwRYVd6g6cAXnIbRiIwc2EhPrTuKUBdSLvlEKyIP3GCf89fltvcZiP9MMFA1w==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
buffer-from "^1.0.0"
source-map "^0.6.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
source-map@^0.6.0, source-map@^0.6.1, source-map@~0.6.1:
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "0.6.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/source-map/-/source-map-0.6.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-UjgapumWlbMhkBgzT7Ykc5YXUT46F0iKu8SGXq0bcwP5dz/h0Plj6enJqjz1Zbq2l5WaqYnrVbwWOWMyF3F47g==
spdx-correct@^3.0.0:
version "3.1.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/spdx-correct/-/spdx-correct-3.1.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-cOYcUWwhCuHCXi49RhFRCyJEK3iPj1Ziz9DpViV3tbZOwXD49QzIN3MpOLJNxh2qwq2lJJZaKMVw9qNi4jTC0w==
dependencies:
spdx-expression-parse "^3.0.0"
spdx-license-ids "^3.0.0"
spdx-exceptions@^2.1.0:
version "2.3.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-2.3.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-/tTrYOC7PPI1nUAgx34hUpqXuyJG+DTHJTnIULG4rDygi4xu/tfgmq1e1cIRwRzwZgo4NLySi+ricLkZkw4i5A==
spdx-expression-parse@^3.0.0:
version "3.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-3.0.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-cbqHunsQWnJNE6KhVSMsMeH5H/L9EpymbzqTQ3uLwNCLZ1Q481oWaofqH7nO6V07xlXwY6PhQdQ2IedWx/ZK4Q==
dependencies:
spdx-exceptions "^2.1.0"
spdx-license-ids "^3.0.0"
spdx-license-ids@^3.0.0:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "3.0.12"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-3.0.12.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-rr+VVSXtRhO4OHbXUiAF7xW3Bo9DuuF6C5jH+q/x15j2jniycgKbxU09Hr0WqlSLUs4i4ltHGXqTe7VHclYWyA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
sprintf-js@~1.0.2:
version "1.0.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/sprintf-js/-/sprintf-js-1.0.3.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-D9cPgkvLlV3t3IzL0D0YLvGA9Ahk4PcvVwUbN0dSGr1aP0Nrt4AEnTUbuGvquEC0mA64Gqt1fzirlRs5ibXx8g==
stack-utils@^2.0.3:
version "2.0.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/stack-utils/-/stack-utils-2.0.6.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-XlkWvfIm6RmsWtNJx+uqtKLS8eqFbxUg0ZzLXqY0caEy9l7hruX8IpiDnjsLavoBgqCCR71TqWO8MaXYheJ3RQ==
dependencies:
escape-string-regexp "^2.0.0"
string-length@^4.0.1:
version "4.0.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/string-length/-/string-length-4.0.2.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-+l6rNN5fYHNhZZy41RXsYptCjA2Igmq4EG7kZAYFQI1E1VTXarr6ZPXBg6eq7Y6eK4FEhY6AJlyuFIb/v/S0VQ==
dependencies:
char-regex "^1.0.2"
strip-ansi "^6.0.0"
string-width@^4.1.0, string-width@^4.2.0, string-width@^4.2.3:
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "4.2.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/string-width/-/string-width-4.2.3.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==
dependencies:
emoji-regex "^8.0.0"
is-fullwidth-code-point "^3.0.0"
strip-ansi "^6.0.1"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
strip-ansi@^6.0.0, strip-ansi@^6.0.1:
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "6.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==
dependencies:
ansi-regex "^5.0.1"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
strip-bom@^4.0.0:
version "4.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/strip-bom/-/strip-bom-4.0.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-3xurFv5tEgii33Zi8Jtp55wEIILR9eh34FAW00PZf+JnSsTmV/ioewSgQl97JHvgjoRGwPShsWm+IdrxB35d0w==
strip-final-newline@^2.0.0:
version "2.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/strip-final-newline/-/strip-final-newline-2.0.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-BrpvfNAE3dcvq7ll3xVumzjKjZQ5tI1sEUIKr3Uoks0XUl45St3FlatVqef9prk4jRDzhW6WZg+3bk93y6pLjA==
strip-json-comments@^3.1.1:
version "3.1.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/strip-json-comments/-/strip-json-comments-3.1.1.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-6fPc+R4ihwqP6N/aIv2f1gMH8lOVtWQHoqC4yK6oSDVVocumAsfCqjkXnqiYMhmMwS/mEHLp7Vehlt3ql6lEig==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
supports-color@^5.3.0:
version "5.5.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/supports-color/-/supports-color-5.5.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-QjVjwdXIt408MIiAqCX4oUKsgU2EqAGzs2Ppkm4aQYbjm+ZEWEcW4SfFNTr4uMNZma0ey4f5lgLrkB0aX0QMow==
dependencies:
has-flag "^3.0.0"
supports-color@^7.1.0:
version "7.2.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/supports-color/-/supports-color-7.2.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-qpCAvRl9stuOHveKsn7HncJRvv501qIacKzQlO/+Lwxc9+0q2wLyv4Dfvt80/DPn2pqOBsJdDiogXGR9+OvwRw==
dependencies:
has-flag "^4.0.0"
supports-color@^8.0.0:
version "8.1.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/supports-color/-/supports-color-8.1.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-MpUEN2OodtUzxvKQl72cUF7RQ5EiHsGvSsVG0ia9c5RbWGL2CI4C7EpPS8UTBIplnlzZiNuV56w+FuNxy3ty2Q==
dependencies:
has-flag "^4.0.0"
supports-preserve-symlinks-flag@^1.0.0:
version "1.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/supports-preserve-symlinks-flag/-/supports-preserve-symlinks-flag-1.0.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-ot0WnXS9fgdkgIcePe6RHNk1WA8+muPa6cSjeR3V8K27q9BB1rTE3R1p7Hv0z1ZyAc8s6Vvv8DIyWf681MAt0w==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
symbol-tree@^3.2.4:
version "3.2.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/symbol-tree/-/symbol-tree-3.2.4.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-9QNk5KwDF+Bvz+PyObkmSYjI5ksVUYtjW7AU22r2NKcfLJcXp96hkDWU3+XndOsUb+AQ9QhfzfCT2O+CNWT5Tw==
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
tabbable@^5.3.3:
version "5.3.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/tabbable/-/tabbable-5.3.3.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-QD9qKY3StfbZqWOPLp0++pOrAVb/HbUi5xCc8cUo4XjP19808oaMiDzn0leBY5mCespIBM0CIZePzZjgzR83kA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
tapable@^2.1.1, tapable@^2.2.0:
version "2.2.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/tapable/-/tapable-2.2.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-GNzQvQTOIP6RyTfE2Qxb8ZVlNmw0n88vp1szwWRimP02mnTsx3Wtn5qRdqY9w2XduFNUgvOwhNnQsjwCp+kqaQ==
terser-webpack-plugin@^5.1.3:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "5.3.6"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/terser-webpack-plugin/-/terser-webpack-plugin-5.3.6.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-kfLFk+PoLUQIbLmB1+PZDMRSZS99Mp+/MHqDNmMA6tOItzRt+Npe3E+fsMs5mfcM0wCtrrdU387UnV+vnSffXQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
"@jridgewell/trace-mapping" "^0.3.14"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
jest-worker "^27.4.5"
schema-utils "^3.1.1"
serialize-javascript "^6.0.0"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
terser "^5.14.1"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
terser@^5.14.1:
version "5.15.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/terser/-/terser-5.15.1.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-K1faMUvpm/FBxjBXud0LWVAGxmvoPbZbfTCYbSgaaYQaIXI3/TdI7a7ZGA73Zrou6Q8Zmz3oeUTsp/dj+ag2Xw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
chore(deps): bump terser from 5.12.0 to 5.14.2 (#3551) Bumps [terser](https://github.com/terser/terser) from 5.12.0 to 5.14.2. - [Release notes](https://github.com/terser/terser/releases) - [Changelog](https://github.com/terser/terser/blob/master/CHANGELOG.md) - [Commits](https://github.com/terser/terser/commits) --- updated-dependencies: - dependency-name: terser dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2022-07-29 20:48:04 +08:00
"@jridgewell/source-map" "^0.3.2"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
acorn "^8.5.0"
commander "^2.20.0"
source-map-support "~0.5.20"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
test-exclude@^6.0.0:
version "6.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/test-exclude/-/test-exclude-6.0.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-cAGWPIyOHU6zlmg88jwm7VRyXnMN7iV68OGAbYDk/Mh/xC/pzVPlQtY6ngoIH/5/tciuhGfvESU8GrHrcxD56w==
dependencies:
"@istanbuljs/schema" "^0.1.2"
glob "^7.1.4"
minimatch "^3.0.4"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
textarea-caret@^3.1.0:
version "3.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/textarea-caret/-/textarea-caret-3.1.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-cXAvzO9pP5CGa6NKx0WYHl+8CHKZs8byMkt3PCJBCmq2a34YA9pO1NrQET5pzeqnBjBdToF5No4rrmkDUgQC2Q==
throttle-debounce@^3.0.1:
version "3.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/throttle-debounce/-/throttle-debounce-3.0.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-dTEWWNu6JmeVXY0ZYoPuH5cRIwc0MeGbJwah9KUNYSJwommQpCzTySTpEe8Gs1J23aeWEuAobe4Ag7EHVt/LOg==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
tmpl@1.0.5:
version "1.0.5"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/tmpl/-/tmpl-1.0.5.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-3f0uOEAQwIqGuWW2MVzYg8fV/QNnc/IpuJNG837rLuczAaLVHslWHZQj4IGiEl5Hs3kkbhwL9Ab7Hrsmuj+Smw==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
to-fast-properties@^2.0.0:
version "2.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/to-fast-properties/-/to-fast-properties-2.0.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-/OaKK0xYrs3DmxRYqL/yDc+FxFUVYhDlXMhRmv3z915w2HF1tnN1omB354j8VUGO/hbRzyD6Y3sA7v7GS/ceog==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
to-regex-range@^5.0.1:
version "5.0.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/to-regex-range/-/to-regex-range-5.0.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-65P7iz6X5yEr1cwcgvQxbbIw7Uk3gOy5dIdtZ4rDveLqhrdJP+Li/Hx6tyK0NEb+2GCyneCMJiGqrADCSNk8sQ==
dependencies:
is-number "^7.0.0"
totalist@^1.0.0:
version "1.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/totalist/-/totalist-1.1.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-gduQwd1rOdDMGxFG1gEvhV88Oirdo2p+KjoYFU7k2g+i7n6AFFbDQ5kMPUsW0pNbfQsB/cwXvT1i4Bue0s9g5g==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
tough-cookie@^4.1.2:
version "4.1.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/tough-cookie/-/tough-cookie-4.1.2.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-G9fqXWoYFZgTc2z8Q5zaHy/vJMjm+WV0AkAeHxVCQiEB1b+dGvWzFW6QV07cY5jQ5gRkeid2qIkzkxUnmoQZUQ==
dependencies:
psl "^1.1.33"
punycode "^2.1.1"
universalify "^0.2.0"
url-parse "^1.5.3"
tr46@^3.0.0:
version "3.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/tr46/-/tr46-3.0.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-l7FvfAHlcmulp8kr+flpQZmVwtu7nfRV7NZujtN0OqES8EL4O4e0qqzL0DC5gAvx/ZC/9lk6rhcUwYvkBnBnYA==
dependencies:
punycode "^2.1.1"
ts-jest@^29.0.3:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
version "29.0.5"
resolved "https://registry.npmjs.org/ts-jest/-/ts-jest-29.0.5.tgz"
integrity sha512-PL3UciSgIpQ7f6XjVOmbi96vmDHUqAyqDr8YxzopDqX3kfgYtX1cuNeBjP+L9sFXi6nzsGGA6R3fP3DDDJyrxA==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
bs-logger "0.x"
fast-json-stable-stringify "2.x"
jest-util "^29.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
json5 "^2.2.3"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
lodash.memoize "4.x"
make-error "1.x"
semver "7.x"
yargs-parser "^21.0.1"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
tslib@^1.8.1:
version "1.14.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/tslib/-/tslib-1.14.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-Xni35NKzjgMrwevysHTCArtLDpPvye8zV/0E4EyYn43P7/7qvQwPh9BGkHewbMulVntbigmcT7rdX3BNo9wRJg==
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
"tslib@1 || 2":
version "2.4.1"
resolved "https://registry.npmjs.org/tslib/-/tslib-2.4.1.tgz"
integrity sha512-tGyy4dAjRIEwI7BzsB0lynWgOpfqjUdq91XXAlIWD2OwKBH7oCl/GZG/HT4BOHrTlPMOASlMQ7veyTqpmRcrNA==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
tsutils@3:
version "3.21.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/tsutils/-/tsutils-3.21.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-mHKK3iUXL+3UF6xL5k0PEhKRUBKPBCv/+RkEOpjRWxxx27KKRBmmA60A9pgOUvMi8GKhRMPEmjBRPzs2W7O1OA==
dependencies:
tslib "^1.8.1"
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
tweetnacl@^1.0.3:
version "1.0.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/tweetnacl/-/tweetnacl-1.0.3.tgz"
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
integrity sha512-6rt+RN7aOi1nGMyC4Xa5DdYiukl2UWCbcJft7YhxReBGQD7OAM8Pbxw6YMo4r2diNEA8FEmu32YOn9rhaiE5yw==
twemoji-parser@14.0.0:
version "14.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/twemoji-parser/-/twemoji-parser-14.0.0.tgz"
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
integrity sha512-9DUOTGLOWs0pFWnh1p6NF+C3CkQ96PWmEFwhOVmT3WbecRC+68AIqpsnJXygfkFcp4aXbOp8Dwbhh/HQgvoRxA==
twemoji@^14.0.2:
version "14.0.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/twemoji/-/twemoji-14.0.2.tgz"
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
integrity sha512-BzOoXIe1QVdmsUmZ54xbEH+8AgtOKUiG53zO5vVP2iUu6h5u9lN15NcuS6te4OY96qx0H7JK9vjjl9WQbkTRuA==
dependencies:
fs-extra "^8.0.1"
jsonfile "^5.0.0"
twemoji-parser "14.0.0"
universalify "^0.1.2"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
type-check@~0.3.2:
version "0.3.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/type-check/-/type-check-0.3.2.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-ZCmOJdvOWDBYJlzAoFkC+Q0+bUyEOS1ltgp1MGU03fqHG+dbi9tBFU2Rd9QKiDZFAYrhPh2JUf7rZRIuHRKtOg==
dependencies:
prelude-ls "~1.1.2"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
type-coverage-core@^2.17.2:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
version "2.23.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
fast-glob "3"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
minimatch "3 || 4 || 5"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
normalize-path "3"
tslib "1 || 2"
tsutils "3"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
type-detect@4.0.8:
version "4.0.8"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/type-detect/-/type-detect-4.0.8.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-0fr/mIH1dlO+x7TlcMy+bIDqKPsw/70tVyeHW787goQjhmqaZe10uwLujubK9q9Lg6Fiho1KUKDYz0Z7k7g5/g==
type-fest@^0.21.3:
version "0.21.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/type-fest/-/type-fest-0.21.3.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-t0rzBq87m3fVcduHDUFhKmyyX+9eo6WQjZvf51Ea/M0Q7+T374Jp1aUiyUl0GKxp8M/OETVHSDvmkyPgvX+X2w==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
type-fest@^0.6.0:
version "0.6.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/type-fest/-/type-fest-0.6.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-q+MB8nYR1KDLrgr4G5yemftpMC7/QLqVndBmEEdqzmNj5dcFOO4Oo8qlwZE3ULT3+Zim1F8Kq4cBnikNhlCMlg==
type-fest@^0.8.1:
version "0.8.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/type-fest/-/type-fest-0.8.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-4dbzIzqvjtgiM5rw1k5rEHtBANKmdudhGyBEajN01fEyhaAIhsoKNy6y7+IN93IfpFtwY9iqi7kD+xwKhQsNJA==
typed-styles@^0.0.7:
version "0.0.7"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/typed-styles/-/typed-styles-0.0.7.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-pzP0PWoZUhsECYjABgCGQlRGL1n7tOHsgwYv3oIiEpJwGhFTuty/YNeduxQYzXXa3Ge5BdT6sHYIQYpl4uJ+5Q==
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
typescript-coverage-report@^0.6.1, typescript-coverage-report@^0.6.4:
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
version "0.6.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/typescript-coverage-report/-/typescript-coverage-report-0.6.4.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-G+0OFYxwN5oRbORlU1nKYtO00G567lcl4+nbg3MU3Y9ayFnh677dMHmAL4JGP/4Cb1IBN5h/DUQDr/z9X+9lag==
dependencies:
chalk "^4.0.0"
cli-table3 "^0.6.1"
commander "^5.0.0"
ncp "^2.0.0"
react "^16.13.1"
react-dom "^16.13.1"
rimraf "^3.0.2"
semantic-ui-react "^0.88.2"
type-coverage-core "^2.17.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
typescript@^4.4.4, typescript@^4.5.4, typescript@^4.7.4, "typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta", typescript@>=4.3, "typescript@2 || 3 || 4":
version "4.9.3"
perf(statistics): rewrite for performance on very large communities (#3531) Co-authored-by: Sami Mazouz <ilyasmazouz@gmail.com>
2022-07-19 02:07:38 +08:00
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
unicode-canonical-property-names-ecmascript@^2.0.0:
version "2.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/unicode-canonical-property-names-ecmascript/-/unicode-canonical-property-names-ecmascript-2.0.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-yY5PpDlfVIU5+y/BSCxAJRBIS1Zc2dDG3Ujq+sR0U+JjUevW2JhocOF+soROYDSaAezOzOKuyyixhD6mBknSmQ==
unicode-match-property-ecmascript@^2.0.0:
version "2.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/unicode-match-property-ecmascript/-/unicode-match-property-ecmascript-2.0.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-5kaZCrbp5mmbz5ulBkDkbY0SsPOjKqVS35VpL9ulMPfSl0J0Xsm+9Evphv9CoIZFwre7aJoa94AY6seMKGVN5Q==
dependencies:
unicode-canonical-property-names-ecmascript "^2.0.0"
unicode-property-aliases-ecmascript "^2.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
unicode-match-property-value-ecmascript@^2.1.0:
version "2.1.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
unicode-property-aliases-ecmascript@^2.0.0:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "2.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/unicode-property-aliases-ecmascript/-/unicode-property-aliases-ecmascript-2.1.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-6t3foTQI9qne+OZoVQB/8x8rk2k1eVy1gRXhV3oFQ5T6R1dqQ1xtin3XqSlx3+ATBkliTaR/hHyJBm+LVPNM8w==
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
universalify@^0.1.0, universalify@^0.1.2:
version "0.1.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/universalify/-/universalify-0.1.2.tgz"
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
integrity sha512-rBJeI5CXAlmy1pV+617WB9J63U6XcazHHF2f2dbJix4XzpUF0RS3Zbj0FGIOCAva5P/d/GBOYaACQ1w+0azUkg==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
universalify@^0.2.0:
version "0.2.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/universalify/-/universalify-0.2.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-CJ1QgKmNg3CwvAv/kOFmtnEN05f0D/cn9QntgNOQlQF9dgvVTHj3t+8JPdjqawCHk7V/KA+fbUqzZ9XWhcqPUg==
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
update-browserslist-db@^1.0.9:
version "1.0.10"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/update-browserslist-db/-/update-browserslist-db-1.0.10.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-OztqDenkfFkbSG+tRxBeAnCVPckDBcvibKd35yDONx6OU8N7sqgwc7rCbkJ/WcYtVRZ4ba68d6byhC21GFh7sQ==
dependencies:
escalade "^3.1.1"
picocolors "^1.0.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
uri-js@^4.2.2:
version "4.4.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/uri-js/-/uri-js-4.4.1.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-7rKUyy33Q1yc98pQ1DAmLtwX109F7TIfWlW1Ydo8Wl1ii1SeHieeh0HHfPeL2fMXK6z0s8ecKs9frCuLJvndBg==
dependencies:
punycode "^2.1.0"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
url-parse@^1.5.3:
version "1.5.10"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/url-parse/-/url-parse-1.5.10.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-WypcfiRhfeUP9vvF0j6rw0J3hrWrw6iZv3+22h6iRMJ/8z1Tj6XfLP4DsUix5MhMPnXpiHDoKyoZ/bdCkwBCiQ==
dependencies:
querystringify "^2.1.1"
requires-port "^1.0.0"
v8-to-istanbul@^9.0.1:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
version "9.1.0"
resolved "https://registry.npmjs.org/v8-to-istanbul/-/v8-to-istanbul-9.1.0.tgz"
integrity sha512-6z3GW9x8G1gd+JIIgQQQxXuiJtCXeAjp6RaPEPLv62mH3iPHPxV6W3robxtCzNErRo6ZwTmzWhsbNvjyEBKzKA==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
"@jridgewell/trace-mapping" "^0.3.12"
"@types/istanbul-lib-coverage" "^2.0.1"
convert-source-map "^1.6.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
validate-npm-package-license@^3.0.1:
version "3.0.4"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.4.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-DpKm2Ui/xN7/HQKCtpZxoRWBhZ9Z0kqtygG8XCgNQ8ZlDnxuQmWhj566j8fN4Cu3/JmbhsDo7fcAJq4s9h27Ew==
dependencies:
spdx-correct "^3.0.0"
spdx-expression-parse "^3.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
w3c-xmlserializer@^4.0.0:
version "4.0.0"
resolved "https://registry.npmjs.org/w3c-xmlserializer/-/w3c-xmlserializer-4.0.0.tgz"
integrity sha512-d+BFHzbiCx6zGfz0HyQ6Rg69w9k19nviJspaj4yNscGjrHu94sVP+aRm75yEbCh+r2/yR+7q6hux9LVtbuTGBw==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
xml-name-validator "^4.0.0"
walker@^1.0.8:
version "1.0.8"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/walker/-/walker-1.0.8.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-ts/8E8l5b7kY0vlWLewOkDXMmPdLcVV4GmOQLyxuSswIJsweeFZtAsMF7k1Nszz+TYBQrlYRmzOnr398y1JemQ==
dependencies:
makeerror "1.0.12"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
warning@^4.0.2, warning@^4.0.3:
version "4.0.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/warning/-/warning-4.0.3.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-rpJyN222KWIvHJ/F53XSZv0Zl/accqHR8et1kpaMTD/fLCRxtV8iX8czMzY7sVZupTI3zcUTg8eycS2kNF9l6w==
dependencies:
loose-envify "^1.0.0"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
watchpack@^2.4.0:
version "2.4.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/watchpack/-/watchpack-2.4.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-Lcvm7MGST/4fup+ifyKi2hjyIAwcdI4HRgtvTpIUxBRhB+RFtUh8XtDOxUfctVCnhVi+QQj49i91OyvzkJl6cg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
glob-to-regexp "^0.4.1"
graceful-fs "^4.1.2"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
webidl-conversions@^7.0.0:
version "7.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/webidl-conversions/-/webidl-conversions-7.0.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-VwddBukDzu71offAQR975unBIGqfKZpM+8ZX6ySk8nYhVoo5CYaZyzt3YBvYtRtO+aoGlqxPg/B87NGVZ/fu6g==
fix: Assorted Typing Fixes (#3348) With all the commits below, we resolve all outstanding typing issues in the repo, and CI jobs run green. * fix: Convert DashboardPage and DashboardWidget to TypeScript * fix: fix type errors in package manager ext * fix: Convert Post component to TypeScript * fix: avatar typings should accept null user * fix: convert Notification component to TypeScript * fix: properly use `typeof` in ForumApplication * feat: make Notification content attr generic * chore: format Notification component * fix: Convert DiscussionRenamedNotification to TypeScript * fix(pusher) move shims to a location where they get applied * fix(pusher): fix some typing errors * fix(akismet): fix some typing issues * chore: update core dist typings * chore(pusher): format * fix: anchorScroll should accept string selectors * fix: more accurately represent ApiQueryParamsPlural * fix: convert PostStreamState to TypeScript * chore(core): rebuild typings * feat: allow extending app.routes * fix: more flexible typings for highlight.ts * fix: use primitive `number` type for Discussion typings * fix: convert DiscussionListItem to TypeScript * chore: rebuild core typings * fix: final pusher type fixes * feat: start tags TypeScript conversion * fix: require-dev tags in pusher for CI TypeScript purposes. * chore(core): format * chore(tags): build dist typings * feat(pusher): use dist types from tags. * feat: convert flags to TypeScript * chore(flags): generate dist typings * fix(akismet): last type errors * chore: update .yarn-integrity * chore: partially run flarum-cli audit infra --fix The tsconfig changes from that command are ignored, since we don't yet support "replacable sections" that would let us add custom config. * chore: use type imports * fix: broader gitattributes * chore: run flarum-cli audit infra --monorepo --fix * feat: make `app.data` typings extensible * chore(core): format * chore: boost tags TypeScript coverage * fix(tags): further increase type coverage.
2022-03-23 23:43:14 +08:00
webpack-bundle-analyzer@^4.5.0:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "4.7.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/webpack-bundle-analyzer/-/webpack-bundle-analyzer-4.7.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-j9b8ynpJS4K+zfO5GGwsAcQX4ZHpWV+yRiHDiL+bE0XHJ8NiPYLTNVQdlFYWxtpg9lfAQNlwJg16J9AJtFSXRg==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
dependencies:
acorn "^8.0.4"
acorn-walk "^8.0.0"
chalk "^4.1.0"
commander "^7.2.0"
gzip-size "^6.0.0"
lodash "^4.17.20"
opener "^1.5.2"
sirv "^1.0.7"
ws "^7.3.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
webpack-cli@^4.10.0, webpack-cli@^4.9.1, webpack-cli@4.x.x:
perf(statistics): rewrite for performance on very large communities (#3531) Co-authored-by: Sami Mazouz <ilyasmazouz@gmail.com>
2022-07-19 02:07:38 +08:00
version "4.10.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/webpack-cli/-/webpack-cli-4.10.0.tgz"
perf(statistics): rewrite for performance on very large communities (#3531) Co-authored-by: Sami Mazouz <ilyasmazouz@gmail.com>
2022-07-19 02:07:38 +08:00
integrity sha512-NLhDfH/h4O6UOy+0LSso42xvYypClINuMNBVVzX4vX98TmTaTUxwRbXdhucbFMd2qLaCTcLq/PdYrvi8onw90w==
dependencies:
"@discoveryjs/json-ext" "^0.5.0"
"@webpack-cli/configtest" "^1.2.0"
"@webpack-cli/info" "^1.5.0"
"@webpack-cli/serve" "^1.7.0"
colorette "^2.0.14"
commander "^7.0.0"
cross-spawn "^7.0.3"
fastest-levenshtein "^1.0.12"
import-local "^3.0.2"
interpret "^2.2.0"
rechoir "^0.7.0"
webpack-merge "^5.7.3"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
webpack-merge@^5.7.3, webpack-merge@^5.8.0:
version "5.8.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/webpack-merge/-/webpack-merge-5.8.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-/SaI7xY0831XwP6kzuwhKWVKDP9t1QY1h65lAFLbZqMPIuYcD9QAW4u9STIbU9kaJbPBB/geU/gLr1wDjOhQ+Q==
dependencies:
clone-deep "^4.0.1"
wildcard "^2.0.0"
webpack-sources@^3.2.3:
version "3.2.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/webpack-sources/-/webpack-sources-3.2.3.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-/DyMEOrDgLKKIG0fmvtz+4dUX/3Ghozwgm6iPp8KRhvn+eQf9+Q7GWxVNMk3+uCPWfdXYC4ExGBckIXdFEfH1w==
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
webpack@^5.0.0, webpack@^5.1.0, webpack@^5.65.0, webpack@^5.73.0, webpack@>=2, "webpack@4.x.x || 5.x.x":
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "5.75.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/webpack/-/webpack-5.75.0.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-piaIaoVJlqMsPtX/+3KTTO6jfvrSYgauFVdt8cr9LTHKmcq/AMd4mhzsiP7ZF/PGRNPGA8336jldh9l2Kt2ogQ==
perf(statistics): rewrite for performance on very large communities (#3531) Co-authored-by: Sami Mazouz <ilyasmazouz@gmail.com>
2022-07-19 02:07:38 +08:00
dependencies:
"@types/eslint-scope" "^3.7.3"
"@types/estree" "^0.0.51"
"@webassemblyjs/ast" "1.11.1"
"@webassemblyjs/wasm-edit" "1.11.1"
"@webassemblyjs/wasm-parser" "1.11.1"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
acorn "^8.7.1"
perf(statistics): rewrite for performance on very large communities (#3531) Co-authored-by: Sami Mazouz <ilyasmazouz@gmail.com>
2022-07-19 02:07:38 +08:00
acorn-import-assertions "^1.7.6"
browserslist "^4.14.5"
chrome-trace-event "^1.0.2"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
enhanced-resolve "^5.10.0"
perf(statistics): rewrite for performance on very large communities (#3531) Co-authored-by: Sami Mazouz <ilyasmazouz@gmail.com>
2022-07-19 02:07:38 +08:00
es-module-lexer "^0.9.0"
eslint-scope "5.1.1"
events "^3.2.0"
glob-to-regexp "^0.4.1"
graceful-fs "^4.2.9"
json-parse-even-better-errors "^2.3.1"
loader-runner "^4.2.0"
mime-types "^2.1.27"
neo-async "^2.6.2"
schema-utils "^3.1.0"
tapable "^2.1.1"
terser-webpack-plugin "^5.1.3"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
watchpack "^2.4.0"
perf(statistics): rewrite for performance on very large communities (#3531) Co-authored-by: Sami Mazouz <ilyasmazouz@gmail.com>
2022-07-19 02:07:38 +08:00
webpack-sources "^3.2.3"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
whatwg-encoding@^2.0.0:
version "2.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/whatwg-encoding/-/whatwg-encoding-2.0.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-p41ogyeMUrw3jWclHWTQg1k05DSVXPLcVxRTYsXUk+ZooOCZLcoYgPZ/HL/D/N+uQPOtcp1me1WhBEaX02mhWg==
dependencies:
iconv-lite "0.6.3"
whatwg-mimetype@^3.0.0:
version "3.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/whatwg-mimetype/-/whatwg-mimetype-3.0.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-nt+N2dzIutVRxARx1nghPKGv1xHikU7HKdfafKkLNLindmPU/ch3U31NOCGGA/dmPcmb1VlofO0vnKAcsm0o/Q==
whatwg-url@^11.0.0:
version "11.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/whatwg-url/-/whatwg-url-11.0.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-RKT8HExMpoYx4igMiVMY83lN6UeITKJlBQ+vR/8ZJ8OCdSiN3RwCq+9gH0+Xzj0+5IrM6i4j/6LuvzbZIQgEcQ==
dependencies:
tr46 "^3.0.0"
webidl-conversions "^7.0.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
which@^2.0.1:
version "2.0.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/which/-/which-2.0.2.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-BLI3Tl1TW3Pvl70l3yq3Y64i+awpwXqsGBYWkkqMtnbXgrMD+yj7rhW0kuEDxzJaYXGjEW5ogapKNMEKNMjibA==
dependencies:
isexe "^2.0.0"
wildcard@^2.0.0:
version "2.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/wildcard/-/wildcard-2.0.0.tgz"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
integrity sha512-JcKqAHLPxcdb9KM49dufGXn2x3ssnfjbcaQdLlfZsL9rH9wgDQjUtDxbo8NE0F6SFvydeu1VhZe7hZuHsB2/pw==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
word-wrap@~1.2.3:
version "1.2.3"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/word-wrap/-/word-wrap-1.2.3.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-Hz/mrNwitNRh/HUAtM/VT/5VH+ygD6DV7mYKZAtHOrbs8U7lvPS6xf7EJKMF0uW1KJCl0H701g3ZGus+muE5vQ==
wrap-ansi@^7.0.0:
version "7.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-7.0.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-YVGIj2kamLSTxw6NsZjoBxfSwsn0ycdesmc4p+Q21c5zPuZ1pl+NfxVdxPtdHvmNVOQ6XSYG4AUtyt/Fi7D16Q==
dependencies:
ansi-styles "^4.0.0"
string-width "^4.1.0"
strip-ansi "^6.0.0"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
wrappy@1:
version "1.0.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/wrappy/-/wrappy-1.0.2.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-l4Sp/DRseor9wL6EvV2+TuQn63dMkPjZ/sp9XkghTEbV9KlPS1xUsZ3u7/IQO4wxtcFB4bgpQPRcR3QCvezPcQ==
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
write-file-atomic@^4.0.2:
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
version "4.0.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/write-file-atomic/-/write-file-atomic-4.0.2.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-7KxauUdBmSdWnmpaGFg+ppNjKF8uNLry8LyzjauQDOVONfFLNKrKvQOxZ/VuTIcS/gge/YNahf5RIIQWTSarlg==
dependencies:
imurmurhash "^0.1.4"
signal-exit "^3.0.7"
feat: use yarn workspaces
2022-03-12 07:54:22 +08:00
ws@^7.3.1:
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
version "7.5.9"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/ws/-/ws-7.5.9.tgz"
chore: update JS dependencies (#3695) * chore: lock mithril to `2.0` because `2.2` has breaking changes with no upgrade guide * chore: update JS dependencies `yarn upgrade` * chore: fix typings after js deps updates * chore(review): better semver Co-authored-by: David Wheatley <hi@davwheat.dev>
2022-11-26 01:20:30 +08:00
integrity sha512-F+P9Jil7UiSKSkppIiD94dN07AwvFixvLIj1Og1Rl9GGMuNipJnV9JzjD6XuqmAeiswGvUmNLjr5cFuXwNS77Q==
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
ws@^8.11.0:
version "8.13.0"
resolved "https://registry.npmjs.org/ws/-/ws-8.13.0.tgz"
integrity sha512-x9vcZYTrFPC7aSIbj7sRCYo7L/Xb8Iy+pW0ng0wt2vCJv7M9HOMy0UoN3rr+IFC7hb7vXoqS+P9ktyLLLhO+LA==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
xml-name-validator@^4.0.0:
version "4.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/xml-name-validator/-/xml-name-validator-4.0.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-ICP2e+jsHvAj2E2lIHxa5tjXRlKDJo4IdvPvCXbXQGdzSfmSpNVyIKMvoZHjDY9DP0zV17iI85o90vRFXNccRw==
xmlchars@^2.2.0:
version "2.2.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/xmlchars/-/xmlchars-2.2.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-JZnDKK8B0RCDw84FNdDAIpZK+JuJw+s7Lz8nksI7SIuU3UXJJslUthsi+uWBUYOwPFwW7W7PRLRfUKpxjtjFCw==
y18n@^5.0.5:
version "5.0.8"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/y18n/-/y18n-5.0.8.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-0pfFzegeDWJHJIAmTLRP2DwHjdF5s7jo9tuztdQxAhINCdvS+3nGINqPd00AphqJR/0LhANUS6/+7SCb98YOfA==
yallist@^4.0.0:
version "4.0.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/yallist/-/yallist-4.0.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-3wdGidZyq5PB084XLES5TpOSRA3wjXAlIWMhum2kRcv/41Sn2emQ0dycQW4uZXLejwKvg6EsvbdlVL+FYEct7A==
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
yaml@^1.10.0:
version "1.10.2"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/yaml/-/yaml-1.10.2.tgz"
fix: update JS dependencies
2022-11-11 07:23:44 +08:00
integrity sha512-r3vXyErRCYJ7wg28yvBY5VSoAF8ZvlcW9/BwUzEtUsjvX/DKs24dIkuwjtuprwJJHsbyUbLApepYTR1BN4uHrg==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
yargs-parser@^21.0.1, yargs-parser@^21.1.1:
version "21.1.1"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/yargs-parser/-/yargs-parser-21.1.1.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-tVpsJW7DdjecAiFpbIB1e3qxIQsE6NoPc5/eTdrbbIC4h0LVsWhnoa3g+m2HclBIujHzsxZ4VJVA+GUuc2/LBw==
yargs@^17.3.1:
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
version "17.7.1"
resolved "https://registry.npmjs.org/yargs/-/yargs-17.7.1.tgz"
integrity sha512-cwiTb08Xuv5fqF4AovYacTFNxk62th7LKJ6BL9IGUpTJrWoU7/7WdQGTP2SjKf1dUNBGzDd28p/Yfs/GI6JrLw==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
dependencies:
cliui "^8.0.1"
escalade "^3.1.1"
get-caller-file "^2.0.5"
require-directory "^2.1.1"
string-width "^4.2.3"
y18n "^5.0.5"
yargs-parser "^21.1.1"
feat(jest): mithril component testing (#3679) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * feat(jest): mithril component testing * fix: use separate `tsconfig.test.json` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-11 06:02:50 +08:00
yields-keycode@1.1.0:
version "1.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/yields-keycode/-/yields-keycode-1.1.0.tgz"
feat(jest): mithril component testing (#3679) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * feat(jest): mithril component testing * fix: use separate `tsconfig.test.json` Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-11 06:02:50 +08:00
integrity sha512-5xkHkiEa8TRGlcDzOvVXrVhhLbla9WDFmHsN2tyTtFwxwCo7cpJdvOczvaUjSQKay3VuW5sV4jMtiesTKbZYXw==
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
yocto-queue@^0.1.0:
version "0.1.0"
feat(permission): add the no one permission One thing that has been very frustrating while developing extensions is that you cannot easily create a feature that you would like to allow disabling through the permission grid. This Proof of Concept PR is a question, whether I'm the only one running into this limitation for Flarum. It does: - introduce a fake permission, similar to Guest - removes the whole permission entry from the db when selected - restores the permission visually on the frontend It has to: - confirm admins also cannot use the permission if selected - not break v1.x functionality or be moved to v2.0 - appeal to core and community
2023-03-26 16:03:09 +08:00
resolved "https://registry.npmjs.org/yocto-queue/-/yocto-queue-0.1.0.tgz"
feat(jest): create jest config package for unit testing (#3678) * feat(jest): create jest config package for unit testing * chore: housekeeping * fix: now we need to explicitly allow importing without extension * fix: recover EditorDriverInterface import * Apply suggestions from code review * chore: yarn Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
2023-02-09 05:02:40 +08:00
integrity sha512-rVksvsnNCdJ/ohGc6xgPwyN8eheCxsiLM8mxuE/t/mOVqJewPuO1miLpTHQiRgTKCLexL4MeAFVagts7HmNZ2Q==
Reference in New Issue Copy Permalink