Discource-C
/
discourse
mirror of https://github.com/discourse/discourse.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
discourse/yarn.lock

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

4622 lines
209 KiB
Plaintext
Raw Normal View History

Run JS test in chrome headless on Travis.
2017-12-14 21:15:04 -05:00
# THIS IS AN AUTOGENERATED FILE. DO NOT EDIT THIS FILE DIRECTLY.
# yarn lockfile v1
DEV: Update sub-dependencies (#22325) Achieved by running `yarn upgrade --latest` both yarn.lock directories, then reverting changes to package.json files and running `yarn` again. I also de-duped yarn.lock files with `npx yarn-deduplicate && yarn`
2023-06-29 11:08:33 -04:00
"@aashutoshrathi/word-wrap@^1.2.3":
version "1.2.6"
resolved "https://registry.yarnpkg.com/@aashutoshrathi/word-wrap/-/word-wrap-1.2.6.tgz#bd9154aec9983f77b3a034ecaa015c2e4201f6cf"
integrity sha512-1Yjs2SvM8TflER/OD3cOjhWWOZb58A2t7wpE2S9XfBYTiIl+XFhQG2bjy4Pu1I+EAlCNUzRDYDdFwFYUKvXcIA==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
"@ampproject/remapping@^2.2.0":
version "2.2.1"
resolved "https://registry.yarnpkg.com/@ampproject/remapping/-/remapping-2.2.1.tgz#99e8e11851128b8702cd57c33684f1d0f260b630"
integrity sha512-lFMjJTrFL3j7L9yBxwYfCq2k6qqwHyzuUl/XBnif78PWTJYyL/dfowQHWE3sp6U6ZzqWiiIZnpTMO96zhkjwtg==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
dependencies:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
"@jridgewell/gen-mapping" "^0.3.0"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
"@jridgewell/trace-mapping" "^0.3.9"
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
"@babel/code-frame@^7.22.13":
version "7.22.13"
resolved "https://registry.yarnpkg.com/@babel/code-frame/-/code-frame-7.22.13.tgz#e3c1c099402598483b7a8c46a721d1038803755e"
integrity sha512-XktuhWlJ5g+3TJXc5upd9Ks1HutSArik6jf2eAjYFyIOf4ej3RN+184cZbzDvbPnuTJIUhPKKJE3cIsYTiAT3w==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
dependencies:
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
"@babel/highlight" "^7.22.13"
chalk "^2.4.2"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
"@babel/compat-data@^7.22.9":
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
version "7.23.2"
resolved "https://registry.yarnpkg.com/@babel/compat-data/-/compat-data-7.23.2.tgz#6a12ced93455827037bfb5ed8492820d60fc32cc"
integrity sha512-0S9TQMmDHlqAZ2ITT95irXKfxN9bncq8ZCoJhun3nHL/lLUxd2NKBJYoNGWH7S0hz6fRQwWlAWn/ILM0C70KZQ==
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
"@babel/core@^7.18.6", "@babel/core@^7.20.12", "@babel/core@^7.23.2":
version "7.23.2"
resolved "https://registry.yarnpkg.com/@babel/core/-/core-7.23.2.tgz#ed10df0d580fff67c5f3ee70fd22e2e4c90a9f94"
integrity sha512-n7s51eWdaWZ3vGT2tD4T7J6eJs3QoBXydv7vkUM06Bf1cbVD2Kc2UrkzhiQwobfV7NwOnQXYL7UBJ5VPU+RGoQ==
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
dependencies:
"@ampproject/remapping" "^2.2.0"
"@babel/code-frame" "^7.22.13"
"@babel/generator" "^7.23.0"
"@babel/helper-compilation-targets" "^7.22.15"
"@babel/helper-module-transforms" "^7.23.0"
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
"@babel/helpers" "^7.23.2"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@babel/parser" "^7.23.0"
"@babel/template" "^7.22.15"
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
"@babel/traverse" "^7.23.2"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@babel/types" "^7.23.0"
convert-source-map "^2.0.0"
debug "^4.1.0"
gensync "^1.0.0-beta.2"
json5 "^2.2.3"
semver "^6.3.1"
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
"@babel/eslint-parser@^7.22.15":
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
version "7.22.15"
resolved "https://registry.yarnpkg.com/@babel/eslint-parser/-/eslint-parser-7.22.15.tgz#263f059c476e29ca4972481a17b8b660cb025a34"
integrity sha512-yc8OOBIQk1EcRrpizuARSQS0TWAcOMpEJ1aafhNznaeYkeL+OhqnDObGFylB8ka8VFF/sZc+S4RzHyO+3LjQxg==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
dependencies:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
"@nicolo-ribaudo/eslint-scope-5-internals" "5.1.1-v1"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
eslint-visitor-keys "^2.1.0"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
semver "^6.3.1"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
DEV: Consolidate and update jsconfig, and add types packages (#23824) These updates significantly improve IDE tooling for imports across the Discourse core codebase, and also for framework packages. The `@types/ember-*` packages are a temporary solution until we get onto Ember 5, which ships its types in the main package. The previous approach of having jsconfig files in each package directory did work, but once you start adding all the possible interlinks between them, we hit the file count limit of VSCode's tooling (because it counts every file for every jsconfig its referenced in). Having one file at the root means that a single file can apply to all core packages and plugins. Long-term, to get the same functionality for all themes/plugins, we may need to look at building/publishing a Discourse types package which can be added to theme/plugin package.json files for development purposes.
2023-10-18 07:13:20 -04:00
"@babel/generator@^7.23.0":
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
version "7.23.0"
resolved "https://registry.yarnpkg.com/@babel/generator/-/generator-7.23.0.tgz#df5c386e2218be505b34837acbcb874d7a983420"
integrity sha512-lN85QRR+5IbYrMWM6Y4pE/noaQtg4pNiqeNGX60eqOfo6gtEj6uw/JagelB8vVztSd7R6M5n1+PQkDbHbBRU4g==
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
dependencies:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@babel/types" "^7.23.0"
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
"@jridgewell/gen-mapping" "^0.3.2"
"@jridgewell/trace-mapping" "^0.3.17"
jsesc "^2.5.1"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
"@babel/helper-annotate-as-pure@^7.22.5":
version "7.22.5"
resolved "https://registry.yarnpkg.com/@babel/helper-annotate-as-pure/-/helper-annotate-as-pure-7.22.5.tgz#e7f06737b197d580a01edf75d97e2c8be99d3882"
integrity sha512-LvBTxu8bQSQkcyKOU+a1btnNFQ1dMAd0R6PyW3arXes06F6QLWLIrd681bxRPIXlrMGR3XYnW9JyML7dP3qgxg==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
dependencies:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
"@babel/types" "^7.22.5"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
"@babel/helper-compilation-targets@^7.22.15":
version "7.22.15"
resolved "https://registry.yarnpkg.com/@babel/helper-compilation-targets/-/helper-compilation-targets-7.22.15.tgz#0698fc44551a26cf29f18d4662d5bf545a6cfc52"
integrity sha512-y6EEzULok0Qvz8yyLkCvVX+02ic+By2UdOhylwUOvOn9dvYc9mKICJuuU1n1XBI02YWsNsnrY1kc6DVbjcXbtw==
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
dependencies:
"@babel/compat-data" "^7.22.9"
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
"@babel/helper-validator-option" "^7.22.15"
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
browserslist "^4.21.9"
lru-cache "^5.1.1"
semver "^6.3.1"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@babel/helper-create-class-features-plugin@^7.22.15":
version "7.22.15"
resolved "https://registry.yarnpkg.com/@babel/helper-create-class-features-plugin/-/helper-create-class-features-plugin-7.22.15.tgz#97a61b385e57fe458496fad19f8e63b63c867de4"
integrity sha512-jKkwA59IXcvSaiK2UN45kKwSC9o+KuoXsBDvHvU/7BecYIp8GQ2UwrVvFgJASUT+hBnwJx6MhvMCuMzwZZ7jlg==
DEV: Introduce decorator-position lint rule (#22937)
2023-08-04 07:26:06 -04:00
dependencies:
"@babel/helper-annotate-as-pure" "^7.22.5"
"@babel/helper-environment-visitor" "^7.22.5"
"@babel/helper-function-name" "^7.22.5"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@babel/helper-member-expression-to-functions" "^7.22.15"
DEV: Introduce decorator-position lint rule (#22937)
2023-08-04 07:26:06 -04:00
"@babel/helper-optimise-call-expression" "^7.22.5"
"@babel/helper-replace-supers" "^7.22.9"
"@babel/helper-skip-transparent-expression-wrappers" "^7.22.5"
"@babel/helper-split-export-declaration" "^7.22.6"
semver "^6.3.1"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@babel/helper-environment-visitor@^7.22.20", "@babel/helper-environment-visitor@^7.22.5":
version "7.22.20"
resolved "https://registry.yarnpkg.com/@babel/helper-environment-visitor/-/helper-environment-visitor-7.22.20.tgz#96159db61d34a29dba454c959f5ae4a649ba9167"
integrity sha512-zfedSIzFhat/gFhWfHtgWvlec0nqB9YEIVrpuwjruLlXfUSnA8cJB0miHKwqDnQ7d32aKo2xt88/xZptwxbfhA==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@babel/helper-function-name@^7.22.5", "@babel/helper-function-name@^7.23.0":
version "7.23.0"
resolved "https://registry.yarnpkg.com/@babel/helper-function-name/-/helper-function-name-7.23.0.tgz#1f9a3cdbd5b2698a670c30d2735f9af95ed52759"
integrity sha512-OErEqsrxjZTJciZ4Oo+eoZqeW9UIiOcuYKRJA4ZAgV9myA+pOXhhmpfNCKjEH/auVfEYVFJ6y1Tc4r0eIApqiw==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
dependencies:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@babel/template" "^7.22.15"
"@babel/types" "^7.23.0"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
"@babel/helper-hoist-variables@^7.22.5":
version "7.22.5"
resolved "https://registry.yarnpkg.com/@babel/helper-hoist-variables/-/helper-hoist-variables-7.22.5.tgz#c01a007dac05c085914e8fb652b339db50d823bb"
integrity sha512-wGjk9QZVzvknA6yKIUURb8zY3grXCcOZt+/7Wcy8O2uctxhplmUPkOdlgoNhmdVee2c92JXbf1xpMtVNbfoxRw==
dependencies:
"@babel/types" "^7.22.5"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@babel/helper-member-expression-to-functions@^7.22.15":
version "7.23.0"
resolved "https://registry.yarnpkg.com/@babel/helper-member-expression-to-functions/-/helper-member-expression-to-functions-7.23.0.tgz#9263e88cc5e41d39ec18c9a3e0eced59a3e7d366"
integrity sha512-6gfrPwh7OuT6gZyJZvd6WbTfrqAo7vm4xCzAXOusKqq/vWdKXphTpj5klHKNmRUU6/QRGlBsyU9mAIPaWHlqJA==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
dependencies:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@babel/types" "^7.23.0"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
"@babel/helper-module-imports@^7.22.15":
version "7.22.15"
resolved "https://registry.yarnpkg.com/@babel/helper-module-imports/-/helper-module-imports-7.22.15.tgz#16146307acdc40cc00c3b2c647713076464bdbf0"
integrity sha512-0pYVBnDKZO2fnSPCrgM/6WMc7eS20Fbok+0r88fp+YtWVLZrp4CkafFGIp+W0VKw4a22sgebPT99y+FDNMdP4w==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
dependencies:
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
"@babel/types" "^7.22.15"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
DEV: Consolidate and update jsconfig, and add types packages (#23824) These updates significantly improve IDE tooling for imports across the Discourse core codebase, and also for framework packages. The `@types/ember-*` packages are a temporary solution until we get onto Ember 5, which ships its types in the main package. The previous approach of having jsconfig files in each package directory did work, but once you start adding all the possible interlinks between them, we hit the file count limit of VSCode's tooling (because it counts every file for every jsconfig its referenced in). Having one file at the root means that a single file can apply to all core packages and plugins. Long-term, to get the same functionality for all themes/plugins, we may need to look at building/publishing a Discourse types package which can be added to theme/plugin package.json files for development purposes.
2023-10-18 07:13:20 -04:00
"@babel/helper-module-transforms@^7.23.0":
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
version "7.23.0"
resolved "https://registry.yarnpkg.com/@babel/helper-module-transforms/-/helper-module-transforms-7.23.0.tgz#3ec246457f6c842c0aee62a01f60739906f7047e"
integrity sha512-WhDWw1tdrlT0gMgUJSlX0IQvoO1eN279zrAUbVB+KpV2c3Tylz8+GnKOLllCS6Z/iZQEyVYxhZVUdPTqs2YYPw==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
dependencies:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@babel/helper-environment-visitor" "^7.22.20"
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
"@babel/helper-module-imports" "^7.22.15"
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
"@babel/helper-simple-access" "^7.22.5"
"@babel/helper-split-export-declaration" "^7.22.6"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@babel/helper-validator-identifier" "^7.22.20"
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
"@babel/helper-optimise-call-expression@^7.22.5":
version "7.22.5"
resolved "https://registry.yarnpkg.com/@babel/helper-optimise-call-expression/-/helper-optimise-call-expression-7.22.5.tgz#f21531a9ccbff644fdd156b4077c16ff0c3f609e"
integrity sha512-HBwaojN0xFRx4yIvpwGqxiV2tUfl7401jlok564NgB9EHS1y6QT17FmKWm4ztqjeVdXLuC4fSvHc5ePpQjoTbw==
dependencies:
"@babel/types" "^7.22.5"
"@babel/helper-plugin-utils@^7.22.5":
version "7.22.5"
resolved "https://registry.yarnpkg.com/@babel/helper-plugin-utils/-/helper-plugin-utils-7.22.5.tgz#dd7ee3735e8a313b9f7b05a773d892e88e6d7295"
integrity sha512-uLls06UVKgFG9QD4OeFYLEGteMIAa5kpTPcFL28yuCIIzsf6ZyKZMllKVOCZFhiZ5ptnwX4mtKdWCBE/uT4amg==
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@babel/helper-replace-supers@^7.22.20", "@babel/helper-replace-supers@^7.22.9":
version "7.22.20"
resolved "https://registry.yarnpkg.com/@babel/helper-replace-supers/-/helper-replace-supers-7.22.20.tgz#e37d367123ca98fe455a9887734ed2e16eb7a793"
integrity sha512-qsW0In3dbwQUbK8kejJ4R7IHVGwHJlV6lpG6UA7a9hSa2YEiAib+N1T2kr6PEeUT+Fl7najmSOS6SmAwCHK6Tw==
DEV: Introduce decorator-position lint rule (#22937)
2023-08-04 07:26:06 -04:00
dependencies:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@babel/helper-environment-visitor" "^7.22.20"
"@babel/helper-member-expression-to-functions" "^7.22.15"
DEV: Introduce decorator-position lint rule (#22937)
2023-08-04 07:26:06 -04:00
"@babel/helper-optimise-call-expression" "^7.22.5"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
"@babel/helper-simple-access@^7.22.5":
version "7.22.5"
resolved "https://registry.yarnpkg.com/@babel/helper-simple-access/-/helper-simple-access-7.22.5.tgz#4938357dc7d782b80ed6dbb03a0fba3d22b1d5de"
integrity sha512-n0H99E/K+Bika3++WNL17POvo4rKWZ7lZEp1Q+fStVbUi8nxPQEBOlTmCOxW/0JsS56SKKQ+ojAe2pHKJHN35w==
dependencies:
"@babel/types" "^7.22.5"
"@babel/helper-skip-transparent-expression-wrappers@^7.22.5":
version "7.22.5"
resolved "https://registry.yarnpkg.com/@babel/helper-skip-transparent-expression-wrappers/-/helper-skip-transparent-expression-wrappers-7.22.5.tgz#007f15240b5751c537c40e77abb4e89eeaaa8847"
integrity sha512-tK14r66JZKiC43p8Ki33yLBVJKlQDFoA8GYN67lWCDCqoL6EMMSuM9b+Iff2jHaM/RRFYl7K+iiru7hbRqNx8Q==
dependencies:
"@babel/types" "^7.22.5"
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
"@babel/helper-split-export-declaration@^7.22.6":
version "7.22.6"
resolved "https://registry.yarnpkg.com/@babel/helper-split-export-declaration/-/helper-split-export-declaration-7.22.6.tgz#322c61b7310c0997fe4c323955667f18fcefb91c"
integrity sha512-AsUnxuLhRYsisFiaJwvp1QF+I3KjD5FOxut14q/GzovUe6orHLesW2C7d754kRm53h5gqrz6sFl6sxc4BVtE/g==
dependencies:
"@babel/types" "^7.22.5"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
"@babel/helper-string-parser@^7.22.5":
version "7.22.5"
resolved "https://registry.yarnpkg.com/@babel/helper-string-parser/-/helper-string-parser-7.22.5.tgz#533f36457a25814cf1df6488523ad547d784a99f"
integrity sha512-mM4COjgZox8U+JcXQwPijIZLElkgEpO5rsERVDJTc2qfCDfERyob6k5WegS14SX18IIjv+XD+GrqNumY5JRCDw==
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@babel/helper-validator-identifier@^7.22.20":
version "7.22.20"
resolved "https://registry.yarnpkg.com/@babel/helper-validator-identifier/-/helper-validator-identifier-7.22.20.tgz#c4ae002c61d2879e724581d96665583dbc1dc0e0"
integrity sha512-Y4OZ+ytlatR8AI+8KZfKuL5urKp7qey08ha31L8b3BwewJAoJamTzyvxPR/5D+KkdJCGPq/+8TukHBlY10FX9A==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
"@babel/helper-validator-option@^7.22.15":
version "7.22.15"
resolved "https://registry.yarnpkg.com/@babel/helper-validator-option/-/helper-validator-option-7.22.15.tgz#694c30dfa1d09a6534cdfcafbe56789d36aba040"
integrity sha512-bMn7RmyFjY/mdECUbgn9eoSY4vqvacUnS9i9vGAGttgFWesO6B4CYWA7XlpbWgBt71iv/hfbPlynohStqnu5hA==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
"@babel/helpers@^7.23.2":
version "7.23.2"
resolved "https://registry.yarnpkg.com/@babel/helpers/-/helpers-7.23.2.tgz#2832549a6e37d484286e15ba36a5330483cac767"
integrity sha512-lzchcp8SjTSVe/fPmLwtWVBFC7+Tbn8LGHDVfDp9JGxpAY5opSaEFgt8UQvrnECWOTdji2mOWMz1rOhkHscmGQ==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
dependencies:
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
"@babel/template" "^7.22.15"
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
"@babel/traverse" "^7.23.2"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@babel/types" "^7.23.0"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
"@babel/highlight@^7.22.13":
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
version "7.22.20"
resolved "https://registry.yarnpkg.com/@babel/highlight/-/highlight-7.22.20.tgz#4ca92b71d80554b01427815e06f2df965b9c1f54"
integrity sha512-dkdMCN3py0+ksCgYmGG8jKeGA/8Tk+gJwSYYlFGxG5lmhfKNoAy004YpLxpS1W2J8m/EK2Ew+yOs9pVRwO89mg==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
dependencies:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@babel/helper-validator-identifier" "^7.22.20"
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
chalk "^2.4.2"
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
js-tokens "^4.0.0"
DEV: Rename I18n imports to discourse-i18n (#23915) As of #23867 this is now a real package, so updating the imports to use the real package name, rather than relying on the alias. The name change in the package name is because `I18n` is not a valid name as NPM packages must be all lowercase. This commit also introduces an eslint rule to prevent importing from the old I18n path. For themes/plugins, the old 'i18n' name remains functional.
2023-10-18 06:07:09 -04:00
"@babel/parser@^7.20.15", "@babel/parser@^7.22.15", "@babel/parser@^7.23.0", "@babel/parser@^7.9.4":
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
version "7.23.0"
resolved "https://registry.yarnpkg.com/@babel/parser/-/parser-7.23.0.tgz#da950e622420bf96ca0d0f2909cdddac3acd8719"
integrity sha512-vvPKKdMemU85V9WE/l5wZEmImpCtLqbnTvqDS2U1fJ96KrxoW7KrXhNsNCblQlg8Ck4b85yxdTyelsMUgFUXiw==
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
"@babel/plugin-proposal-decorators@^7.18.6", "@babel/plugin-proposal-decorators@^7.23.2":
version "7.23.2"
resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-decorators/-/plugin-proposal-decorators-7.23.2.tgz#0b345a5754f48309fa50b7cd99075ef0295b12c8"
integrity sha512-eR0gJQc830fJVGz37oKLvt9W9uUIQSAovUl0e9sJ3YeO09dlcoBVYD3CLrjCj4qHdXmfiyTyFt8yeQYSN5fxLg==
DEV: Introduce decorator-position lint rule (#22937)
2023-08-04 07:26:06 -04:00
dependencies:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@babel/helper-create-class-features-plugin" "^7.22.15"
DEV: Introduce decorator-position lint rule (#22937)
2023-08-04 07:26:06 -04:00
"@babel/helper-plugin-utils" "^7.22.5"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@babel/helper-replace-supers" "^7.22.20"
DEV: Introduce decorator-position lint rule (#22937)
2023-08-04 07:26:06 -04:00
"@babel/helper-split-export-declaration" "^7.22.6"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@babel/plugin-syntax-decorators" "^7.22.10"
DEV: Introduce decorator-position lint rule (#22937)
2023-08-04 07:26:06 -04:00
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@babel/plugin-syntax-decorators@^7.22.10":
version "7.22.10"
resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-decorators/-/plugin-syntax-decorators-7.22.10.tgz#7d83ea04d893c442b78ebf4c3cbac59a7211deff"
integrity sha512-z1KTVemBjnz+kSEilAsI4lbkPOl5TvJH7YDSY1CTIzvLWJ+KHXp+mRe8VPmfnyvqOPqar1V2gid2PleKzRUstQ==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
dependencies:
"@babel/helper-plugin-utils" "^7.22.5"
"@babel/runtime@^7.21.0":
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
version "7.23.2"
resolved "https://registry.yarnpkg.com/@babel/runtime/-/runtime-7.23.2.tgz#062b0ac103261d68a966c4c7baf2ae3e62ec3885"
integrity sha512-mM8eg4yl5D6i3lu2QKPuPH4FArvJ8KhTofbE7jwMUv9KX5mBvwPAqnV3MlyBNqdp9RyRKP6Yck8TrfYrPvX3bg==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
dependencies:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
regenerator-runtime "^0.14.0"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@babel/template@^7.22.15":
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
version "7.22.15"
resolved "https://registry.yarnpkg.com/@babel/template/-/template-7.22.15.tgz#09576efc3830f0430f4548ef971dde1350ef2f38"
integrity sha512-QPErUVm4uyJa60rkI73qneDacvdvzxshT3kksGqlGWYdOTIUOwJ7RDUL8sGqslY1uXWSL6xMFKEXDS3ox2uF0w==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
dependencies:
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
"@babel/code-frame" "^7.22.13"
"@babel/parser" "^7.22.15"
"@babel/types" "^7.22.15"
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
"@babel/traverse@^7.23.2":
Build(deps): Bump @babel/traverse from 7.23.0 to 7.23.2 (#23949) Bumps [@babel/traverse](https://github.com/babel/babel/tree/HEAD/packages/babel-traverse) from 7.23.0 to 7.23.2. - [Release notes](https://github.com/babel/babel/releases) - [Changelog](https://github.com/babel/babel/blob/main/CHANGELOG.md) - [Commits](https://github.com/babel/babel/commits/v7.23.2/packages/babel-traverse) --- updated-dependencies: - dependency-name: "@babel/traverse" dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-10-17 07:43:12 -04:00
version "7.23.2"
resolved "https://registry.yarnpkg.com/@babel/traverse/-/traverse-7.23.2.tgz#329c7a06735e144a506bdb2cad0268b7f46f4ad8"
integrity sha512-azpe59SQ48qG6nu2CzcMLbxUudtN+dOM9kDbUqGq3HXUJRlo7i8fvPoxQUzYgLZ4cMVmuZgm8vvBpNeRhd6XSw==
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
dependencies:
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
"@babel/code-frame" "^7.22.13"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@babel/generator" "^7.23.0"
"@babel/helper-environment-visitor" "^7.22.20"
"@babel/helper-function-name" "^7.23.0"
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
"@babel/helper-hoist-variables" "^7.22.5"
"@babel/helper-split-export-declaration" "^7.22.6"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@babel/parser" "^7.23.0"
"@babel/types" "^7.23.0"
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
debug "^4.1.0"
globals "^11.1.0"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@babel/types@^7.22.15", "@babel/types@^7.22.5", "@babel/types@^7.23.0":
version "7.23.0"
resolved "https://registry.yarnpkg.com/@babel/types/-/types-7.23.0.tgz#8c1f020c9df0e737e4e247c0619f58c68458aaeb"
integrity sha512-0oIyUfKoI3mSqMvsxBdclDwxXKXAUA8v/apZbc+iSyARYou1o8ZGDxbUYyLFoW2arqS2jDGqJuZvv1d/io1axg==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
dependencies:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
"@babel/helper-string-parser" "^7.22.5"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@babel/helper-validator-identifier" "^7.22.20"
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
to-fast-properties "^2.0.0"
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
"@discourse/lint-configs@^1.0.0":
version "1.0.0"
resolved "https://registry.yarnpkg.com/@discourse/lint-configs/-/lint-configs-1.0.0.tgz#683ebeebfdf9e75b18ad69bbeff584206bde3e20"
integrity sha512-8+xJ5ZRCsuQ+Mov5YiWsrYBJVj+H+JL9jyNctt5QFz79vfb1VLut4/4Kq58v0xh0pTT43bL1d4fEM+XllHmpCQ==
dependencies:
"@babel/core" "^7.23.2"
"@babel/eslint-parser" "^7.22.15"
"@babel/plugin-proposal-decorators" "^7.23.2"
ember-template-lint "^5.11.2"
eslint "^8.51.0"
eslint-plugin-decorator-position "^5.0.2"
eslint-plugin-ember "^11.11.1"
eslint-plugin-simple-import-sort "^10.0.0"
eslint-plugin-sort-class-members "^1.19.0"
globals "^13.23.0"
prettier "^2.8.8"
prettier-plugin-ember-template-tag "^0.3.2"
FIX: Regression in timezone name localizations (#15761) This also switches to using the NPM package for better build stability. And adds a clearer label in the alert that is displayed to show your current timezone (when changing timezones).
2022-02-02 17:41:42 -05:00
"@discourse/moment-timezone-names-translations@^1.0.0":
version "1.0.0"
resolved "https://registry.yarnpkg.com/@discourse/moment-timezone-names-translations/-/moment-timezone-names-translations-1.0.0.tgz#b22344456513d37c81baf384a41487b539b91534"
integrity sha512-4xr1QWQ0nzmFa2ZXQgWZA+dtE/BU2ePA+qkJWPFzNpq4ZnQi8MmMMAS2285t3rc2ySMBQqYaAArmcSUiufUgRA==
DEV: Don't lint core files when target == plugins (#10259) * DEV: Don't lint core files when target == plugins * Prettier the plugin/*.js files * Update eslintignore/prettierignore * Add eslint-plugin-ember and eslint-plugin-node * Properly lint all js files in all plugins * LINT: run prettier on test/*.js files * DEV: Run prettier checks on test/*.js files * ESLint plugins' assets/javascripts and test/javascripts directories only
2020-08-25 05:40:40 -04:00
"@ember-data/rfc395-data@^0.0.4":
version "0.0.4"
resolved "https://registry.yarnpkg.com/@ember-data/rfc395-data/-/rfc395-data-0.0.4.tgz#ecb86efdf5d7733a76ff14ea651a1b0ed1f8a843"
integrity sha512-tGRdvgC9/QMQSuSuJV45xoyhI0Pzjm7A9o/MVVA3HakXIImJbbzx/k/6dO9CUEQXIyS2y0fW6C1XaYOG7rY0FQ==
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
"@ember/edition-utils@^1.2.0":
version "1.2.0"
resolved "https://registry.yarnpkg.com/@ember/edition-utils/-/edition-utils-1.2.0.tgz#a039f542dc14c8e8299c81cd5abba95e2459cfa6"
integrity sha512-VmVq/8saCaPdesQmftPqbFtxJWrzxNGSQ+e8x8LLe3Hjm36pJ04Q8LeORGZkAeOhldoUX9seLGmSaHeXkIqoog==
DEV: Use esbuild to make DiscourseJsProcessor (#23223) Reverts e2705df and re-lands #23187 and #23219. The issue was incorrect order of execution of Rails' `assets:precompile` task in our own precompilation stack. Co-authored-by: David Taylor <david@taylorhq.com>
2023-08-24 10:36:22 -04:00
"@esbuild/android-arm64@0.19.2":
version "0.19.2"
resolved "https://registry.yarnpkg.com/@esbuild/android-arm64/-/android-arm64-0.19.2.tgz#bc35990f412a749e948b792825eef7df0ce0e073"
integrity sha512-lsB65vAbe90I/Qe10OjkmrdxSX4UJDjosDgb8sZUKcg3oefEuW2OT2Vozz8ef7wrJbMcmhvCC+hciF8jY/uAkw==
"@esbuild/android-arm@0.19.2":
version "0.19.2"
resolved "https://registry.yarnpkg.com/@esbuild/android-arm/-/android-arm-0.19.2.tgz#edd1c8f23ba353c197f5b0337123c58ff2a56999"
integrity sha512-tM8yLeYVe7pRyAu9VMi/Q7aunpLwD139EY1S99xbQkT4/q2qa6eA4ige/WJQYdJ8GBL1K33pPFhPfPdJ/WzT8Q==
"@esbuild/android-x64@0.19.2":
version "0.19.2"
resolved "https://registry.yarnpkg.com/@esbuild/android-x64/-/android-x64-0.19.2.tgz#2dcdd6e6f1f2d82ea1b746abd8da5b284960f35a"
integrity sha512-qK/TpmHt2M/Hg82WXHRc/W/2SGo/l1thtDHZWqFq7oi24AjZ4O/CpPSu6ZuYKFkEgmZlFoa7CooAyYmuvnaG8w==
"@esbuild/darwin-arm64@0.19.2":
version "0.19.2"
resolved "https://registry.yarnpkg.com/@esbuild/darwin-arm64/-/darwin-arm64-0.19.2.tgz#55b36bc06d76f5c243987c1f93a11a80d8fc3b26"
integrity sha512-Ora8JokrvrzEPEpZO18ZYXkH4asCdc1DLdcVy8TGf5eWtPO1Ie4WroEJzwI52ZGtpODy3+m0a2yEX9l+KUn0tA==
"@esbuild/darwin-x64@0.19.2":
version "0.19.2"
resolved "https://registry.yarnpkg.com/@esbuild/darwin-x64/-/darwin-x64-0.19.2.tgz#982524af33a6424a3b5cb44bbd52559623ad719c"
integrity sha512-tP+B5UuIbbFMj2hQaUr6EALlHOIOmlLM2FK7jeFBobPy2ERdohI4Ka6ZFjZ1ZYsrHE/hZimGuU90jusRE0pwDw==
"@esbuild/freebsd-arm64@0.19.2":
version "0.19.2"
resolved "https://registry.yarnpkg.com/@esbuild/freebsd-arm64/-/freebsd-arm64-0.19.2.tgz#8e478a0856645265fe79eac4b31b52193011ee06"
integrity sha512-YbPY2kc0acfzL1VPVK6EnAlig4f+l8xmq36OZkU0jzBVHcOTyQDhnKQaLzZudNJQyymd9OqQezeaBgkTGdTGeQ==
"@esbuild/freebsd-x64@0.19.2":
version "0.19.2"
resolved "https://registry.yarnpkg.com/@esbuild/freebsd-x64/-/freebsd-x64-0.19.2.tgz#01b96604f2540db023c73809bb8ae6cd1692d6f3"
integrity sha512-nSO5uZT2clM6hosjWHAsS15hLrwCvIWx+b2e3lZ3MwbYSaXwvfO528OF+dLjas1g3bZonciivI8qKR/Hm7IWGw==
"@esbuild/linux-arm64@0.19.2":
version "0.19.2"
resolved "https://registry.yarnpkg.com/@esbuild/linux-arm64/-/linux-arm64-0.19.2.tgz#7e5d2c7864c5c83ec789b59c77cd9c20d2594916"
integrity sha512-ig2P7GeG//zWlU0AggA3pV1h5gdix0MA3wgB+NsnBXViwiGgY77fuN9Wr5uoCrs2YzaYfogXgsWZbm+HGr09xg==
"@esbuild/linux-arm@0.19.2":
version "0.19.2"
resolved "https://registry.yarnpkg.com/@esbuild/linux-arm/-/linux-arm-0.19.2.tgz#c32ae97bc0246664a1cfbdb4a98e7b006d7db8ae"
integrity sha512-Odalh8hICg7SOD7XCj0YLpYCEc+6mkoq63UnExDCiRA2wXEmGlK5JVrW50vZR9Qz4qkvqnHcpH+OFEggO3PgTg==
"@esbuild/linux-ia32@0.19.2":
version "0.19.2"
resolved "https://registry.yarnpkg.com/@esbuild/linux-ia32/-/linux-ia32-0.19.2.tgz#3fc4f0fa026057fe885e4a180b3956e704f1ceaa"
integrity sha512-mLfp0ziRPOLSTek0Gd9T5B8AtzKAkoZE70fneiiyPlSnUKKI4lp+mGEnQXcQEHLJAcIYDPSyBvsUbKUG2ri/XQ==
"@esbuild/linux-loong64@0.19.2":
version "0.19.2"
resolved "https://registry.yarnpkg.com/@esbuild/linux-loong64/-/linux-loong64-0.19.2.tgz#633bcaea443f3505fb0ed109ab840c99ad3451a4"
integrity sha512-hn28+JNDTxxCpnYjdDYVMNTR3SKavyLlCHHkufHV91fkewpIyQchS1d8wSbmXhs1fiYDpNww8KTFlJ1dHsxeSw==
"@esbuild/linux-mips64el@0.19.2":
version "0.19.2"
resolved "https://registry.yarnpkg.com/@esbuild/linux-mips64el/-/linux-mips64el-0.19.2.tgz#e0bff2898c46f52be7d4dbbcca8b887890805823"
integrity sha512-KbXaC0Sejt7vD2fEgPoIKb6nxkfYW9OmFUK9XQE4//PvGIxNIfPk1NmlHmMg6f25x57rpmEFrn1OotASYIAaTg==
"@esbuild/linux-ppc64@0.19.2":
version "0.19.2"
resolved "https://registry.yarnpkg.com/@esbuild/linux-ppc64/-/linux-ppc64-0.19.2.tgz#d75798da391f54a9674f8c143b9a52d1dbfbfdde"
integrity sha512-dJ0kE8KTqbiHtA3Fc/zn7lCd7pqVr4JcT0JqOnbj4LLzYnp+7h8Qi4yjfq42ZlHfhOCM42rBh0EwHYLL6LEzcw==
"@esbuild/linux-riscv64@0.19.2":
version "0.19.2"
resolved "https://registry.yarnpkg.com/@esbuild/linux-riscv64/-/linux-riscv64-0.19.2.tgz#012409bd489ed1bb9b775541d4a46c5ded8e6dd8"
integrity sha512-7Z/jKNFufZ/bbu4INqqCN6DDlrmOTmdw6D0gH+6Y7auok2r02Ur661qPuXidPOJ+FSgbEeQnnAGgsVynfLuOEw==
"@esbuild/linux-s390x@0.19.2":
version "0.19.2"
resolved "https://registry.yarnpkg.com/@esbuild/linux-s390x/-/linux-s390x-0.19.2.tgz#ece3ed75c5a150de8a5c110f02e97d315761626b"
integrity sha512-U+RinR6aXXABFCcAY4gSlv4CL1oOVvSSCdseQmGO66H+XyuQGZIUdhG56SZaDJQcLmrSfRmx5XZOWyCJPRqS7g==
"@esbuild/linux-x64@0.19.2":
version "0.19.2"
resolved "https://registry.yarnpkg.com/@esbuild/linux-x64/-/linux-x64-0.19.2.tgz#dea187019741602d57aaf189a80abba261fbd2aa"
integrity sha512-oxzHTEv6VPm3XXNaHPyUTTte+3wGv7qVQtqaZCrgstI16gCuhNOtBXLEBkBREP57YTd68P0VgDgG73jSD8bwXQ==
"@esbuild/netbsd-x64@0.19.2":
version "0.19.2"
resolved "https://registry.yarnpkg.com/@esbuild/netbsd-x64/-/netbsd-x64-0.19.2.tgz#bbfd7cf9ab236a23ee3a41b26f0628c57623d92a"
integrity sha512-WNa5zZk1XpTTwMDompZmvQLHszDDDN7lYjEHCUmAGB83Bgs20EMs7ICD+oKeT6xt4phV4NDdSi/8OfjPbSbZfQ==
"@esbuild/openbsd-x64@0.19.2":
version "0.19.2"
resolved "https://registry.yarnpkg.com/@esbuild/openbsd-x64/-/openbsd-x64-0.19.2.tgz#fa5c4c6ee52a360618f00053652e2902e1d7b4a7"
integrity sha512-S6kI1aT3S++Dedb7vxIuUOb3oAxqxk2Rh5rOXOTYnzN8JzW1VzBd+IqPiSpgitu45042SYD3HCoEyhLKQcDFDw==
"@esbuild/sunos-x64@0.19.2":
version "0.19.2"
resolved "https://registry.yarnpkg.com/@esbuild/sunos-x64/-/sunos-x64-0.19.2.tgz#52a2ac8ac6284c02d25df22bb4cfde26fbddd68d"
integrity sha512-VXSSMsmb+Z8LbsQGcBMiM+fYObDNRm8p7tkUDMPG/g4fhFX5DEFmjxIEa3N8Zr96SjsJ1woAhF0DUnS3MF3ARw==
"@esbuild/win32-arm64@0.19.2":
version "0.19.2"
resolved "https://registry.yarnpkg.com/@esbuild/win32-arm64/-/win32-arm64-0.19.2.tgz#719ed5870855de8537aef8149694a97d03486804"
integrity sha512-5NayUlSAyb5PQYFAU9x3bHdsqB88RC3aM9lKDAz4X1mo/EchMIT1Q+pSeBXNgkfNmRecLXA0O8xP+x8V+g/LKg==
"@esbuild/win32-ia32@0.19.2":
version "0.19.2"
resolved "https://registry.yarnpkg.com/@esbuild/win32-ia32/-/win32-ia32-0.19.2.tgz#24832223880b0f581962c8660f8fb8797a1e046a"
integrity sha512-47gL/ek1v36iN0wL9L4Q2MFdujR0poLZMJwhO2/N3gA89jgHp4MR8DKCmwYtGNksbfJb9JoTtbkoe6sDhg2QTA==
"@esbuild/win32-x64@0.19.2":
version "0.19.2"
resolved "https://registry.yarnpkg.com/@esbuild/win32-x64/-/win32-x64-0.19.2.tgz#1205014625790c7ff0e471644a878a65d1e34ab0"
integrity sha512-tcuhV7ncXBqbt/Ybf0IyrMcwVOAPDckMK9rXNHtF17UTK18OKLpg08glminN06pt2WCoALhXdLfSPbVvK/6fxw==
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
"@eslint-community/eslint-utils@^4.2.0":
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
version "4.4.0"
resolved "https://registry.yarnpkg.com/@eslint-community/eslint-utils/-/eslint-utils-4.4.0.tgz#a23514e8fb9af1269d5f7788aa556798d61c6b59"
integrity sha512-1/sA4dwrzBAyeUoQ6oxahHKmrZvsnLCg4RfxW3ZFGGmQkSNQPFNLV9CUEFQP1x9EYXHTo5p6xdhZM1Ne9p/AfA==
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
dependencies:
eslint-visitor-keys "^3.3.0"
DEV: Consolidate and update jsconfig, and add types packages (#23824) These updates significantly improve IDE tooling for imports across the Discourse core codebase, and also for framework packages. The `@types/ember-*` packages are a temporary solution until we get onto Ember 5, which ships its types in the main package. The previous approach of having jsconfig files in each package directory did work, but once you start adding all the possible interlinks between them, we hit the file count limit of VSCode's tooling (because it counts every file for every jsconfig its referenced in). Having one file at the root means that a single file can apply to all core packages and plugins. Long-term, to get the same functionality for all themes/plugins, we may need to look at building/publishing a Discourse types package which can be added to theme/plugin package.json files for development purposes.
2023-10-18 07:13:20 -04:00
"@eslint-community/regexpp@^4.6.1":
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
version "4.9.1"
resolved "https://registry.yarnpkg.com/@eslint-community/regexpp/-/regexpp-4.9.1.tgz#449dfa81a57a1d755b09aa58d826c1262e4283b4"
integrity sha512-Y27x+MBLjXa+0JWDhykM3+JE+il3kHKAEqabfEWq3SDhZjLYb6/BHL/JKFnH3fe207JaXkyDo685Oc2Glt6ifA==
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
DEV: Consolidate and update jsconfig, and add types packages (#23824) These updates significantly improve IDE tooling for imports across the Discourse core codebase, and also for framework packages. The `@types/ember-*` packages are a temporary solution until we get onto Ember 5, which ships its types in the main package. The previous approach of having jsconfig files in each package directory did work, but once you start adding all the possible interlinks between them, we hit the file count limit of VSCode's tooling (because it counts every file for every jsconfig its referenced in). Having one file at the root means that a single file can apply to all core packages and plugins. Long-term, to get the same functionality for all themes/plugins, we may need to look at building/publishing a Discourse types package which can be added to theme/plugin package.json files for development purposes.
2023-10-18 07:13:20 -04:00
"@eslint/eslintrc@^2.1.2":
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
version "2.1.2"
resolved "https://registry.yarnpkg.com/@eslint/eslintrc/-/eslintrc-2.1.2.tgz#c6936b4b328c64496692f76944e755738be62396"
integrity sha512-+wvgpDsrB1YqAMdEUCcnTlpfVBH7Vqn6A/NT3D8WVXFIaKMlErPIZT3oCIAVCOtarRpMtelZLqJeU3t7WY6X6g==
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
dependencies:
ajv "^6.12.4"
debug "^4.3.2"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
espree "^9.6.0"
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
globals "^13.19.0"
ignore "^5.2.0"
import-fresh "^3.2.1"
js-yaml "^4.1.0"
minimatch "^3.1.2"
strip-json-comments "^3.1.1"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@eslint/js@8.51.0":
version "8.51.0"
resolved "https://registry.yarnpkg.com/@eslint/js/-/js-8.51.0.tgz#6d419c240cfb2b66da37df230f7e7eef801c32fa"
integrity sha512-HxjQ8Qn+4SI3/AFv6sOrDB+g6PpUTDwSJiQqOrnneEk8L71161srI9gjzzZvYVbzHiVg/BvcH95+cK/zfIt4pg==
DEV: Update Font Awesome to 5.15.4
2022-02-03 10:16:17 -05:00
"@fortawesome/fontawesome-free@5.15.4":
version "5.15.4"
resolved "https://registry.yarnpkg.com/@fortawesome/fontawesome-free/-/fontawesome-free-5.15.4.tgz#ecda5712b61ac852c760d8b3c79c96adca5554e5"
integrity sha512-eYm8vijH/hpzr/6/1CJ/V/Eb1xQFW2nnUKArb3z+yUWv7HTwj6M7SP957oMjfZjAHU6qpoNc2wQvIxBLWYa/Jg==
Upgrade to FontAwesome 5 (take two) (#6673) * Add missing icons to set * Revert FA5 revert This reverts commit 42572ff * use new SVG syntax in locales * Noscript page changes (remove login button, center "powered by" footer text) * Cast wider net for SVG icons in settings - include any _icon setting for SVG registry (offers better support for plugin settings) - let themes store multiple pipe-delimited icons in a setting - also replaces broken onebox image icon with SVG reference in cooked post processor * interpolate icons in locales * Fix composer whisper icon alignment * Add support for stacked icons * SECURITY: enforce hostname to match discourse hostname This ensures that the hostname rails uses for various helpers always matches the Discourse hostname * load SVG sprite with pre-initializers * FIX: enable caching on SVG sprites * PERF: use JSONP for SVG sprites so they are served from CDN This avoids needing to deal with CORS for loading of the SVG Note, added the svg- prefix to the filename so we can quickly tell in dev tools what the file is * Add missing SVG sprite JSONP script to CSP * Upgrade to FA 5.5.0 * Add support for all FA4.7 icons - adds complete frontend and backend for renamed FA4.7 icons - improves performance of SvgSprite.bundle and SvgSprite.all_icons * Fix group avatar flair preview - adds an endpoint at /svg-sprites/search/:keyword - adds frontend ajax call that pulls icon in avatar flair preview even when it is not in subset * Remove FA 4.7 font files
2018-11-26 16:49:57 -05:00
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
"@glimmer/env@0.1.7", "@glimmer/env@^0.1.7":
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
version "0.1.7"
resolved "https://registry.yarnpkg.com/@glimmer/env/-/env-0.1.7.tgz#fd2d2b55a9029c6b37a6c935e8c8871ae70dfa07"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
integrity sha512-JKF/a9I9jw6fGoz8kA7LEQslrwJ5jms5CXhu/aqkBWk+PmZ6pTl8mlb/eJ/5ujBGTiQzBhy5AIWF712iA+4/mw==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
"@glimmer/global-context@0.84.3":
version "0.84.3"
resolved "https://registry.yarnpkg.com/@glimmer/global-context/-/global-context-0.84.3.tgz#f8bf2cda9562716f2ddf3f96837e7559600635c4"
integrity sha512-8Oy9Wg5IZxMEeAnVmzD2NkObf89BeHoFSzJgJROE/deutd3rxg83mvlOez4zBBGYwnTb+VGU2LYRpet92egJjA==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
dependencies:
"@glimmer/env" "^0.1.7"
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
"@glimmer/interfaces@0.84.3":
version "0.84.3"
resolved "https://registry.yarnpkg.com/@glimmer/interfaces/-/interfaces-0.84.3.tgz#629777a4abe373b0785656f6c8d08989f5784805"
integrity sha512-dk32ykoNojt0mvEaIW6Vli5MGTbQo58uy3Epj7ahCgTHmWOKuw/0G83f2UmFprRwFx689YTXG38I/vbpltEjzg==
Support for Ember Template linting
2020-02-05 11:33:15 -05:00
dependencies:
"@simple-dom/interface" "^1.4.0"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
"@glimmer/reference@^0.84.3":
version "0.84.3"
resolved "https://registry.yarnpkg.com/@glimmer/reference/-/reference-0.84.3.tgz#6420ad9c102633ac83939fd1b2457269d21fb632"
integrity sha512-lV+p/aWPVC8vUjmlvYVU7WQJsLh319SdXuAWoX/SE3pq340BJlAJiEcAc6q52y9JNhT57gMwtjMX96W5Xcx/qw==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
dependencies:
"@glimmer/env" "^0.1.7"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
"@glimmer/global-context" "0.84.3"
"@glimmer/interfaces" "0.84.3"
"@glimmer/util" "0.84.3"
"@glimmer/validator" "0.84.3"
"@glimmer/syntax@^0.84.2", "@glimmer/syntax@^0.84.3":
version "0.84.3"
resolved "https://registry.yarnpkg.com/@glimmer/syntax/-/syntax-0.84.3.tgz#4045a1708cef7fd810cff42fe6deeba40c7286d0"
integrity sha512-ioVbTic6ZisLxqTgRBL2PCjYZTFIwobifCustrozRU2xGDiYvVIL0vt25h2c1ioDsX59UgVlDkIK4YTAQQSd2A==
dependencies:
"@glimmer/interfaces" "0.84.3"
"@glimmer/util" "0.84.3"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
"@handlebars/parser" "~2.0.0"
simple-html-tokenizer "^0.5.11"
Support for Ember Template linting
2020-02-05 11:33:15 -05:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
"@glimmer/util@0.84.3":
version "0.84.3"
resolved "https://registry.yarnpkg.com/@glimmer/util/-/util-0.84.3.tgz#9ae0166982c0b48aa94b02d6ba8c2c81976ade4b"
integrity sha512-qFkh6s16ZSRuu2rfz3T4Wp0fylFj3HBsONGXQcrAdZjdUaIS6v3pNj6mecJ71qRgcym9Hbaq/7/fefIwECUiKw==
DEV: Merge package.json files (#21172) This means: a single yarn.lock and removing one of the package.json files
2023-04-20 06:46:12 -04:00
dependencies:
"@glimmer/env" "0.1.7"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
"@glimmer/interfaces" "0.84.3"
DEV: Merge package.json files (#21172) This means: a single yarn.lock and removing one of the package.json files
2023-04-20 06:46:12 -04:00
"@simple-dom/interface" "^1.4.0"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
"@glimmer/validator@0.84.3", "@glimmer/validator@^0.84.3":
version "0.84.3"
resolved "https://registry.yarnpkg.com/@glimmer/validator/-/validator-0.84.3.tgz#cd83b7f9ab78953f23cc11a32d83d7f729c54df2"
integrity sha512-RTBV4TokUB0vI31UC7ikpV7lOYpWUlyqaKV//pRC4pexYMlmqnVhkFrdiimB/R1XyNdUOQUmnIAcdic39NkbhQ==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
dependencies:
"@glimmer/env" "^0.1.7"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
"@glimmer/global-context" "0.84.3"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
"@glint/core@^1.1.0":
version "1.1.0"
resolved "https://registry.yarnpkg.com/@glint/core/-/core-1.1.0.tgz#b89600b59fcfac7a112615510ea05c08f985d3d9"
integrity sha512-SeAdKrQF65NRDzzmkwUC0VRZjBDysQXeIKXhyCUtXaatFDeyC0zdESJRcUykMdQoI5R6MKcts2X3gthLRuEGKA==
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
dependencies:
"@glimmer/syntax" "^0.84.2"
escape-string-regexp "^4.0.0"
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
semver "^7.5.2"
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
silent-error "^1.1.1"
uuid "^8.3.2"
vscode-languageserver "^8.0.1"
vscode-languageserver-textdocument "^1.0.5"
vscode-uri "^3.0.2"
yargs "^17.5.1"
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
"@glint/environment-ember-loose@^1.1.0":
version "1.1.0"
resolved "https://registry.yarnpkg.com/@glint/environment-ember-loose/-/environment-ember-loose-1.1.0.tgz#b0e3a321376924cd74c9bb741fdfd99a04d9f363"
integrity sha512-Qwr3OAptRZ8zqxaPvpVBdbSiiImYMRNu+0IPQGaDutqOV80GzWYeiMuEyPC0Nwy4mQ3991YxE24Q+a5/FTfTNw==
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
"@glint/environment-ember-template-imports@^1.1.0":
version "1.1.0"
resolved "https://registry.yarnpkg.com/@glint/environment-ember-template-imports/-/environment-ember-template-imports-1.1.0.tgz#908ec8b38a5837f4c28b12e4a3fe6c547366d37a"
integrity sha512-duNk2NzDilNctzz+XHecICfMMt8LjLEhaWPiBvFfFeLW35gqZo2XQpeBQI/pq2gH0ZbWOP7rr9Kde12v7ossZg==
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
"@glint/template@^1.1.0":
version "1.1.0"
resolved "https://registry.yarnpkg.com/@glint/template/-/template-1.1.0.tgz#5734f8f4d9f425676c97bb701c9af03dd2e783ab"
integrity sha512-gK4tifrw7mIMYECzGeG5jrez2lY0TlwE584cnoYOFhzxXKrsuungdiebd7LDwjvfQpImQd1JUSQr3u/uF/XYJg==
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
"@handlebars/parser@~2.0.0":
version "2.0.0"
resolved "https://registry.yarnpkg.com/@handlebars/parser/-/parser-2.0.0.tgz#5e8b7298f31ff8f7b260e6b7363c7e9ceed7d9c5"
integrity sha512-EP9uEDZv/L5Qh9IWuMUGJRfwhXJ4h1dqKTT4/3+tY0eu7sPis7xh23j61SYUnNF4vqCQvvUXpDo9Bh/+q1zASA==
DEV: Update sub-dependencies (#22325) Achieved by running `yarn upgrade --latest` both yarn.lock directories, then reverting changes to package.json files and running `yarn` again. I also de-duped yarn.lock files with `npx yarn-deduplicate && yarn`
2023-06-29 11:08:33 -04:00
"@highlightjs/cdn-assets@11.8.0":
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "11.8.0"
resolved "https://registry.yarnpkg.com/@highlightjs/cdn-assets/-/cdn-assets-11.8.0.tgz#e3aa9f20bf742b50bd7b1d60a24c8e7d124a602f"
integrity sha512-gkfCH4xGBGY9xPaW+t26WpgnfpDhNhB5RtVUDLx3MHkC7ZrmKeIxXsfjzOiuOnEgRk+vydlY6XeOeglh+eVhyg==
DEV: Fix build due to highlight.js branch issue (#12441) Highlight.js changed their default branch from master to main. This switches to the @highlightjs/cdn-assets package, thus sidestepping the problem. It's a slightly cleaner integration though (no need to build locally anymore).
2021-03-18 18:21:23 -04:00
DEV: Consolidate and update jsconfig, and add types packages (#23824) These updates significantly improve IDE tooling for imports across the Discourse core codebase, and also for framework packages. The `@types/ember-*` packages are a temporary solution until we get onto Ember 5, which ships its types in the main package. The previous approach of having jsconfig files in each package directory did work, but once you start adding all the possible interlinks between them, we hit the file count limit of VSCode's tooling (because it counts every file for every jsconfig its referenced in). Having one file at the root means that a single file can apply to all core packages and plugins. Long-term, to get the same functionality for all themes/plugins, we may need to look at building/publishing a Discourse types package which can be added to theme/plugin package.json files for development purposes.
2023-10-18 07:13:20 -04:00
"@humanwhocodes/config-array@^0.11.11":
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
version "0.11.12"
resolved "https://registry.yarnpkg.com/@humanwhocodes/config-array/-/config-array-0.11.12.tgz#549afec9bfce5232ac6325db12765f407e70e3a0"
integrity sha512-NlGesA1usRNn6ctHCZ21M4/dKPgW9Nn1FypRdIKKgZOKzkVV4T1FlK5mBiLhHBCDmEbdQG0idrcXlbZfksJ+RA==
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
dependencies:
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
"@humanwhocodes/object-schema" "^2.0.0"
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
debug "^4.1.1"
minimatch "^3.0.5"
"@humanwhocodes/module-importer@^1.0.1":
version "1.0.1"
resolved "https://registry.yarnpkg.com/@humanwhocodes/module-importer/-/module-importer-1.0.1.tgz#af5b2691a22b44be847b0ca81641c5fb6ad0172c"
integrity sha512-bxveV4V8v5Yb4ncFTT3rPSgZBOpCkjfK0y4oVVVJwIuDVBRMDXrPyXRL988i5ap9m9bnyEEjWfm5WkBmtffLfA==
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
"@humanwhocodes/object-schema@^2.0.0":
version "2.0.1"
resolved "https://registry.yarnpkg.com/@humanwhocodes/object-schema/-/object-schema-2.0.1.tgz#e5211452df060fa8522b55c7b3c0c4d1981cb044"
integrity sha512-dvuCeX5fC9dXgJn9t+X5atfmgQAzUOWqS1254Gh0m6i8wKd10ebXkfNKiRK+1GWi/yTvvLDHpoxLr0xxxeslWw==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
"@jridgewell/gen-mapping@^0.3.0", "@jridgewell/gen-mapping@^0.3.2":
version "0.3.3"
resolved "https://registry.yarnpkg.com/@jridgewell/gen-mapping/-/gen-mapping-0.3.3.tgz#7e02e6eb5df901aaedb08514203b096614024098"
integrity sha512-HLhSWOLRi875zjjMG/r+Nv0oCW8umGb0BgEhyX3dDX3egwZtB8PqLnjz3yedt8R5StBrzcg4aBpnh8UA9D1BoQ==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
dependencies:
"@jridgewell/set-array" "^1.0.1"
"@jridgewell/sourcemap-codec" "^1.4.10"
"@jridgewell/trace-mapping" "^0.3.9"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@jridgewell/resolve-uri@^3.1.0":
version "3.1.1"
resolved "https://registry.yarnpkg.com/@jridgewell/resolve-uri/-/resolve-uri-3.1.1.tgz#c08679063f279615a3326583ba3a90d1d82cc721"
integrity sha512-dSYZh7HhCDtCKm4QakX0xFpsRDqjjtZf/kjI/v3T3Nwt5r8/qz/M19F9ySyOqU94SXBmeG9ttTul+YnR4LOxFA==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
"@jridgewell/set-array@^1.0.1":
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
version "1.1.2"
resolved "https://registry.yarnpkg.com/@jridgewell/set-array/-/set-array-1.1.2.tgz#7c6cf998d6d20b914c0a55a91ae928ff25965e72"
integrity sha512-xnkseuNADM0gt2bs+BvhO0p78Mk762YnZdsuzFV018NoG1Sj1SCQvpSqa7XUaTam5vAGasABV9qXASMKnFMwMw==
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@jridgewell/sourcemap-codec@^1.4.10", "@jridgewell/sourcemap-codec@^1.4.14", "@jridgewell/sourcemap-codec@^1.4.15":
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "1.4.15"
resolved "https://registry.yarnpkg.com/@jridgewell/sourcemap-codec/-/sourcemap-codec-1.4.15.tgz#d7c6e6755c78567a951e04ab52ef0fd26de59f32"
integrity sha512-eF2rxCRulEKXHTRiDrDy6erMYWqNw4LPdQ8UQA4huuxaQsVeRPFl2oM8oDGxMFhJUWZf9McpLtJasDDZb/Bpeg==
"@jridgewell/trace-mapping@^0.3.17", "@jridgewell/trace-mapping@^0.3.9":
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
version "0.3.20"
resolved "https://registry.yarnpkg.com/@jridgewell/trace-mapping/-/trace-mapping-0.3.20.tgz#72e45707cf240fa6b081d0366f8265b0cd10197f"
integrity sha512-R8LcPeWZol2zR8mmH3JeKQ6QRCFb7XgUhV9ZlGhHLGyg4wpPiPZNQOOWhFZhxKw8u//yTbNGI42Bx/3paXEQ+Q==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
dependencies:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@jridgewell/resolve-uri" "^3.1.0"
"@jridgewell/sourcemap-codec" "^1.4.14"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
DEV: introduces documentation for chat (#19772) Note this commit also slightly changes internal API: channel instead of getChannel and updateCurrentUserChannelNotificationsSettings instead of updateCurrentUserChatChannelNotificationsSettings. Also destroyChannel takes a second param which is the name confirmation instead of an optional object containing this confirmation. This is to enforce the fact that it's required. In the future a top level jsdoc config file could be used instead of the hack tempfile, but while it's only an experiment for chat, it's probably good enough.
2023-01-18 06:36:16 -05:00
"@jsdoc/salty@^0.2.1":
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "0.2.5"
resolved "https://registry.yarnpkg.com/@jsdoc/salty/-/salty-0.2.5.tgz#1b2fa5bb8c66485b536d86eee877c263d322f692"
integrity sha512-TfRP53RqunNe2HBobVBJ0VLhK1HbfvBYeTC1ahnN64PWvyYyGebmMiPkuwvD9fpw2ZbkoPb8Q7mwy0aR8Z9rvw==
DEV: introduces documentation for chat (#19772) Note this commit also slightly changes internal API: channel instead of getChannel and updateCurrentUserChannelNotificationsSettings instead of updateCurrentUserChatChannelNotificationsSettings. Also destroyChannel takes a second param which is the name confirmation instead of an optional object containing this confirmation. This is to enforce the fact that it's required. In the future a top level jsdoc config file could be used instead of the hack tempfile, but while it's only an experiment for chat, it's probably good enough.
2023-01-18 06:36:16 -05:00
dependencies:
lodash "^4.17.21"
DEV: Update sub-dependencies (#22325) Achieved by running `yarn upgrade --latest` both yarn.lock directories, then reverting changes to package.json files and running `yarn` again. I also de-duped yarn.lock files with `npx yarn-deduplicate && yarn`
2023-06-29 11:08:33 -04:00
"@json-editor/json-editor@2.10.0":
DEV: Update `@json-editor/json-editor` (#22308) Manually tried it out by editing a json_schema setting of a theme component
2023-06-27 17:01:58 -04:00
version "2.10.0"
resolved "https://registry.yarnpkg.com/@json-editor/json-editor/-/json-editor-2.10.0.tgz#95002ed971e8b39d8d8834df885f002275a1e5ce"
integrity sha512-RGkzTccb4UDtmcQ1PYDWDJ3SXoGIRmesTUTJCyZ9kyVGjHs/HgqIXlpQPmg9fHFi9D45/8RTdGqlvkZMGw2zlA==
DEV: Add experimental json_scheme site setting type (#12226)
2021-03-01 09:15:17 -05:00
dependencies:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
core-js "^3.27.2"
DEV: Add experimental json_scheme site setting type (#12226)
2021-03-01 09:15:17 -05:00
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
"@lint-todo/utils@^13.1.1":
version "13.1.1"
resolved "https://registry.yarnpkg.com/@lint-todo/utils/-/utils-13.1.1.tgz#5c054d61ee037b9e552add118264771122cc1166"
integrity sha512-F5z53uvRIF4dYfFfJP3a2Cqg+4P1dgJchJsFnsZE0eZp0LK8X7g2J0CsJHRgns+skpXOlM7n5vFGwkWCWj8qJg==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
dependencies:
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
"@types/eslint" "^8.4.9"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
find-up "^5.0.0"
fs-extra "^9.1.0"
proper-lockfile "^4.1.2"
slash "^3.0.0"
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
tslib "^2.4.1"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
upath "^2.0.1"
DEV: Bump `@mixer/parallel-prettier` (#19053)
2022-11-16 15:38:57 -05:00
"@mixer/parallel-prettier@^2.0.3":
version "2.0.3"
resolved "https://registry.yarnpkg.com/@mixer/parallel-prettier/-/parallel-prettier-2.0.3.tgz#970902afcd38c8c71155e1d089e5444896abc253"
integrity sha512-42ImvDusmxjpQLHEmZrljV/+L9ynfmaTe5ooLMTTLyELulUJtJW8vBXCadQdodfZ5wjr2Sg3YGIzWE0rnBsfDg==
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
dependencies:
chalk "^4.1.0"
commander "^7.0.0"
DEV: Bump `@mixer/parallel-prettier` (#19053)
2022-11-16 15:38:57 -05:00
glob-stream "^7.0.0"
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
ignore "^5.1.8"
ora "^5.3.0"
prettier "^2.0.4"
rxjs "^6.6.3"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
"@nicolo-ribaudo/eslint-scope-5-internals@5.1.1-v1":
version "5.1.1-v1"
resolved "https://registry.yarnpkg.com/@nicolo-ribaudo/eslint-scope-5-internals/-/eslint-scope-5-internals-5.1.1-v1.tgz#dbf733a965ca47b1973177dc0bb6c889edcfb129"
integrity sha512-54/JRvkLIzzDWshCWfuhadfrfZVPiElY8Fcgmg1HroEly/EDSszzhBAsarCux+D/kOslTRquNzuyGSmUSTTHGg==
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
dependencies:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
eslint-scope "5.1.1"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
"@nodelib/fs.scandir@2.1.5":
version "2.1.5"
resolved "https://registry.yarnpkg.com/@nodelib/fs.scandir/-/fs.scandir-2.1.5.tgz#7619c2eb21b25483f6d167548b4cfd5a7488c3d5"
integrity sha512-vq24Bq3ym5HEQm2NKCr3yXDwjc7vTsEThRDnkp2DK9p1uqLR+DHurm/NOTo0KG7HYHU7eppKZj3MyqYuMBf62g==
dependencies:
"@nodelib/fs.stat" "2.0.5"
run-parallel "^1.1.9"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
"@nodelib/fs.stat@2.0.5", "@nodelib/fs.stat@^2.0.2":
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
version "2.0.5"
resolved "https://registry.yarnpkg.com/@nodelib/fs.stat/-/fs.stat-2.0.5.tgz#5bd262af94e9d25bd1e71b05deed44876a222e8b"
integrity sha512-RkhPPp2zrqDAQA/2jNhnztcPAlv64XdhIp7a7454A5ovI7Bukxgt7MX7udwAu3zg1DcpPU0rz3VV1SeaqvY4+A==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
"@nodelib/fs.walk@^1.2.3", "@nodelib/fs.walk@^1.2.8":
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
version "1.2.8"
resolved "https://registry.yarnpkg.com/@nodelib/fs.walk/-/fs.walk-1.2.8.tgz#e95737e8bb6746ddedf69c556953494f196fe69a"
integrity sha512-oGB+UxlgWcgQkgwo8GcEGwemoTFt3FIO9ababBmaGwXIoBKZ+GTy0pP185beGg7Llih/NSHSV2XAs1lnznocSg==
dependencies:
"@nodelib/fs.scandir" "2.1.5"
fastq "^1.6.0"
Revert "DEV: FloatKit (#23541)" (#23549) This reverts commits 0623ac684a65f95ce4f5438ff47944b1dc2119f4 408e71e437ef8abf98f93e3449898bf906766b0e a32fa3b9470dde0543fcee809f2abd1f219f7336 User tips were running into some issues.
2023-09-12 13:55:12 -04:00
"@puppeteer/browsers@1.6.0":
version "1.6.0"
resolved "https://registry.yarnpkg.com/@puppeteer/browsers/-/browsers-1.6.0.tgz#d52413a7039e40a5ef72fb13fb6505fd87ce842e"
integrity sha512-R2ib8j329427jtKB/qlz0MJbwfJE/6I8ocJLiajsRqJ2PPI8DbjiNzC3lQZeISXEcjOBVhbG2RafN8SlHdcT+A==
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
dependencies:
debug "4.3.4"
extract-zip "2.0.1"
progress "2.0.3"
proxy-agent "6.3.0"
tar-fs "3.0.4"
unbzip2-stream "1.4.3"
yargs "17.7.1"
Support for Ember Template linting
2020-02-05 11:33:15 -05:00
"@simple-dom/interface@^1.4.0":
version "1.4.0"
resolved "https://registry.yarnpkg.com/@simple-dom/interface/-/interface-1.4.0.tgz#e8feea579232017f89b0138e2726facda6fbb71f"
integrity sha512-l5qumKFWU0S+4ZzMaLXFU8tQZsicHEMEyAxI5kDFGhJsRqDwe0a7/iPA/GdxlGyDKseQQAgIz5kzU7eXTrlSpA==
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
"@tootallnate/quickjs-emscripten@^0.23.0":
version "0.23.0"
resolved "https://registry.yarnpkg.com/@tootallnate/quickjs-emscripten/-/quickjs-emscripten-0.23.0.tgz#db4ecfd499a9765ab24002c3b696d02e6d32a12c"
integrity sha512-C5Mc6rdnsaJDjO3UpGW/CQTHtCKaYlScZTly4JIu97Jxo/odCiH0ITnDXSJPTOrEKk/ycSZ0AOgTmkDtkOsvIA==
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
"@types/eslint@^8.4.9":
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
version "8.44.5"
resolved "https://registry.yarnpkg.com/@types/eslint/-/eslint-8.44.5.tgz#24d7f3b07aff47a13b570efd5c52d96f38cd352e"
integrity sha512-Ol2eio8LtD/tGM4Ga7Jb83NuFwEv3NqvssSlifXL9xuFpSyQZw0ecmm2Kux6iU0KxQmp95hlPmGCzGJ0TCFeRA==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
dependencies:
"@types/estree" "*"
"@types/json-schema" "*"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
"@types/estree@*":
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
version "1.0.3"
resolved "https://registry.yarnpkg.com/@types/estree/-/estree-1.0.3.tgz#2be19e759a3dd18c79f9f436bd7363556c1a73dd"
integrity sha512-CS2rOaoQ/eAgAfcTfq6amKG7bsN+EMcgGY4FAFQdvSj2y1ixvOZTUA9mOtCai7E1SYu283XNw7urKK30nP3wkQ==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
"@types/json-schema@*":
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
version "7.0.14"
resolved "https://registry.yarnpkg.com/@types/json-schema/-/json-schema-7.0.14.tgz#74a97a5573980802f32c8e47b663530ab3b6b7d1"
integrity sha512-U3PUjAudAdJBeC2pgN8uTIKgxrb4nlDF3SF0++EldXQvQBGkpFZMSnwQiIoDU77tv45VgNkl/L4ouD+rEomujw==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
DEV: introduces documentation for chat (#19772) Note this commit also slightly changes internal API: channel instead of getChannel and updateCurrentUserChannelNotificationsSettings instead of updateCurrentUserChatChannelNotificationsSettings. Also destroyChannel takes a second param which is the name confirmation instead of an optional object containing this confirmation. This is to enforce the fact that it's required. In the future a top level jsdoc config file could be used instead of the hack tempfile, but while it's only an experiment for chat, it's probably good enough.
2023-01-18 06:36:16 -05:00
"@types/linkify-it@*":
Revert "DEV: FloatKit (#23541)" (#23549) This reverts commits 0623ac684a65f95ce4f5438ff47944b1dc2119f4 408e71e437ef8abf98f93e3449898bf906766b0e a32fa3b9470dde0543fcee809f2abd1f219f7336 User tips were running into some issues.
2023-09-12 13:55:12 -04:00
version "3.0.2"
resolved "https://registry.yarnpkg.com/@types/linkify-it/-/linkify-it-3.0.2.tgz#fd2cd2edbaa7eaac7e7f3c1748b52a19143846c9"
integrity sha512-HZQYqbiFVWufzCwexrvh694SOim8z2d+xJl5UNamcvQFejLY/2YUtzXHYi3cHdI7PMlS8ejH2slRAOJQ32aNbA==
DEV: introduces documentation for chat (#19772) Note this commit also slightly changes internal API: channel instead of getChannel and updateCurrentUserChannelNotificationsSettings instead of updateCurrentUserChatChannelNotificationsSettings. Also destroyChannel takes a second param which is the name confirmation instead of an optional object containing this confirmation. This is to enforce the fact that it's required. In the future a top level jsdoc config file could be used instead of the hack tempfile, but while it's only an experiment for chat, it's probably good enough.
2023-01-18 06:36:16 -05:00
"@types/markdown-it@^12.2.3":
version "12.2.3"
resolved "https://registry.yarnpkg.com/@types/markdown-it/-/markdown-it-12.2.3.tgz#0d6f6e5e413f8daaa26522904597be3d6cd93b51"
integrity sha512-GKMHFfv3458yYy+v/N8gjufHO6MSZKCOXpZc5GXIWWy8uldwfmPn98vp81gZ5f9SVw8YYBctgfJ22a2d7AOMeQ==
dependencies:
"@types/linkify-it" "*"
"@types/mdurl" "*"
"@types/mdurl@*":
version "1.0.2"
resolved "https://registry.yarnpkg.com/@types/mdurl/-/mdurl-1.0.2.tgz#e2ce9d83a613bacf284c7be7d491945e39e1f8e9"
integrity sha512-eC4U9MlIcu2q0KQmXszyn5Akca/0jrQmwDRgpAMJai7qBWq4amIQhZyNau4VYGtCeALvW1/NtjzJJ567aZxfKA==
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
"@types/minimatch@^3.0.3", "@types/minimatch@^3.0.4":
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
version "3.0.5"
resolved "https://registry.yarnpkg.com/@types/minimatch/-/minimatch-3.0.5.tgz#1001cc5e6a3704b83c236027e77f2f58ea010f40"
integrity sha512-Klz949h02Gz2uZCMGwDUSDS1YBlTdDDgbWHi+81l29tQALUtvz4rAYi5uoVhE5Lagoq6DeqAUlbrHvW/mXDgdQ==
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
"@types/node@*":
Revert "DEV: FloatKit (#23541)" (#23549) This reverts commits 0623ac684a65f95ce4f5438ff47944b1dc2119f4 408e71e437ef8abf98f93e3449898bf906766b0e a32fa3b9470dde0543fcee809f2abd1f219f7336 User tips were running into some issues.
2023-09-12 13:55:12 -04:00
version "20.3.2"
resolved "https://registry.yarnpkg.com/@types/node/-/node-20.3.2.tgz#fa6a90f2600e052a03c18b8cb3fd83dd4e599898"
integrity sha512-vOBLVQeCQfIcF/2Y7eKFTqrMnizK5lRNQ7ykML/5RuwVXVWxYkgwS7xbt4B6fKCUPgbSL5FSsjHQpaGQP/dQmw==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
"@types/symlink-or-copy@^1.2.0":
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
version "1.2.1"
resolved "https://registry.yarnpkg.com/@types/symlink-or-copy/-/symlink-or-copy-1.2.1.tgz#9696b4620e59fd613f2895535c498be5d536bb02"
integrity sha512-8LQKxlJ8zXQ5U0wFXTSBXLHg8+oBbLMJXEC6vOqhL+iz8EfVvSxfdwtvq8ufkT9pumab0ntnvYXQBF/+cxzl9w==
Run JS test in chrome headless on Travis.
2017-12-14 21:15:04 -05:00
DEV: Switch from puppeteer to puppeteer-core for smoke test (#15262) `puppeteer` includes a full chromium binary, which adds more than 300mb to our node_modules directory in development/test mode (and therefore the `discourse_dev` and `discourse_test` docker images). We already reach out to the system copy of Chrome for our qunit tests, and already have chrome installed in our `discourse_dev`/`discourse_test` docker images, so it's much more efficient to switch to `puppeteer-core` which doesn't include the chromium binary.
2021-12-13 04:31:49 -05:00
"@types/yauzl@^2.9.1":
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "2.10.0"
resolved "https://registry.yarnpkg.com/@types/yauzl/-/yauzl-2.10.0.tgz#b3248295276cf8c6f153ebe6a9aba0c988cb2599"
integrity sha512-Cn6WYCm0tXv8p6k+A8PvbDG763EDpBoTzHdA+Q/MF6H3sapGjCm9NzoaJncJS9tUKSuCoDs9XHxYYsQDgxR6kw==
DEV: Switch from puppeteer to puppeteer-core for smoke test (#15262) `puppeteer` includes a full chromium binary, which adds more than 300mb to our node_modules directory in development/test mode (and therefore the `discourse_dev` and `discourse_test` docker images). We already reach out to the system copy of Chrome for our qunit tests, and already have chrome installed in our `discourse_dev`/`discourse_test` docker images, so it's much more efficient to switch to `puppeteer-core` which doesn't include the chromium binary.
2021-12-13 04:31:49 -05:00
dependencies:
"@types/node" "*"
FEATURE: Automatic admin editor dark mode (#15419)
2021-12-29 11:02:37 -05:00
ace-builds@1.4.13:
version "1.4.13"
resolved "https://registry.yarnpkg.com/ace-builds/-/ace-builds-1.4.13.tgz#186f42d3849ebcc6a48b93088a058489897514c1"
integrity sha512-SOLzdaQkY6ecPKYRDDg+MY1WoGgXA34cIvYJNNoBMGGUswHmlauU2Hy0UL96vW0Fs/LgFbMUjD+6vqzWTldIYQ==
Use Yarn to manage dependencies, cleanup unused bootstrap libs (#6436)
2018-10-03 10:15:43 -04:00
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
acorn-jsx@^5.3.2:
version "5.3.2"
resolved "https://registry.yarnpkg.com/acorn-jsx/-/acorn-jsx-5.3.2.tgz#7ed5bb55908b3b2f1bc55c6af1653bada7f07937"
integrity sha512-rq9s+JNhf0IChjtDXxllJ7g41oZk5SlXtp0LHwyA5cejwn7vKmKp4pPri6YEePv2PU65sAsegbXtIinmDFDXgQ==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
acorn@^8.9.0:
version "8.10.0"
resolved "https://registry.yarnpkg.com/acorn/-/acorn-8.10.0.tgz#8be5b3907a67221a81ab23c7889c4c5526b62ec5"
integrity sha512-F0SAmZ8iUtS//m8DmCTA0jlh6TDKkHQyK6xc6V4KDTyZKA9dnvX9/3sRTVQrWm79glUAZbnmmNcdYwUIHWVybw==
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
Revert "DEV: FloatKit (#23541)" (#23549) This reverts commits 0623ac684a65f95ce4f5438ff47944b1dc2119f4 408e71e437ef8abf98f93e3449898bf906766b0e a32fa3b9470dde0543fcee809f2abd1f219f7336 User tips were running into some issues.
2023-09-12 13:55:12 -04:00
agent-base@^7.0.1, agent-base@^7.0.2, agent-base@^7.1.0:
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
version "7.1.0"
resolved "https://registry.yarnpkg.com/agent-base/-/agent-base-7.1.0.tgz#536802b76bc0b34aa50195eb2442276d613e3434"
integrity sha512-o/zjMZRhJxny7OyEF+Op8X+efiELC7k7yOjMzgfzVqOzXqkBkWI79YoTdOtsuWd5BWhAGAuOY/Xa6xpiaWXiNg==
Add smoke test script that runs in chrome headless.
2017-12-18 03:32:58 -05:00
dependencies:
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
debug "^4.3.4"
Add smoke test script that runs in chrome headless.
2017-12-18 03:32:58 -05:00
DEV: Consolidate and update jsconfig, and add types packages (#23824) These updates significantly improve IDE tooling for imports across the Discourse core codebase, and also for framework packages. The `@types/ember-*` packages are a temporary solution until we get onto Ember 5, which ships its types in the main package. The previous approach of having jsconfig files in each package directory did work, but once you start adding all the possible interlinks between them, we hit the file count limit of VSCode's tooling (because it counts every file for every jsconfig its referenced in). Having one file at the root means that a single file can apply to all core packages and plugins. Long-term, to get the same functionality for all themes/plugins, we may need to look at building/publishing a Discourse types package which can be added to theme/plugin package.json files for development purposes.
2023-10-18 07:13:20 -04:00
ajv@^6.12.4:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
version "6.12.6"
resolved "https://registry.yarnpkg.com/ajv/-/ajv-6.12.6.tgz#baf5a62e802b07d977034586f8c3baf5adf26df4"
integrity sha512-j3fVLgvTo527anyYyJOGTYJbG+vnnQYvE0m5mmkc1TK+nxAppkCLMIL0aZ4dblVCNoGShhm+kzE4ZUykBoMg4g==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
dependencies:
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
fast-deep-equal "^3.1.1"
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
fast-json-stable-stringify "^2.0.0"
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
json-schema-traverse "^0.4.1"
uri-js "^4.2.2"
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
ansi-regex@^5.0.1:
version "5.0.1"
resolved "https://registry.yarnpkg.com/ansi-regex/-/ansi-regex-5.0.1.tgz#082cb2c89c9fe8659a311a53bd6a4dc5301db304"
integrity sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
ansi-styles@^3.2.1:
Upgrade to FontAwesome 5 (take two) (#6673) * Add missing icons to set * Revert FA5 revert This reverts commit 42572ff * use new SVG syntax in locales * Noscript page changes (remove login button, center "powered by" footer text) * Cast wider net for SVG icons in settings - include any _icon setting for SVG registry (offers better support for plugin settings) - let themes store multiple pipe-delimited icons in a setting - also replaces broken onebox image icon with SVG reference in cooked post processor * interpolate icons in locales * Fix composer whisper icon alignment * Add support for stacked icons * SECURITY: enforce hostname to match discourse hostname This ensures that the hostname rails uses for various helpers always matches the Discourse hostname * load SVG sprite with pre-initializers * FIX: enable caching on SVG sprites * PERF: use JSONP for SVG sprites so they are served from CDN This avoids needing to deal with CORS for loading of the SVG Note, added the svg- prefix to the filename so we can quickly tell in dev tools what the file is * Add missing SVG sprite JSONP script to CSP * Upgrade to FA 5.5.0 * Add support for all FA4.7 icons - adds complete frontend and backend for renamed FA4.7 icons - improves performance of SvgSprite.bundle and SvgSprite.all_icons * Fix group avatar flair preview - adds an endpoint at /svg-sprites/search/:keyword - adds frontend ajax call that pulls icon in avatar flair preview even when it is not in subset * Remove FA 4.7 font files
2018-11-26 16:49:57 -05:00
version "3.2.1"
resolved "https://registry.yarnpkg.com/ansi-styles/-/ansi-styles-3.2.1.tgz#41fbb20243e50b12be0f04b8dedbf07520ce841d"
integrity sha512-VT0ZI6kZRdTh8YyJw3SMbYm/u+NqfsAxEpWO0Pf9sq8/e94WxxOpPKx9FR1FlyCtOVDNOQ+8ntlqFxiRc+r5qA==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
dependencies:
color-convert "^1.9.0"
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
ansi-styles@^4.0.0, ansi-styles@^4.1.0:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "4.3.0"
resolved "https://registry.yarnpkg.com/ansi-styles/-/ansi-styles-4.3.0.tgz#edd803628ae71c04c85ae7a0906edad34b648937"
integrity sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
dependencies:
color-convert "^2.0.1"
DEV: Upgrade Markdown.it to v13.0.1 (#17099) Updates markdown-it to v13.0.1 Noteworthy changes: * `markdownit()` is now available on `globalThis` instead of `window`. * The `text_collapse` rule was renamed to `fragments_join` which affected the `bbcode-inline` implementation. * The `linkify` rule was added to the `inline` chain which affected the handling of the `[url]` BBCode. If available, our implementation reuses `link_open` and `link_close` tokens created by linkify in order to prevent duplicate links. * The rendered HTML for code changed slightly. There's now a linebreak before the `</code>` tag. The tests were adjusted accordingly.
2022-06-20 09:25:13 -04:00
argparse@^2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/argparse/-/argparse-2.0.1.tgz#246f50f3ca78a3240f6c997e8a9bd1eac49e4b38"
integrity sha512-8+9WqebbFzpX9OR+Wa6O29asIogeRMzcGtAINdpMHHyAg10f05aSFVBbcEqGf/PXw1EjAZ+q2/bEBg3DvurK3Q==
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
aria-query@^5.3.0:
DEV: Update sub-dependencies (#22325) Achieved by running `yarn upgrade --latest` both yarn.lock directories, then reverting changes to package.json files and running `yarn` again. I also de-duped yarn.lock files with `npx yarn-deduplicate && yarn`
2023-06-29 11:08:33 -04:00
version "5.3.0"
resolved "https://registry.yarnpkg.com/aria-query/-/aria-query-5.3.0.tgz#650c569e41ad90b51b3d7df5e5eed1c7549c103e"
integrity sha512-b0P0sZPKtyu8HkeRAfCq0IfURZK+SuwMjY1UXGBU27wpAiTwQAIlq56IbIO+ytk/JjS1fMR14ee5WBBfKi5J6A==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
dependencies:
dequal "^2.0.3"
array-buffer-byte-length@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/array-buffer-byte-length/-/array-buffer-byte-length-1.0.0.tgz#fabe8bc193fea865f317fe7807085ee0dee5aead"
integrity sha512-LPuwb2P+NrQw3XhxGc36+XSvuBPopovXYTR9Ew++Du9Yb/bx5AzBfrIsBoj0EZUifjQU+sHL21sseZ3jerWO/A==
dependencies:
call-bind "^1.0.2"
is-array-buffer "^3.0.1"
array-equal@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/array-equal/-/array-equal-1.0.0.tgz#8c2a5ef2472fd9ea742b04c77a75093ba2757c93"
integrity sha512-H3LU5RLiSsGXPhN+Nipar0iR0IofH+8r89G2y1tBKxQ/agagKyAjhkAFDRBfodP2caPrNKHpAWNIM/c9yeL7uA==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
array-union@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/array-union/-/array-union-2.1.0.tgz#b798420adbeb1de828d84acd8a2e23d3efe85e8d"
integrity sha512-HGyxoOTYUyCM6stUe6EJgnd4EoewAI7zMdfqO+kGjnlZmBDz/cR5pf8r/cR4Wq60sL/p0IkcjUEEPwS3GFrIyw==
Support for Ember Template linting
2020-02-05 11:33:15 -05:00
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
arraybuffer.prototype.slice@^1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/arraybuffer.prototype.slice/-/arraybuffer.prototype.slice-1.0.2.tgz#98bd561953e3e74bb34938e77647179dfe6e9f12"
integrity sha512-yMBKppFur/fbHu9/6USUe03bZ4knMYiwFBcyiaXB8Go0qNehwX6inYPzK9U0NeQvGxKthcmHcaR8P5MStSRBAw==
dependencies:
array-buffer-byte-length "^1.0.0"
call-bind "^1.0.2"
define-properties "^1.2.0"
es-abstract "^1.22.1"
get-intrinsic "^1.2.1"
is-array-buffer "^3.0.2"
is-shared-array-buffer "^1.0.2"
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
assertion-error@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/assertion-error/-/assertion-error-1.1.0.tgz#e60b6b0e8f301bd97e5375215bda406c85118c0b"
integrity sha512-jgsaNduz+ndvGyFt3uSuWqvy4lCnIJiovtouQN5JZHOKCS2QuhEdbcQHFhVksz2N2U9hXJo8odG7ETyWlEeuDw==
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
ast-types@^0.13.4:
version "0.13.4"
resolved "https://registry.yarnpkg.com/ast-types/-/ast-types-0.13.4.tgz#ee0d77b343263965ecc3fb62da16e7222b2b6782"
integrity sha512-x1FCFnFifvYDDzTaLII71vG5uvDwgtmDTEVWAxrgeiR8VjMONcCXJx7E+USjDtHlwFmt9MysbqgF9b9Vjr6w+w==
dependencies:
tslib "^2.0.1"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
async-disk-cache@^1.2.1:
version "1.3.5"
resolved "https://registry.yarnpkg.com/async-disk-cache/-/async-disk-cache-1.3.5.tgz#cc6206ed79bb6982b878fc52e0505e4f52b62a02"
integrity sha512-VZpqfR0R7CEOJZ/0FOTgWq70lCrZyS1rkI8PXugDUkTKyyAUgZ2zQ09gLhMkEn+wN8LYeUTPxZdXtlX/kmbXKQ==
dependencies:
debug "^2.1.3"
heimdalljs "^0.2.3"
istextorbinary "2.1.0"
mkdirp "^0.5.0"
rimraf "^2.5.3"
rsvp "^3.0.18"
username-sync "^1.0.2"
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
async-disk-cache@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/async-disk-cache/-/async-disk-cache-2.1.0.tgz#e0f37b187ed8c41a5991518a9556d206ae2843a2"
integrity sha512-iH+boep2xivfD9wMaZWkywYIURSmsL96d6MoqrC94BnGSvXE4Quf8hnJiHGFYhw/nLeIa1XyRaf4vvcvkwAefg==
dependencies:
debug "^4.1.1"
heimdalljs "^0.2.3"
istextorbinary "^2.5.1"
mkdirp "^0.5.0"
rimraf "^3.0.0"
rsvp "^4.8.5"
username-sync "^1.0.2"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
async-promise-queue@^1.0.3, async-promise-queue@^1.0.5:
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
version "1.0.5"
resolved "https://registry.yarnpkg.com/async-promise-queue/-/async-promise-queue-1.0.5.tgz#cb23bce9fce903a133946a700cc85f27f09ea49d"
integrity sha512-xi0aQ1rrjPWYmqbwr18rrSKbSaXIeIwSd1J4KAgVfkq8utNbdZoht7GfvfY6swFUAMJ9obkc4WPJmtGwl+B8dw==
dependencies:
async "^2.4.1"
debug "^2.6.8"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
async@^2.4.1:
Build(deps): Bump async from 2.6.3 to 2.6.4 (#21183) Bumps [async](https://github.com/caolan/async) from 2.6.3 to 2.6.4. - [Release notes](https://github.com/caolan/async/releases) - [Changelog](https://github.com/caolan/async/blob/v2.6.4/CHANGELOG.md) - [Commits](https://github.com/caolan/async/compare/v2.6.3...v2.6.4) --- updated-dependencies: - dependency-name: async dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-27 15:29:21 -04:00
version "2.6.4"
resolved "https://registry.yarnpkg.com/async/-/async-2.6.4.tgz#706b7ff6084664cd7eae713f6f965433b5504221"
integrity sha512-mzo5dfJYwAn29PeiJ0zvwTo04zj8HDJj0Mn8TD7sno7q12prdbnasKJHhkm2c1LgrhlJ0teaea8860oxi51mGA==
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
dependencies:
lodash "^4.17.14"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
at-least-node@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/at-least-node/-/at-least-node-1.0.0.tgz#602cd4b46e844ad4effc92a8011a3c46e0238dc2"
integrity sha512-+q/t7Ekv1EDY2l6Gda6LLiX14rU9TV20Wa3ofeQmwPFZbOMo9DXrLbOjFaaclkXKWidIaopwAObQDqwWtGUjqg==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
available-typed-arrays@^1.0.5:
version "1.0.5"
resolved "https://registry.yarnpkg.com/available-typed-arrays/-/available-typed-arrays-1.0.5.tgz#92f95616501069d07d10edb2fc37d3e1c65123b7"
integrity sha512-DMD0KiN46eipeziST1LPP/STfDU0sufISXmjSgvVsoU2tqxctQeASejWcfNtxYKqETM1UxQ8sp2OrSBWpHY6sw==
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
b4a@^1.6.4:
version "1.6.4"
resolved "https://registry.yarnpkg.com/b4a/-/b4a-1.6.4.tgz#ef1c1422cae5ce6535ec191baeed7567443f36c9"
integrity sha512-fpWrvyVHEKyeEvbKZTVOeZF3VSKKWtJxFIxX/jaVPf+cLbGUSitjb49pHLqPV2BUNNZ0LcoeEGfE/YCpyDYHIw==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
babel-import-util@^0.2.0:
version "0.2.0"
resolved "https://registry.yarnpkg.com/babel-import-util/-/babel-import-util-0.2.0.tgz#b468bb679919601a3570f9e317536c54f2862e23"
integrity sha512-CtWYYHU/MgK88rxMrLfkD356dApswtR/kWZ/c6JifG1m10e7tBBrs/366dFzWMAoqYmG5/JSh+94tUSpIwh+ag==
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
babel-import-util@^2.0.0:
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
version "2.0.1"
resolved "https://registry.yarnpkg.com/babel-import-util/-/babel-import-util-2.0.1.tgz#263a2963ee9208428c04f05326c6ea32b2206ac6"
integrity sha512-N1ZfNprtf/37x0R05J0QCW/9pCAcuI+bjZIK9tlu0JEkwEST7ssdD++gxHRbD58AiG5QE5OuNYhRoEFsc1wESw==
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
babel-plugin-ember-modules-api-polyfill@^3.5.0:
version "3.5.0"
resolved "https://registry.yarnpkg.com/babel-plugin-ember-modules-api-polyfill/-/babel-plugin-ember-modules-api-polyfill-3.5.0.tgz#27b6087fac75661f779f32e60f94b14d0e9f6965"
integrity sha512-pJajN/DkQUnStw0Az8c6khVcMQHgzqWr61lLNtVeu0g61LRW0k9jyK7vaedrHDWGe/Qe8sxG5wpiyW9NsMqFzA==
dependencies:
ember-rfc176-data "^0.3.17"
babel-plugin-ember-template-compilation@^2.0.0:
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
version "2.2.0"
resolved "https://registry.yarnpkg.com/babel-plugin-ember-template-compilation/-/babel-plugin-ember-template-compilation-2.2.0.tgz#b119fadcd5c831299fbd706420d2ea742848a659"
integrity sha512-1I7f5gf06h5wKdKUvaYEIaoSFur5RLUvTMQG4ak0c5Y11DWUxcoX9hrun1xe9fqfY2dtGFK+ZUM6sn6z8sqK/w==
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
dependencies:
"@glimmer/syntax" "^0.84.3"
babel-import-util "^2.0.0"
babel-plugin-htmlbars-inline-precompile@^5.3.0:
version "5.3.1"
resolved "https://registry.yarnpkg.com/babel-plugin-htmlbars-inline-precompile/-/babel-plugin-htmlbars-inline-precompile-5.3.1.tgz#5ba272e2e4b6221522401f5f1d98a73b1de38787"
integrity sha512-QWjjFgSKtSRIcsBhJmEwS2laIdrA6na8HAlc/pEAhjHgQsah/gMiBFRZvbQTy//hWxR4BMwV7/Mya7q5H8uHeA==
dependencies:
babel-plugin-ember-modules-api-polyfill "^3.5.0"
line-column "^1.0.2"
magic-string "^0.25.7"
parse-static-imports "^1.1.0"
string.prototype.matchall "^4.0.5"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
balanced-match@^1.0.0:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "1.0.2"
resolved "https://registry.yarnpkg.com/balanced-match/-/balanced-match-1.0.2.tgz#e83e3a7e3f300b34cb9d87f615fa0cbf357690ee"
integrity sha512-3oSeUO0TMV67hN1AmbXsK4yaqU7tjiHlbxRDZOpH0KW9+CeX4bRAaX0Anxt0tx2MrpRpWwQaPwIlISEJhYU5Pw==
DEV: introduces documentation for chat (#19772) Note this commit also slightly changes internal API: channel instead of getChannel and updateCurrentUserChannelNotificationsSettings instead of updateCurrentUserChatChannelNotificationsSettings. Also destroyChannel takes a second param which is the name confirmation instead of an optional object containing this confirmation. This is to enforce the fact that it's required. In the future a top level jsdoc config file could be used instead of the hack tempfile, but while it's only an experiment for chat, it's probably good enough.
2023-01-18 06:36:16 -05:00
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
base64-js@^1.3.1:
version "1.5.1"
resolved "https://registry.yarnpkg.com/base64-js/-/base64-js-1.5.1.tgz#1b1b440160a5bf7ad40b650f095963481903930a"
integrity sha512-AKpaYlHn8t4SVbOHCy+b5+KKgvR4vrsD8vbvrbiQJps7fKDTkjkDry6ji0rUJjC0kzbNePLwzxq8iypo41qeWA==
Run JS test in chrome headless on Travis.
2017-12-14 21:15:04 -05:00
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
basic-ftp@^5.0.2:
version "5.0.3"
resolved "https://registry.yarnpkg.com/basic-ftp/-/basic-ftp-5.0.3.tgz#b14c0fe8111ce001ec913686434fe0c2fb461228"
integrity sha512-QHX8HLlncOLpy54mh+k/sWIFd0ThmRqwe9ZjELybGZK+tZ8rUb9VO0saKJUROTbE+KhzDUT7xziGpGrW8Kmd+g==
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
"binaryextensions@1 || 2", binaryextensions@^2.1.2:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "2.3.0"
resolved "https://registry.yarnpkg.com/binaryextensions/-/binaryextensions-2.3.0.tgz#1d269cbf7e6243ea886aa41453c3651ccbe13c22"
integrity sha512-nAihlQsYGyc5Bwq6+EsubvANYGExeJKHDO3RjnvwU042fawQTQfM3Kxn7IHUXQOz4bzfwsGYYHGSvXyW4zOGLg==
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
bl@^4.1.0:
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
version "4.1.0"
resolved "https://registry.yarnpkg.com/bl/-/bl-4.1.0.tgz#451535264182bec2fbbc83a62ab98cf11d9f7b3a"
integrity sha512-1W07cM9gS6DcLperZfFSj+bWLtaPGSOHWhPiGzXmvVJbRLdG82sH/Kn8EtW1VqWVA54AKf2h5k5BbnIbwF3h6w==
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
dependencies:
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
buffer "^5.5.0"
inherits "^2.0.4"
readable-stream "^3.4.0"
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
blank-object@^1.0.1:
version "1.0.2"
resolved "https://registry.yarnpkg.com/blank-object/-/blank-object-1.0.2.tgz#f990793fbe9a8c8dd013fb3219420bec81d5f4b9"
integrity sha512-kXQ19Xhoghiyw66CUiGypnuRpWlbHAzY/+NyvqTEdTfhfQGH1/dbEMYiXju7fYKIFePpzp/y9dsu5Cu/PkmawQ==
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
bluebird@^3.7.2:
version "3.7.2"
resolved "https://registry.yarnpkg.com/bluebird/-/bluebird-3.7.2.tgz#9f229c15be272454ffa973ace0dbee79a1b0c36f"
integrity sha512-XpNj6GDQzdfW+r2Wnn7xiSAd7TM3jzkxGXBGTtWKuSXv1xUV+azxAm8jdWZN06QTQk+2N2XB9jRDkvbmQmcRtg==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
brace-expansion@^1.1.7:
version "1.1.11"
resolved "https://registry.yarnpkg.com/brace-expansion/-/brace-expansion-1.1.11.tgz#3c7fcbf529d87226f3d2f52b966ff5271eb441dd"
integrity sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==
DEV: Merge package.json files (#21172) This means: a single yarn.lock and removing one of the package.json files
2023-04-20 06:46:12 -04:00
dependencies:
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
balanced-match "^1.0.0"
concat-map "0.0.1"
DEV: Merge package.json files (#21172) This means: a single yarn.lock and removing one of the package.json files
2023-04-20 06:46:12 -04:00
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
braces@^3.0.2:
version "3.0.2"
resolved "https://registry.yarnpkg.com/braces/-/braces-3.0.2.tgz#3454e1a462ee8d599e236df336cd9ea4f8afe107"
integrity sha512-b8um+L1RzM3WDSzvhm6gIz1yfTbBt6YTlcEKAvsmqCZZFw46z626lVj9j1yEPW33H5H+lBQpZMP1k8l+78Ha0A==
DEV: Merge package.json files (#21172) This means: a single yarn.lock and removing one of the package.json files
2023-04-20 06:46:12 -04:00
dependencies:
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
fill-range "^7.0.1"
DEV: Merge package.json files (#21172) This means: a single yarn.lock and removing one of the package.json files
2023-04-20 06:46:12 -04:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
broccoli-debug@^0.6.5:
version "0.6.5"
resolved "https://registry.yarnpkg.com/broccoli-debug/-/broccoli-debug-0.6.5.tgz#164a5cdafd8936e525e702bf8f91f39d758e2e78"
integrity sha512-RIVjHvNar9EMCLDW/FggxFRXqpjhncM/3qq87bn/y+/zR9tqEkHvTqbyOc4QnB97NO2m6342w4wGkemkaeOuWg==
dependencies:
broccoli-plugin "^1.2.1"
fs-tree-diff "^0.5.2"
heimdalljs "^0.2.1"
heimdalljs-logger "^0.1.7"
symlink-or-copy "^1.1.8"
tree-sync "^1.2.2"
broccoli-funnel@^2.0.0:
version "2.0.2"
resolved "https://registry.yarnpkg.com/broccoli-funnel/-/broccoli-funnel-2.0.2.tgz#0edf629569bc10bd02cc525f74b9a38e71366a75"
integrity sha512-/vDTqtv7ipjEZQOVqO4vGDVAOZyuYzQ/EgGoyewfOgh1M7IQAToBKZI0oAQPgMBeFPPlIbfMuAngk+ohPBuaHQ==
dependencies:
array-equal "^1.0.0"
blank-object "^1.0.1"
broccoli-plugin "^1.3.0"
debug "^2.2.0"
fast-ordered-set "^1.0.0"
fs-tree-diff "^0.5.3"
heimdalljs "^0.2.0"
minimatch "^3.0.0"
mkdirp "^0.5.0"
path-posix "^1.0.0"
rimraf "^2.4.3"
symlink-or-copy "^1.0.0"
walk-sync "^0.3.1"
broccoli-kitchen-sink-helpers@^0.3.1:
version "0.3.1"
resolved "https://registry.yarnpkg.com/broccoli-kitchen-sink-helpers/-/broccoli-kitchen-sink-helpers-0.3.1.tgz#77c7c18194b9664163ec4fcee2793444926e0c06"
integrity sha512-gqYnKSJxBSjj/uJqeuRAzYVbmjWhG0mOZ8jrp6+fnUIOgLN6MvI7XxBECDHkYMIFPJ8Smf4xaI066Q2FqQDnXg==
dependencies:
glob "^5.0.10"
mkdirp "^0.5.1"
broccoli-merge-trees@^3.0.1:
version "3.0.2"
resolved "https://registry.yarnpkg.com/broccoli-merge-trees/-/broccoli-merge-trees-3.0.2.tgz#f33b451994225522b5c9bcf27d59decfd8ba537d"
integrity sha512-ZyPAwrOdlCddduFbsMyyFzJUrvW6b04pMvDiAQZrCwghlvgowJDY+EfoXn+eR1RRA5nmGHJ+B68T63VnpRiT1A==
dependencies:
broccoli-plugin "^1.3.0"
merge-trees "^2.0.0"
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
broccoli-node-api@^1.7.0:
version "1.7.0"
resolved "https://registry.yarnpkg.com/broccoli-node-api/-/broccoli-node-api-1.7.0.tgz#391aa6edecd2a42c63c111b4162956b2fa288cb6"
integrity sha512-QIqLSVJWJUVOhclmkmypJJH9u9s/aWH4+FH6Q6Ju5l+Io4dtwqdPUNmDfw40o6sxhbZHhqGujDJuHTML1wG8Yw==
broccoli-node-info@^2.1.0:
version "2.2.0"
resolved "https://registry.yarnpkg.com/broccoli-node-info/-/broccoli-node-info-2.2.0.tgz#feb01c13020792f429e01d7f7845dc5b3a7932b3"
integrity sha512-VabSGRpKIzpmC+r+tJueCE5h8k6vON7EIMMWu6d/FyPdtijwLQ7QvzShEw+m3mHoDzUaj/kiZsDYrS8X2adsBg==
broccoli-output-wrapper@^3.2.5:
version "3.2.5"
resolved "https://registry.yarnpkg.com/broccoli-output-wrapper/-/broccoli-output-wrapper-3.2.5.tgz#514b17801c92922a2c2f87fd145df2a25a11bc5f"
integrity sha512-bQAtwjSrF4Nu0CK0JOy5OZqw9t5U0zzv2555EA/cF8/a8SLDTIetk9UgrtMVw7qKLKdSpOZ2liZNeZZDaKgayw==
dependencies:
fs-extra "^8.1.0"
heimdalljs-logger "^0.1.10"
symlink-or-copy "^1.2.0"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
broccoli-persistent-filter@^2.3.0:
version "2.3.1"
resolved "https://registry.yarnpkg.com/broccoli-persistent-filter/-/broccoli-persistent-filter-2.3.1.tgz#4a052e0e0868b344c3a2977e35a3d497aa9eca72"
integrity sha512-hVsmIgCDrl2NFM+3Gs4Cr2TA6UPaIZip99hN8mtkaUPgM8UeVnCbxelCvBjUBHo0oaaqP5jzqqnRVvb568Yu5g==
dependencies:
async-disk-cache "^1.2.1"
async-promise-queue "^1.0.3"
broccoli-plugin "^1.0.0"
fs-tree-diff "^2.0.0"
hash-for-dep "^1.5.0"
heimdalljs "^0.2.1"
heimdalljs-logger "^0.1.7"
mkdirp "^0.5.1"
promise-map-series "^0.2.1"
rimraf "^2.6.1"
rsvp "^4.7.0"
symlink-or-copy "^1.0.1"
sync-disk-cache "^1.3.3"
walk-sync "^1.0.0"
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
broccoli-persistent-filter@^3.1.2:
version "3.1.3"
resolved "https://registry.yarnpkg.com/broccoli-persistent-filter/-/broccoli-persistent-filter-3.1.3.tgz#aca815bf3e3b0247bd0a7b567fdb0d0e08c99cc2"
integrity sha512-Q+8iezprZzL9voaBsDY3rQVl7c7H5h+bvv8SpzCZXPZgfBFCbx7KFQ2c3rZR6lW5k4Kwoqt7jG+rZMUg67Gwxw==
dependencies:
async-disk-cache "^2.0.0"
async-promise-queue "^1.0.3"
broccoli-plugin "^4.0.3"
fs-tree-diff "^2.0.0"
hash-for-dep "^1.5.0"
heimdalljs "^0.2.1"
heimdalljs-logger "^0.1.7"
promise-map-series "^0.2.1"
rimraf "^3.0.0"
symlink-or-copy "^1.0.1"
sync-disk-cache "^2.0.0"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
broccoli-plugin@^1.0.0, broccoli-plugin@^1.2.1, broccoli-plugin@^1.3.0:
version "1.3.1"
resolved "https://registry.yarnpkg.com/broccoli-plugin/-/broccoli-plugin-1.3.1.tgz#a26315732fb99ed2d9fb58f12a1e14e986b4fabd"
integrity sha512-DW8XASZkmorp+q7J4EeDEZz+LoyKLAd2XZULXyD9l4m9/hAKV3vjHmB1kiUshcWAYMgTP1m2i4NnqCE/23h6AQ==
dependencies:
promise-map-series "^0.2.1"
quick-temp "^0.1.3"
rimraf "^2.3.4"
symlink-or-copy "^1.1.8"
broccoli-plugin@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/broccoli-plugin/-/broccoli-plugin-2.1.0.tgz#2fab6c578219cfcc64f773e9616073313fc8b334"
integrity sha512-ElE4caljW4slapyEhSD9jU9Uayc8SoSABWdmY9SqbV8DHNxU6xg1jJsPcMm+cXOvggR3+G+OXAYQeFjWVnznaw==
dependencies:
promise-map-series "^0.2.1"
quick-temp "^0.1.3"
rimraf "^2.3.4"
symlink-or-copy "^1.1.8"
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
broccoli-plugin@^4.0.3:
version "4.0.7"
resolved "https://registry.yarnpkg.com/broccoli-plugin/-/broccoli-plugin-4.0.7.tgz#dd176a85efe915ed557d913744b181abe05047db"
integrity sha512-a4zUsWtA1uns1K7p9rExYVYG99rdKeGRymW0qOCNkvDPHQxVi3yVyJHhQbM3EZwdt2E0mnhr5e0c/bPpJ7p3Wg==
dependencies:
broccoli-node-api "^1.7.0"
broccoli-output-wrapper "^3.2.5"
fs-merger "^3.2.1"
promise-map-series "^0.3.0"
quick-temp "^0.1.8"
rimraf "^3.0.2"
symlink-or-copy "^1.3.1"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
broccoli-stew@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/broccoli-stew/-/broccoli-stew-3.0.0.tgz#fd1d19d162ad9490b42e5c563b78c26eb1e80b95"
integrity sha512-NXfi+Vas24n3Ivo21GvENTI55qxKu7OwKRnCLWXld8MiLiQKQlWIq28eoARaFj0lTUFwUa4jKZeA7fW9PiWQeg==
dependencies:
broccoli-debug "^0.6.5"
broccoli-funnel "^2.0.0"
broccoli-merge-trees "^3.0.1"
broccoli-persistent-filter "^2.3.0"
broccoli-plugin "^2.1.0"
chalk "^2.4.1"
debug "^4.1.1"
ensure-posix-path "^1.0.1"
fs-extra "^8.0.1"
minimatch "^3.0.4"
resolve "^1.11.1"
rsvp "^4.8.5"
symlink-or-copy "^1.2.0"
walk-sync "^1.1.3"
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
browserslist@^4.21.9:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
version "4.22.1"
resolved "https://registry.yarnpkg.com/browserslist/-/browserslist-4.22.1.tgz#ba91958d1a59b87dab6fed8dfbcb3da5e2e9c619"
integrity sha512-FEVc202+2iuClEhZhrWy6ZiAcRLvNMyYcxZ8raemul1DYVOVdFsbqckWLdsixQZCpJlwe77Z3UTalE7jsjnKfQ==
DEV: Merge package.json files (#21172) This means: a single yarn.lock and removing one of the package.json files
2023-04-20 06:46:12 -04:00
dependencies:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
caniuse-lite "^1.0.30001541"
electron-to-chromium "^1.4.535"
node-releases "^2.0.13"
update-browserslist-db "^1.0.13"
DEV: Merge package.json files (#21172) This means: a single yarn.lock and removing one of the package.json files
2023-04-20 06:46:12 -04:00
buffer-crc32@~0.2.3:
Update javascripts (#9907)
2020-05-28 12:15:13 -04:00
version "0.2.13"
resolved "https://registry.yarnpkg.com/buffer-crc32/-/buffer-crc32-0.2.13.tgz#0d333e3f00eac50aa1454abd30ef8c2a5d9a7242"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-VO9Ht/+p3SN7SKWqcrgEzjGbRSJYTx+Q1pTQC0wrWqHx0vpJraQ6GtHx8tvcg1rlK1byhU5gccxgOgj7B0TDkQ==
Update javascripts (#9907)
2020-05-28 12:15:13 -04:00
DEV: Switch from puppeteer to puppeteer-core for smoke test (#15262) `puppeteer` includes a full chromium binary, which adds more than 300mb to our node_modules directory in development/test mode (and therefore the `discourse_dev` and `discourse_test` docker images). We already reach out to the system copy of Chrome for our qunit tests, and already have chrome installed in our `discourse_dev`/`discourse_test` docker images, so it's much more efficient to switch to `puppeteer-core` which doesn't include the chromium binary.
2021-12-13 04:31:49 -05:00
buffer@^5.2.1, buffer@^5.5.0:
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
version "5.7.1"
resolved "https://registry.yarnpkg.com/buffer/-/buffer-5.7.1.tgz#ba62e7c13133053582197160851a8f648e99eed0"
integrity sha512-EHcyIPBQ4BSGlvjB16k5KgAJ27CIsHY/2JBmCRReo48y9rQ3MaUzWX3KVlBa4U7MyX02HdVj0K7C3WaB3ju7FQ==
dependencies:
base64-js "^1.3.1"
ieee754 "^1.1.13"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
call-bind@^1.0.0, call-bind@^1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/call-bind/-/call-bind-1.0.2.tgz#b1d4e89e688119c3c9a903ad30abb2f6a919be3c"
integrity sha512-7O+FbCihrB5WGbFYesctwmTKae6rOiIzmz1icreWJ+0aA7LJfuqhEso2T9ncpcFtzMQtzXf2QGGueWJGTYsqrA==
dependencies:
function-bind "^1.1.1"
get-intrinsic "^1.0.2"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
callsites@^3.0.0:
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
version "3.1.0"
resolved "https://registry.yarnpkg.com/callsites/-/callsites-3.1.0.tgz#b3630abd8943432f54b3f0519238e33cd7df2f73"
integrity sha512-P8BjAsXvZS+VIDUI11hHCQEv74YT67YUi5JJFNWIqL235sBmjX4+qx9Muvls5ivyNENctx46xQLQ3aTuE7ssaQ==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
can-symlink@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/can-symlink/-/can-symlink-1.0.0.tgz#97b607d8a84bb6c6e228b902d864ecb594b9d219"
integrity sha512-RbsNrFyhwkx+6psk/0fK/Q9orOUr9VMxohGd8vTa4djf4TGLfblBgUfqZChrZuW0Q+mz2eBPFLusw9Jfukzmhg==
dependencies:
tmp "0.0.28"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
caniuse-lite@^1.0.30001541:
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
version "1.0.30001550"
resolved "https://registry.yarnpkg.com/caniuse-lite/-/caniuse-lite-1.0.30001550.tgz#6ec6a2239eb2a8123cc26cfe0571db5c79eb8669"
integrity sha512-p82WjBYIypO0ukTsd/FG3Xxs+4tFeaY9pfT4amQL8KWtYH7H9nYwReGAbMTJ0hsmRO8IfDtsS6p3ZWj8+1c2RQ==
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
DEV: introduces documentation for chat (#19772) Note this commit also slightly changes internal API: channel instead of getChannel and updateCurrentUserChannelNotificationsSettings instead of updateCurrentUserChatChannelNotificationsSettings. Also destroyChannel takes a second param which is the name confirmation instead of an optional object containing this confirmation. This is to enforce the fact that it's required. In the future a top level jsdoc config file could be used instead of the hack tempfile, but while it's only an experiment for chat, it's probably good enough.
2023-01-18 06:36:16 -05:00
catharsis@^0.9.0:
version "0.9.0"
resolved "https://registry.yarnpkg.com/catharsis/-/catharsis-0.9.0.tgz#40382a168be0e6da308c277d3a2b3eb40c7d2121"
integrity sha512-prMTQVpcns/tzFgFVkVp6ak6RykZyWb3gu8ckUpd6YkTlacOd3DXGJjIpD4Q6zJirizvaiAjSSHlOsA+6sNh2A==
dependencies:
lodash "^4.17.15"
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
chai@^4.3.6:
Revert "DEV: FloatKit (#23541)" (#23549) This reverts commits 0623ac684a65f95ce4f5438ff47944b1dc2119f4 408e71e437ef8abf98f93e3449898bf906766b0e a32fa3b9470dde0543fcee809f2abd1f219f7336 User tips were running into some issues.
2023-09-12 13:55:12 -04:00
version "4.3.7"
resolved "https://registry.yarnpkg.com/chai/-/chai-4.3.7.tgz#ec63f6df01829088e8bf55fca839bcd464a8ec51"
integrity sha512-HLnAzZ2iupm25PlN0xFreAlBA5zaBSv3og0DdeGA4Ar6h6rJ3A0rolRUKJhSF2V10GZKDgWF/VmAEsNWjCRB+A==
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
dependencies:
assertion-error "^1.1.0"
check-error "^1.0.2"
deep-eql "^4.1.2"
get-func-name "^2.0.0"
loupe "^2.3.1"
pathval "^1.1.1"
type-detect "^4.0.5"
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
chalk@^2.4.1, chalk@^2.4.2:
DEV: uses central eslint-config-discourse (#8150) * DEV: uses centrain eslint-config-discourse Discourse project or plugins can now have a central configuration by doing: `yarn add --dev eslint-config-discourse@latest` * adds postinstall script
2019-10-07 20:56:24 -04:00
version "2.4.2"
resolved "https://registry.yarnpkg.com/chalk/-/chalk-2.4.2.tgz#cd42541677a54333cf541a49108c1432b44c9424"
integrity sha512-Mti+f9lpJNcwF4tWV8/OrTTtF1gZi+f8FqlyAdouralcFWFQWF2+NgCHShjkCb+IFBLq9buZwE1xckQU4peSuQ==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
dependencies:
Upgrade to FontAwesome 5 (take two) (#6673) * Add missing icons to set * Revert FA5 revert This reverts commit 42572ff * use new SVG syntax in locales * Noscript page changes (remove login button, center "powered by" footer text) * Cast wider net for SVG icons in settings - include any _icon setting for SVG registry (offers better support for plugin settings) - let themes store multiple pipe-delimited icons in a setting - also replaces broken onebox image icon with SVG reference in cooked post processor * interpolate icons in locales * Fix composer whisper icon alignment * Add support for stacked icons * SECURITY: enforce hostname to match discourse hostname This ensures that the hostname rails uses for various helpers always matches the Discourse hostname * load SVG sprite with pre-initializers * FIX: enable caching on SVG sprites * PERF: use JSONP for SVG sprites so they are served from CDN This avoids needing to deal with CORS for loading of the SVG Note, added the svg- prefix to the filename so we can quickly tell in dev tools what the file is * Add missing SVG sprite JSONP script to CSP * Upgrade to FA 5.5.0 * Add support for all FA4.7 icons - adds complete frontend and backend for renamed FA4.7 icons - improves performance of SvgSprite.bundle and SvgSprite.all_icons * Fix group avatar flair preview - adds an endpoint at /svg-sprites/search/:keyword - adds frontend ajax call that pulls icon in avatar flair preview even when it is not in subset * Remove FA 4.7 font files
2018-11-26 16:49:57 -05:00
ansi-styles "^3.2.1"
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
escape-string-regexp "^1.0.5"
Upgrade to FontAwesome 5 (take two) (#6673) * Add missing icons to set * Revert FA5 revert This reverts commit 42572ff * use new SVG syntax in locales * Noscript page changes (remove login button, center "powered by" footer text) * Cast wider net for SVG icons in settings - include any _icon setting for SVG registry (offers better support for plugin settings) - let themes store multiple pipe-delimited icons in a setting - also replaces broken onebox image icon with SVG reference in cooked post processor * interpolate icons in locales * Fix composer whisper icon alignment * Add support for stacked icons * SECURITY: enforce hostname to match discourse hostname This ensures that the hostname rails uses for various helpers always matches the Discourse hostname * load SVG sprite with pre-initializers * FIX: enable caching on SVG sprites * PERF: use JSONP for SVG sprites so they are served from CDN This avoids needing to deal with CORS for loading of the SVG Note, added the svg- prefix to the filename so we can quickly tell in dev tools what the file is * Add missing SVG sprite JSONP script to CSP * Upgrade to FA 5.5.0 * Add support for all FA4.7 icons - adds complete frontend and backend for renamed FA4.7 icons - improves performance of SvgSprite.bundle and SvgSprite.all_icons * Fix group avatar flair preview - adds an endpoint at /svg-sprites/search/:keyword - adds frontend ajax call that pulls icon in avatar flair preview even when it is not in subset * Remove FA 4.7 font files
2018-11-26 16:49:57 -05:00
supports-color "^5.3.0"
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
chalk@^4.0.0, chalk@^4.1.0, chalk@^4.1.2:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
version "4.1.2"
resolved "https://registry.yarnpkg.com/chalk/-/chalk-4.1.2.tgz#aac4e2b7734a740867aeb16bf02aad556a1e7a01"
integrity sha512-oKnbhFyRIXpUuez8iBMmyEa4nbj4IOQyuhc/wy9kY7/WVPcwIO9VA668Pu8RkO7+0G76SLROeyw9CpQ061i4mA==
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
dependencies:
ansi-styles "^4.1.0"
supports-color "^7.1.0"
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
chalk@^5.3.0:
version "5.3.0"
resolved "https://registry.yarnpkg.com/chalk/-/chalk-5.3.0.tgz#67c20a7ebef70e7f3970a01f90fa210cb6860385"
integrity sha512-dLitG79d+GV1Nb/VYcCDFivJeK1hiukt9QjRNVOsUtTy1rR1YJsmpGGTZ3qJos+uw7WmWF4wUwBd9jxjocFC2w==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
DEV: updates chart.js to 3.5.1 (#14107)
2021-08-23 07:49:49 -04:00
chart.js@3.5.1:
version "3.5.1"
resolved "https://registry.yarnpkg.com/chart.js/-/chart.js-3.5.1.tgz#73e24d23a4134a70ccdb5e79a917f156b6f3644a"
integrity sha512-m5kzt72I1WQ9LILwQC4syla/LD/N413RYv2Dx2nnTkRS9iv/ey1xLTt0DnPc/eWV4zI+BgEgDYBIzbQhZHc/PQ==
Use Yarn to manage dependencies, cleanup unused bootstrap libs (#6436)
2018-10-03 10:15:43 -04:00
DEV: Update sub-dependencies (#22325) Achieved by running `yarn upgrade --latest` both yarn.lock directories, then reverting changes to package.json files and running `yarn` again. I also de-duped yarn.lock files with `npx yarn-deduplicate && yarn`
2023-06-29 11:08:33 -04:00
chartjs-plugin-datalabels@2.2.0:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "2.2.0"
resolved "https://registry.yarnpkg.com/chartjs-plugin-datalabels/-/chartjs-plugin-datalabels-2.2.0.tgz#369578e131d743c2e34b5fbe2d3f9335f6639b8f"
integrity sha512-14ZU30lH7n89oq+A4bWaJPnAG8a7ZTk7dKf48YAzMvJjQtjrgg5Dpk9f+LbjCF6bpx3RAGTeL13IXpKQYyRvlw==
FEATURE: Poll breakdown 2.0 (#10345) The poll breakdown modal replaces the grouped pie charts feature. Includes: * MODAL: Untangle `onSelectPanel` Previously modal-tab component would call on click the onSelectPanel callback with itself (modal-tab) as `this` which severely limited its usefulness. Now showModal binds the callback to its controller. "The PR includes a fix/change to d-modal (b7f6ec6) that hasn't been extracted to a separate PR because it's not currently possible to test a change like this in abstract, i.e. with dynamically created controllers/components in tests. The percentage/count toggle test for the poll breakdown feature is essentially a test for that d-modal modification."
2020-08-06 11:57:06 -04:00
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
check-error@^1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/check-error/-/check-error-1.0.2.tgz#574d312edd88bb5dd8912e9286dd6c0aed4aac82"
integrity sha512-BrgHpW9NURQgzoNyjfq0Wu6VFO6D7IZEmJNdtgNqpzGG8RuNFHt2jQxWlAs4HMe119chBnv+34syEZtc6IhLtA==
DEV: Bump chrome-launcher (#19082)
2022-11-17 18:03:05 -05:00
chrome-launcher@^0.15.1:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "0.15.2"
resolved "https://registry.yarnpkg.com/chrome-launcher/-/chrome-launcher-0.15.2.tgz#4e6404e32200095fdce7f6a1e1004f9bd36fa5da"
integrity sha512-zdLEwNo3aUVzIhKhTtXfxhdvZhUghrnmkvcAq2NoDd+LeOHKf03H5jwZ8T/STsAlzyALkBVK552iaG1fGf1xVQ==
Run JS test in chrome headless on Travis.
2017-12-14 21:15:04 -05:00
dependencies:
DEV: Update chrome-launcher (#8318) This version is compatible with macOS Catalina
2019-11-08 10:50:41 -05:00
"@types/node" "*"
FIX: Qunit tests were failing if your node was defaulting to IPV6 (#15773) This is now the default in newer node versions. The code that fails is a workaround for another error :'( This also upgrades `chrome-launcher` which helpers with debugging.
2022-02-02 10:56:03 -05:00
escape-string-regexp "^4.0.0"
is-wsl "^2.2.0"
Run JS test in chrome headless on Travis.
2017-12-14 21:15:04 -05:00
lighthouse-logger "^1.0.0"
DEV: Bump chrome-remote-interface (#19083)
2022-11-17 17:21:10 -05:00
chrome-remote-interface@^0.31.3:
version "0.31.3"
resolved "https://registry.yarnpkg.com/chrome-remote-interface/-/chrome-remote-interface-0.31.3.tgz#bd01b89f5f0e968f7eeb37b8b7c5ac20e6e1f4d0"
integrity sha512-NTwb1YNPHXLTus1RjqsLxJmdViKwKJg/lrFEcM6pbyQy04Ow2QKWHXyPpxzwE+dFsJghWuvSAdTy4W0trluz1g==
Run JS test in chrome headless on Travis.
2017-12-14 21:15:04 -05:00
dependencies:
commander "2.11.x"
DEV: Bump chrome-launcher/chrome-remote-interface (#16160)
2022-03-12 13:52:07 -05:00
ws "^7.2.0"
Run JS test in chrome headless on Travis.
2017-12-14 21:15:04 -05:00
Revert "DEV: FloatKit (#23541)" (#23549) This reverts commits 0623ac684a65f95ce4f5438ff47944b1dc2119f4 408e71e437ef8abf98f93e3449898bf906766b0e a32fa3b9470dde0543fcee809f2abd1f219f7336 User tips were running into some issues.
2023-09-12 13:55:12 -04:00
chromium-bidi@0.4.20:
version "0.4.20"
resolved "https://registry.yarnpkg.com/chromium-bidi/-/chromium-bidi-0.4.20.tgz#1cd56426638452b40b29b7054e83c379e7e2b20a"
integrity sha512-ruHgVZFEv00mAQMz1tQjfjdG63jiPWrQPF6HLlX2ucqLqVTJoWngeBEKHaJ6n1swV/HSvgnBNbtTRIlcVyW3Fw==
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
dependencies:
mitt "3.0.1"
DEV: Update ember-template-lint (#22242)
2023-06-22 16:54:46 -04:00
ci-info@^3.8.0:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
version "3.9.0"
resolved "https://registry.yarnpkg.com/ci-info/-/ci-info-3.9.0.tgz#4279a62028a7b1f262f3473fc9605f5e218c59b4"
integrity sha512-NIxF55hv4nSqQswkAeiOi1r83xy8JldOFDTWiug55KBu9Jnblncd2U6ViHmYgHf01TPZS77NJBhBMKdWj9HQMQ==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
clean-up-path@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/clean-up-path/-/clean-up-path-1.0.0.tgz#de9e8196519912e749c9eaf67c13d64fac72a3e5"
integrity sha512-PHGlEF0Z6976qQyN6gM7kKH6EH0RdfZcc8V+QhFe36eRxV0SMH5OUBZG7Bxa9YcreNzyNbK63cGiZxdSZgosRw==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
cli-cursor@^3.1.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/cli-cursor/-/cli-cursor-3.1.0.tgz#264305a7ae490d1d03bf0c9ba7c925d1753af307"
integrity sha512-I/zHAwsKf9FqGoXM4WWRACob9+SNukZTd94DWF57E4toouRulbCxcUh6RKUEOQlYTHJnzkPMySvPNaaSLNfLZw==
dependencies:
restore-cursor "^3.1.0"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
cli-spinners@^2.5.0:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
version "2.9.1"
resolved "https://registry.yarnpkg.com/cli-spinners/-/cli-spinners-2.9.1.tgz#9c0b9dad69a6d47cbb4333c14319b060ed395a35"
integrity sha512-jHgecW0pxkonBJdrKsqxgRX9AcG+u/5k0Q7WPDfi8AogLAdwxEkyYYNWwZ5GvVFoFx2uiY1eNcSK00fh+1+FyQ==
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
cliui@^8.0.1:
version "8.0.1"
resolved "https://registry.yarnpkg.com/cliui/-/cliui-8.0.1.tgz#0c04b075db02cbfe60dc8e6cf2f5486b1a3608aa"
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"
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
clone@^1.0.2:
version "1.0.4"
resolved "https://registry.yarnpkg.com/clone/-/clone-1.0.4.tgz#da309cc263df15994c688ca902179ca3c7cd7c7e"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-JQHZ2QMW6l3aH/j6xCqQThY/9OH4D/9ls34cgkUBiEeocRTU04tHfKPBsUK1PqZCUQM7GiA0IIXJSuXHI64Kbg==
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
DEV: updates chart.js to 3.5.1 (#14107)
2021-08-23 07:49:49 -04:00
color-convert@^1.9.0:
Upgrade to FontAwesome 5 (take two) (#6673) * Add missing icons to set * Revert FA5 revert This reverts commit 42572ff * use new SVG syntax in locales * Noscript page changes (remove login button, center "powered by" footer text) * Cast wider net for SVG icons in settings - include any _icon setting for SVG registry (offers better support for plugin settings) - let themes store multiple pipe-delimited icons in a setting - also replaces broken onebox image icon with SVG reference in cooked post processor * interpolate icons in locales * Fix composer whisper icon alignment * Add support for stacked icons * SECURITY: enforce hostname to match discourse hostname This ensures that the hostname rails uses for various helpers always matches the Discourse hostname * load SVG sprite with pre-initializers * FIX: enable caching on SVG sprites * PERF: use JSONP for SVG sprites so they are served from CDN This avoids needing to deal with CORS for loading of the SVG Note, added the svg- prefix to the filename so we can quickly tell in dev tools what the file is * Add missing SVG sprite JSONP script to CSP * Upgrade to FA 5.5.0 * Add support for all FA4.7 icons - adds complete frontend and backend for renamed FA4.7 icons - improves performance of SvgSprite.bundle and SvgSprite.all_icons * Fix group avatar flair preview - adds an endpoint at /svg-sprites/search/:keyword - adds frontend ajax call that pulls icon in avatar flair preview even when it is not in subset * Remove FA 4.7 font files
2018-11-26 16:49:57 -05:00
version "1.9.3"
resolved "https://registry.yarnpkg.com/color-convert/-/color-convert-1.9.3.tgz#bb71850690e1f136567de629d2d5471deda4c1e8"
integrity sha512-QfAUtd+vFdAtFQcC8CCyYt1fYWxSqAiK2cSD6zDB8N3cpsEBAvRxp9zOGg6G/SHHJYAT88/az/IuDGALsNVbGg==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
dependencies:
Upgrade to FontAwesome 5 (take two) (#6673) * Add missing icons to set * Revert FA5 revert This reverts commit 42572ff * use new SVG syntax in locales * Noscript page changes (remove login button, center "powered by" footer text) * Cast wider net for SVG icons in settings - include any _icon setting for SVG registry (offers better support for plugin settings) - let themes store multiple pipe-delimited icons in a setting - also replaces broken onebox image icon with SVG reference in cooked post processor * interpolate icons in locales * Fix composer whisper icon alignment * Add support for stacked icons * SECURITY: enforce hostname to match discourse hostname This ensures that the hostname rails uses for various helpers always matches the Discourse hostname * load SVG sprite with pre-initializers * FIX: enable caching on SVG sprites * PERF: use JSONP for SVG sprites so they are served from CDN This avoids needing to deal with CORS for loading of the SVG Note, added the svg- prefix to the filename so we can quickly tell in dev tools what the file is * Add missing SVG sprite JSONP script to CSP * Upgrade to FA 5.5.0 * Add support for all FA4.7 icons - adds complete frontend and backend for renamed FA4.7 icons - improves performance of SvgSprite.bundle and SvgSprite.all_icons * Fix group avatar flair preview - adds an endpoint at /svg-sprites/search/:keyword - adds frontend ajax call that pulls icon in avatar flair preview even when it is not in subset * Remove FA 4.7 font files
2018-11-26 16:49:57 -05:00
color-name "1.1.3"
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
color-convert@^2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/color-convert/-/color-convert-2.0.1.tgz#72d3a68d598c9bdb3af2ad1e84f21d896abd4de3"
integrity sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ==
dependencies:
color-name "~1.1.4"
Upgrade to FontAwesome 5 (take two) (#6673) * Add missing icons to set * Revert FA5 revert This reverts commit 42572ff * use new SVG syntax in locales * Noscript page changes (remove login button, center "powered by" footer text) * Cast wider net for SVG icons in settings - include any _icon setting for SVG registry (offers better support for plugin settings) - let themes store multiple pipe-delimited icons in a setting - also replaces broken onebox image icon with SVG reference in cooked post processor * interpolate icons in locales * Fix composer whisper icon alignment * Add support for stacked icons * SECURITY: enforce hostname to match discourse hostname This ensures that the hostname rails uses for various helpers always matches the Discourse hostname * load SVG sprite with pre-initializers * FIX: enable caching on SVG sprites * PERF: use JSONP for SVG sprites so they are served from CDN This avoids needing to deal with CORS for loading of the SVG Note, added the svg- prefix to the filename so we can quickly tell in dev tools what the file is * Add missing SVG sprite JSONP script to CSP * Upgrade to FA 5.5.0 * Add support for all FA4.7 icons - adds complete frontend and backend for renamed FA4.7 icons - improves performance of SvgSprite.bundle and SvgSprite.all_icons * Fix group avatar flair preview - adds an endpoint at /svg-sprites/search/:keyword - adds frontend ajax call that pulls icon in avatar flair preview even when it is not in subset * Remove FA 4.7 font files
2018-11-26 16:49:57 -05:00
color-name@1.1.3:
version "1.1.3"
resolved "https://registry.yarnpkg.com/color-name/-/color-name-1.1.3.tgz#a7d0558bd89c42f795dd42328f740831ca53bc25"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-72fSenhMw2HZMTVHeCA9KCmpEIbzWiQsjN+BHcBbS9vr1mtt+vJjPdksIBNUmKAW8TFUDPJK5SUU3QhE9NEXDw==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
DEV: updates chart.js to 3.5.1 (#14107)
2021-08-23 07:49:49 -04:00
color-name@~1.1.4:
Use Yarn to manage dependencies, cleanup unused bootstrap libs (#6436)
2018-10-03 10:15:43 -04:00
version "1.1.4"
resolved "https://registry.yarnpkg.com/color-name/-/color-name-1.1.4.tgz#c2a09a87acbde69543de6f63fa3995c826c536a2"
Update yarn.lock with integrity hashes This should prevent the stable version of yarn from rewriting the lock file all the time.
2018-10-04 05:21:13 -04:00
integrity sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA==
Use Yarn to manage dependencies, cleanup unused bootstrap libs (#6436)
2018-10-03 10:15:43 -04:00
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
colors@^1.4.0:
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
version "1.4.0"
resolved "https://registry.yarnpkg.com/colors/-/colors-1.4.0.tgz#c50491479d4c1bdaed2c9ced32cf7c7dc2360f78"
integrity sha512-a+UqTh4kgZg/SlGvfbzDHpgRu7AAQOmmqRHJnxhRZICKFUT91brVhNNt58CMWU9PsBbv3PDCZUHbVxuDiH2mtA==
Run JS test in chrome headless on Travis.
2017-12-14 21:15:04 -05:00
commander@2.11.x:
version "2.11.0"
resolved "https://registry.yarnpkg.com/commander/-/commander-2.11.0.tgz#157152fd1e7a6c8d98a5b715cf376df928004563"
Update yarn.lock with integrity hashes This should prevent the stable version of yarn from rewriting the lock file all the time.
2018-10-04 05:21:13 -04:00
integrity sha512-b0553uYA5YAEGgyYIGYROzKQ7X5RAqedkfjiZxwi0kL1g3bOaBNNZfYkzt/CL0umgD5wc9Jec2FbB98CjkMRvQ==
Run JS test in chrome headless on Travis.
2017-12-14 21:15:04 -05:00
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
commander@^7.0.0:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "7.2.0"
resolved "https://registry.yarnpkg.com/commander/-/commander-7.2.0.tgz#a36cb57d0b501ce108e4d20559a150a391d97ab7"
integrity sha512-QrWXB+ZQSVPmIWIhtEO9H+gwHaMGYiF5ChvoJ+K9ZGHG/sVsa6yiesAD1GC/x46sET00Xlwo1u49RVVVzvcSkw==
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
commander@^8.3.0:
version "8.3.0"
resolved "https://registry.yarnpkg.com/commander/-/commander-8.3.0.tgz#4837ea1b2da67b9c616a67afbb0fafee567bca66"
integrity sha512-OkTL9umf+He2DZkUq8f8J9of7yL6RJKI24dVITBmNfZBmri9zYZQrKkuXiKhyfPSu8tUhnVBB1iKXevvnlR4Ww==
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
commander@^9.4.1:
version "9.5.0"
resolved "https://registry.yarnpkg.com/commander/-/commander-9.5.0.tgz#bc08d1eb5cedf7ccb797a96199d41c7bc3e60d30"
integrity sha512-KRs7WVDKg86PWiuAqhDrAQnTXZKraVcCc6vFdL14qrZ/DcWwuRo7VoiYXalXO7S5GKpqYiVEwCbgFDfxNHKJBQ==
Run JS test in chrome headless on Travis.
2017-12-14 21:15:04 -05:00
concat-map@0.0.1:
version "0.0.1"
resolved "https://registry.yarnpkg.com/concat-map/-/concat-map-0.0.1.tgz#d8a96bd77fd68df7793a73036a3ba0d5405d477b"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-/Srv4dswyQNBfohGpz9o6Yb3Gz3SrUDqBH5rTuhGR7ahtlbYKnVxw2bCFMRljaA7EXHaXZ8wsHdodFvbkhKmqg==
Run JS test in chrome headless on Travis.
2017-12-14 21:15:04 -05:00
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
concurrently@^8.2.1:
version "8.2.1"
resolved "https://registry.yarnpkg.com/concurrently/-/concurrently-8.2.1.tgz#bcab9cacc38c23c503839583151e0fa96fd5b584"
integrity sha512-nVraf3aXOpIcNud5pB9M82p1tynmZkrSGQ1p6X/VY8cJ+2LMVqAgXsJxYYefACSHbTYlm92O1xuhdGTjwoEvbQ==
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
dependencies:
chalk "^4.1.2"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
date-fns "^2.30.0"
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
lodash "^4.17.21"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
rxjs "^7.8.1"
shell-quote "^1.8.1"
spawn-command "0.0.2"
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
supports-color "^8.1.1"
tree-kill "^1.2.2"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
yargs "^17.7.2"
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
convert-source-map@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/convert-source-map/-/convert-source-map-2.0.0.tgz#4b560f649fc4e918dd0ab75cf4961e8bc882d82a"
integrity sha512-Kvp459HrV2FEJ1CAsi1Ku+MY3kasH19TFykTz2xWmMeq6bk2NU3XXvfJ+Q61m0xktWwt+1HSYf3JZsTms3aRJg==
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
core-js@^3.27.2, core-js@^3.4.1:
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
version "3.33.0"
resolved "https://registry.yarnpkg.com/core-js/-/core-js-3.33.0.tgz#70366dbf737134761edb017990cf5ce6c6369c40"
integrity sha512-HoZr92+ZjFEKar5HS6MC776gYslNOKHt75mEBKWKnPeFDpZ6nH5OeF3S6HFT1mUAUZKrzkez05VboaX8myjSuw==
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
DEV: Use eslint-config-discourse as source of truth for linting dependencies (#8388)
2019-11-22 13:16:11 -05:00
core-util-is@~1.0.0:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "1.0.3"
resolved "https://registry.yarnpkg.com/core-util-is/-/core-util-is-1.0.3.tgz#a6042d3634c2b27e9328f837b965fac83808db85"
integrity sha512-ZQBvi1DcpJ4GDqanjucZ2Hj3wEO5pZDS89BWbkcrvdxksJorwUDDZamX9ldFkp9aw2lmBDLgkObEA4DWNJ9FYQ==
Add smoke test script that runs in chrome headless.
2017-12-18 03:32:58 -05:00
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
cross-fetch@4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/cross-fetch/-/cross-fetch-4.0.0.tgz#f037aef1580bb3a1a35164ea2a848ba81b445983"
integrity sha512-e4a5N8lVvuLgAWgnCrLr2PP0YyDOTHa9H/Rj54dirp61qXnNq46m82bRhNqIA5VccJtWBvPTFRV3TtvHUKPB1g==
DEV: Update puppeteer, fix deprecations, lint (#16616) 1. Updates puppeteer to x 2. Fixes deprecations: ``` waitFor is deprecated and will be removed in a future release. See https://github.com/puppeteer/puppeteer/issues/6214 for details and how to migrate your code. ``` 3. Lints/prettyfies the smoke_test.js file
2022-05-03 14:58:58 -04:00
dependencies:
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
node-fetch "^2.6.12"
DEV: Update puppeteer, fix deprecations, lint (#16616) 1. Updates puppeteer to x 2. Fixes deprecations: ``` waitFor is deprecated and will be removed in a future release. See https://github.com/puppeteer/puppeteer/issues/6214 for details and how to migrate your code. ``` 3. Lints/prettyfies the smoke_test.js file
2022-05-03 14:58:58 -04:00
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
cross-spawn@^7.0.2:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
version "7.0.3"
resolved "https://registry.yarnpkg.com/cross-spawn/-/cross-spawn-7.0.3.tgz#f73a85b9d5d41d045551c177e2882d4ac85728a6"
integrity sha512-iRDPJKUPVEND7dHPO8rkbOnPpyDygcDFtWjpeWNCgy8WP2rXcxXL8TskReQl6OrB2G7+UJrags1q15Fudc7G6w==
DEV: upgrades from Ember 2.13 to Ember 3.5.1 (#6808) Co-Authored-By: Bianca Nenciu <nbianca@users.noreply.github.com> Co-Authored-By: David Taylor <david@taylorhq.com>
2019-01-10 05:06:01 -05:00
dependencies:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
path-key "^3.1.0"
shebang-command "^2.0.0"
which "^2.0.1"
DEV: upgrades from Ember 2.13 to Ember 3.5.1 (#6808) Co-Authored-By: Bianca Nenciu <nbianca@users.noreply.github.com> Co-Authored-By: David Taylor <david@taylorhq.com>
2019-01-10 05:06:01 -05:00
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
css-tree@^2.0.4:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "2.3.1"
resolved "https://registry.yarnpkg.com/css-tree/-/css-tree-2.3.1.tgz#10264ce1e5442e8572fc82fbe490644ff54b5c20"
integrity sha512-6Fv1DV/TYw//QF5IzQdqsNDjx/wc8TrMBZsqjL9eW01tWb7R7k/mq+/VXfJCl7SoD5emsJop9cOByJZfs8hYIw==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
dependencies:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
mdn-data "2.0.30"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
source-map-js "^1.0.1"
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
data-uri-to-buffer@^5.0.1:
version "5.0.1"
resolved "https://registry.yarnpkg.com/data-uri-to-buffer/-/data-uri-to-buffer-5.0.1.tgz#db89a9e279c2ffe74f50637a59a32fb23b3e4d7c"
integrity sha512-a9l6T1qqDogvvnw0nKlfZzqsyikEBZBClF39V3TFoKhDtGBqHu2HkuomJc02j5zft8zrUaXEuoicLeW54RkzPg==
DEV: Update ember-template-lint (#22242)
2023-06-22 16:54:46 -04:00
date-fns@^2.30.0:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "2.30.0"
resolved "https://registry.yarnpkg.com/date-fns/-/date-fns-2.30.0.tgz#f367e644839ff57894ec6ac480de40cae4b0f4d0"
integrity sha512-fnULvOpxnC5/Vg3NCiWelDsLiUc9bRwAPs/+LfTLNvetFCtCTN+yQz15C/fs4AwX1R9K5GLtLfn8QW+dWisaAw==
dependencies:
"@babel/runtime" "^7.21.0"
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
debug@4, debug@4.3.4, debug@^4.1.0, debug@^4.1.1, debug@^4.3.2, debug@^4.3.4:
DEV: Update puppeteer, fix deprecations, lint (#16616) 1. Updates puppeteer to x 2. Fixes deprecations: ``` waitFor is deprecated and will be removed in a future release. See https://github.com/puppeteer/puppeteer/issues/6214 for details and how to migrate your code. ``` 3. Lints/prettyfies the smoke_test.js file
2022-05-03 14:58:58 -04:00
version "4.3.4"
resolved "https://registry.yarnpkg.com/debug/-/debug-4.3.4.tgz#1319f6579357f2338d3337d2cdd4914bb5dcc865"
integrity sha512-PRWFHuSU3eDtQJPvnNY7Jcket1j0t5OuOsFzPPzsekD52Zl8qUfFIPEiswXqIvHWGVHOgX+7G/vCNNhehwxfkQ==
DEV: Switch from puppeteer to puppeteer-core for smoke test (#15262) `puppeteer` includes a full chromium binary, which adds more than 300mb to our node_modules directory in development/test mode (and therefore the `discourse_dev` and `discourse_test` docker images). We already reach out to the system copy of Chrome for our qunit tests, and already have chrome installed in our `discourse_dev`/`discourse_test` docker images, so it's much more efficient to switch to `puppeteer-core` which doesn't include the chromium binary.
2021-12-13 04:31:49 -05:00
dependencies:
ms "2.1.2"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
debug@^2.1.3, debug@^2.2.0, debug@^2.6.8, debug@^2.6.9:
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
version "2.6.9"
resolved "https://registry.yarnpkg.com/debug/-/debug-2.6.9.tgz#5d128515df134ff327e90a4c93f4e077a536341f"
integrity sha512-bC7ElrdJaJnPbAP+1EotYvqZsb3ecl5wi6Bfi6BJTUcNowp6cvspg0jXznRTKDjm/E7AdgFBVeAPVMNcKGsHMA==
Run JS test in chrome headless on Travis.
2017-12-14 21:15:04 -05:00
dependencies:
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
ms "2.0.0"
Run JS test in chrome headless on Travis.
2017-12-14 21:15:04 -05:00
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
deep-eql@^4.1.2:
version "4.1.3"
resolved "https://registry.yarnpkg.com/deep-eql/-/deep-eql-4.1.3.tgz#7c7775513092f7df98d8df9996dd085eb668cc6d"
integrity sha512-WaEtAOpRA1MQ0eohqZjpGD8zdI0Ovsm8mmFhaDN8dvDZzyoUMcYDnf5Y6iu7HTXxf8JDS23qWa4a+hKCDyOPzw==
dependencies:
type-detect "^4.0.0"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
deep-is@^0.1.3:
version "0.1.4"
resolved "https://registry.yarnpkg.com/deep-is/-/deep-is-0.1.4.tgz#a6f2dce612fadd2ef1f519b73551f17e85199831"
integrity sha512-oIPzksmTg4/MriiaYGO+okXDT7ztn/w3Eptv/+gSIdMdKsJo0u4CfYNFJPy+4SKMuCqGw2wxnA+URMg3t8a/bQ==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
defaults@^1.0.3:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "1.0.4"
resolved "https://registry.yarnpkg.com/defaults/-/defaults-1.0.4.tgz#b0b02062c1e2aa62ff5d9528f0f98baa90978d7a"
integrity sha512-eFuaLoy/Rxalv2kr+lqMlUnrDWV+3j4pljOIJgLIhI058IQfWJ7vXhyEIHu+HtC738klGALYxOKDO0bQP3tg8A==
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
dependencies:
clone "^1.0.2"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
define-data-property@^1.0.1:
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
version "1.1.1"
resolved "https://registry.yarnpkg.com/define-data-property/-/define-data-property-1.1.1.tgz#c35f7cd0ab09883480d12ac5cb213715587800b3"
integrity sha512-E7uGkTzkk1d0ByLeSc6ZsFS79Axg+m1P/VsgYsxHgiuc3tFSj+MjMIwe90FC4lOAZzNBdY7kkO2P2wKdsQ1vgQ==
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
dependencies:
get-intrinsic "^1.2.1"
gopd "^1.0.1"
has-property-descriptors "^1.0.0"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
define-properties@^1.1.3, define-properties@^1.1.4, define-properties@^1.2.0:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
version "1.2.1"
resolved "https://registry.yarnpkg.com/define-properties/-/define-properties-1.2.1.tgz#10781cc616eb951a80a034bafcaa7377f6af2b6c"
integrity sha512-8QmQKqEASLd5nx0U1B1okLElbUuuttJ/AnYmRXbbbGDWh6uS208EjD4Xqq/I9wK7u0v6O08XhTWnt5XtEbR6Dg==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
dependencies:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
define-data-property "^1.0.1"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
has-property-descriptors "^1.0.0"
object-keys "^1.1.1"
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
degenerator@^5.0.0:
version "5.0.1"
resolved "https://registry.yarnpkg.com/degenerator/-/degenerator-5.0.1.tgz#9403bf297c6dad9a1ece409b37db27954f91f2f5"
integrity sha512-TllpMR/t0M5sqCXfj85i4XaAzxmS5tVA16dqvdkMwGmzI+dXLXnw3J+3Vdv7VKw+ThlTMboK6i9rnZ6Nntj5CQ==
dependencies:
ast-types "^0.13.4"
escodegen "^2.1.0"
esprima "^4.0.1"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
dequal@^2.0.3:
version "2.0.3"
resolved "https://registry.yarnpkg.com/dequal/-/dequal-2.0.3.tgz#2644214f1997d39ed0ee0ece72335490a7ac67be"
integrity sha512-0je+qPKHEMohvfRTCEo3CrPG6cAzAYgmzKyxRiYSSDkS6eGJdyVJm7WaYA5ECaAD9wLB2T4EEeymA5aFVcYXCA==
Revert "DEV: FloatKit (#23541)" (#23549) This reverts commits 0623ac684a65f95ce4f5438ff47944b1dc2119f4 408e71e437ef8abf98f93e3449898bf906766b0e a32fa3b9470dde0543fcee809f2abd1f219f7336 User tips were running into some issues.
2023-09-12 13:55:12 -04:00
devtools-protocol@0.0.1147663:
version "0.0.1147663"
resolved "https://registry.yarnpkg.com/devtools-protocol/-/devtools-protocol-0.0.1147663.tgz#4ec5610b39a6250d1f87e6b9c7e16688ed0ac78e"
integrity sha512-hyWmRrexdhbZ1tcJUGpO95ivbRhWXz++F4Ko+n21AY5PNln2ovoJw+8ZMNDTtip+CNFQfrtLVh/w4009dXO/eQ==
DEV: Switch from puppeteer to puppeteer-core for smoke test (#15262) `puppeteer` includes a full chromium binary, which adds more than 300mb to our node_modules directory in development/test mode (and therefore the `discourse_dev` and `discourse_test` docker images). We already reach out to the system copy of Chrome for our qunit tests, and already have chrome installed in our `discourse_dev`/`discourse_test` docker images, so it's much more efficient to switch to `puppeteer-core` which doesn't include the chromium binary.
2021-12-13 04:31:49 -05:00
DEV: Update to diffHTML 1.0.0-beta.30 (#23729)
2023-10-03 03:15:17 -04:00
diffhtml@1.0.0-beta.30:
version "1.0.0-beta.30"
resolved "https://registry.yarnpkg.com/diffhtml/-/diffhtml-1.0.0-beta.30.tgz#725c0a5941bd825675f8a62b701a12a67e7516c7"
integrity sha512-yrBteaq309reltj+kAnGqsnpJyQSqmCkd5LAJNAcWNmlgvu+PbiUm9bNxdRYi21BQsQsljTxrjs+AWeeHHghWA==
FEATURE: Use diffhtml to update composer preview (#11237) Displaying videos, animated GIFs or any kind of rich content in preview used to refresh on every keystroke, which could cause performance problems.
2021-02-18 09:07:26 -05:00
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
dir-glob@^3.0.1:
version "3.0.1"
resolved "https://registry.yarnpkg.com/dir-glob/-/dir-glob-3.0.1.tgz#56dbf73d992a4a93ba1584f4534063fd2e41717f"
integrity sha512-WkrWp9GR4KXfKGYzOLmTuGVi1UWFfws377n9cc55/tb6DuqyF6pcQ5AbiHEshaDpY9v6oaSr2XCDidGmMwdzIA==
Support for Ember Template linting
2020-02-05 11:33:15 -05:00
dependencies:
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
path-type "^4.0.0"
Support for Ember Template linting
2020-02-05 11:33:15 -05:00
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
doctrine@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/doctrine/-/doctrine-3.0.0.tgz#addebead72a6574db783639dc87a121773973961"
integrity sha512-yS+Q5i3hBf7GBkd4KG8a7eBNNWNGLTaEwwYWUijIYM7zrlYDM0BFXHjjPWlWZ1Rg7UaddZeIDmi9jF3HmqiQ2w==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
dependencies:
DEV: Merge package.json files (#21172) This means: a single yarn.lock and removing one of the package.json files
2023-04-20 06:46:12 -04:00
esutils "^2.0.2"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
dot-case@^3.0.4:
version "3.0.4"
resolved "https://registry.yarnpkg.com/dot-case/-/dot-case-3.0.4.tgz#9b2b670d00a431667a8a75ba29cd1b98809ce751"
integrity sha512-Kv5nKlh6yRrdrGvxeJ2e5y2eRUpkUosIW4A2AS38zwSz27zu7ufDwQPi5Jhs3XAlGNetl3bmnGhQsMtkKJnj3w==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
dependencies:
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
no-case "^3.0.4"
tslib "^2.0.3"
DEV: Merge package.json files (#21172) This means: a single yarn.lock and removing one of the package.json files
2023-04-20 06:46:12 -04:00
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
duplexify@^4.1.1:
version "4.1.2"
resolved "https://registry.yarnpkg.com/duplexify/-/duplexify-4.1.2.tgz#18b4f8d28289132fa0b9573c898d9f903f81c7b0"
integrity sha512-fz3OjcNCHmRP12MJoZMPglx8m4rrFP8rovnk4vT8Fs+aonZoCwGg10dSsQsfP/E62eZcPTMSMP6686fu9Qlqtw==
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
dependencies:
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
end-of-stream "^1.4.1"
inherits "^2.0.3"
readable-stream "^3.1.1"
stream-shift "^1.0.0"
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
editions@^1.1.1:
version "1.3.4"
resolved "https://registry.yarnpkg.com/editions/-/editions-1.3.4.tgz#3662cb592347c3168eb8e498a0ff73271d67f50b"
integrity sha512-gzao+mxnYDzIysXKMQi/+M1mjy/rjestjg6OPoYTtI+3Izp23oiGZitsl9lPDPiTGXbcSIk1iJWhliSaglxnUg==
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
editions@^2.2.0:
version "2.3.1"
resolved "https://registry.yarnpkg.com/editions/-/editions-2.3.1.tgz#3bc9962f1978e801312fbd0aebfed63b49bfe698"
integrity sha512-ptGvkwTvGdGfC0hfhKg0MT+TRLRKGtUiWGBInxOm5pz7ssADezahjCUaYuZ8Dr+C05FW0AECIIPt4WBxVINEhA==
dependencies:
errlop "^2.0.0"
semver "^6.3.0"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
electron-to-chromium@^1.4.535:
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
version "1.4.557"
resolved "https://registry.yarnpkg.com/electron-to-chromium/-/electron-to-chromium-1.4.557.tgz#f3941b569c82b7bb909411855c6ff9bfe1507829"
integrity sha512-6x0zsxyMXpnMJnHrondrD3SuAeKcwij9S+83j2qHAQPXbGTDDfgImzzwgGlzrIcXbHQ42tkG4qA6U860cImNhw==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
ember-cli-babel-plugin-helpers@^1.1.1:
version "1.1.1"
resolved "https://registry.yarnpkg.com/ember-cli-babel-plugin-helpers/-/ember-cli-babel-plugin-helpers-1.1.1.tgz#5016b80cdef37036c4282eef2d863e1d73576879"
integrity sha512-sKvOiPNHr5F/60NLd7SFzMpYPte/nnGkq/tMIfXejfKHIhaiIkYFqX8Z9UFTKWLLn+V7NOaby6niNPZUdvKCRw==
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
ember-cli-htmlbars@^6.2.0:
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
version "6.3.0"
resolved "https://registry.yarnpkg.com/ember-cli-htmlbars/-/ember-cli-htmlbars-6.3.0.tgz#ac85f2bbd09788992ab7f9ca832cd044fb8e5798"
integrity sha512-N9Y80oZfcfWLsqickMfRd9YByVcTGyhYRnYQ2XVPVrp6jyUyOeRWmEAPh7ERSXpp8Ws4hr/JB9QVQrn/yZa+Ag==
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
dependencies:
"@ember/edition-utils" "^1.2.0"
babel-plugin-ember-template-compilation "^2.0.0"
babel-plugin-htmlbars-inline-precompile "^5.3.0"
broccoli-debug "^0.6.5"
broccoli-persistent-filter "^3.1.2"
broccoli-plugin "^4.0.3"
ember-cli-version-checker "^5.1.2"
fs-tree-diff "^2.0.1"
hash-for-dep "^1.5.1"
heimdalljs-logger "^0.1.10"
js-string-escape "^1.0.1"
semver "^7.3.4"
silent-error "^1.1.1"
walk-sync "^2.2.0"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
ember-cli-version-checker@^5.1.2:
version "5.1.2"
resolved "https://registry.yarnpkg.com/ember-cli-version-checker/-/ember-cli-version-checker-5.1.2.tgz#649c7b6404902e3b3d69c396e054cea964911ab0"
integrity sha512-rk7GY+FmLn/2e22HsZs0Ycrz8HQ1W3Fv+2TFOuEFW9optnDXDgkntPBIl6gact/LHsfBM5RKbM3dHsIIeLgl0Q==
dependencies:
resolve-package-path "^3.1.0"
semver "^7.3.4"
silent-error "^1.1.1"
DEV: Don't lint core files when target == plugins (#10259) * DEV: Don't lint core files when target == plugins * Prettier the plugin/*.js files * Update eslintignore/prettierignore * Add eslint-plugin-ember and eslint-plugin-node * Properly lint all js files in all plugins * LINT: run prettier on test/*.js files * DEV: Run prettier checks on test/*.js files * ESLint plugins' assets/javascripts and test/javascripts directories only
2020-08-25 05:40:40 -04:00
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
ember-rfc176-data@^0.3.15, ember-rfc176-data@^0.3.17:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "0.3.18"
resolved "https://registry.yarnpkg.com/ember-rfc176-data/-/ember-rfc176-data-0.3.18.tgz#bb6fdcef49999981317ea81b6cc9210fb4108d65"
integrity sha512-JtuLoYGSjay1W3MQAxt3eINWXNYYQliK90tLwtb8aeCuQK8zKGCRbBodVIrkcTqshULMnRuTOS6t1P7oQk3g6Q==
ember-template-imports@^3.4.1, ember-template-imports@^3.4.2:
version "3.4.2"
resolved "https://registry.yarnpkg.com/ember-template-imports/-/ember-template-imports-3.4.2.tgz#6cf7de7d4b8348a0fddf3aaec4947aa1211289e6"
integrity sha512-OS8TUVG2kQYYwP3netunLVfeijPoOKIs1SvPQRTNOQX4Pu8xGGBEZmrv0U1YTnQn12Eg+p6w/0UdGbUnITjyzw==
dependencies:
babel-import-util "^0.2.0"
broccoli-stew "^3.0.0"
ember-cli-babel-plugin-helpers "^1.1.1"
ember-cli-version-checker "^5.1.2"
line-column "^1.0.2"
magic-string "^0.25.7"
parse-static-imports "^1.1.0"
string.prototype.matchall "^4.0.6"
validate-peer-dependencies "^1.1.0"
DEV: Don't lint core files when target == plugins (#10259) * DEV: Don't lint core files when target == plugins * Prettier the plugin/*.js files * Update eslintignore/prettierignore * Add eslint-plugin-ember and eslint-plugin-node * Properly lint all js files in all plugins * LINT: run prettier on test/*.js files * DEV: Run prettier checks on test/*.js files * ESLint plugins' assets/javascripts and test/javascripts directories only
2020-08-25 05:40:40 -04:00
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
ember-template-lint@^5.11.2:
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
version "5.11.2"
resolved "https://registry.yarnpkg.com/ember-template-lint/-/ember-template-lint-5.11.2.tgz#dd7cf15000444fcc8899d907e8d911cd77c31fc0"
integrity sha512-G8KXmFCYLKM9ifMb+rluL8CNIawUl45i4z4VrK+Nn5ciWSo+Vx2jUp+sS6wKCdBqGYoiqjUgn/hmGnCVOId+yQ==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
dependencies:
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
"@lint-todo/utils" "^13.1.1"
aria-query "^5.3.0"
chalk "^5.3.0"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
ci-info "^3.8.0"
date-fns "^2.30.0"
ember-template-imports "^3.4.2"
ember-template-recast "^6.1.4"
eslint-formatter-kakoune "^1.0.0"
find-up "^6.3.0"
fuse.js "^6.5.3"
get-stdin "^9.0.0"
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
globby "^13.2.2"
DEV: Update sub-dependencies (#22325) Achieved by running `yarn upgrade --latest` both yarn.lock directories, then reverting changes to package.json files and running `yarn` again. I also de-duped yarn.lock files with `npx yarn-deduplicate && yarn`
2023-06-29 11:08:33 -04:00
is-glob "^4.0.3"
language-tags "^1.0.8"
micromatch "^4.0.5"
resolve "^1.22.3"
v8-compile-cache "^2.3.0"
yargs "^17.7.2"
DEV: Update ember-template-lint (#22242)
2023-06-22 16:54:46 -04:00
ember-template-recast@^6.1.4:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "6.1.4"
resolved "https://registry.yarnpkg.com/ember-template-recast/-/ember-template-recast-6.1.4.tgz#e964c184adfd876878009f8aa0b84c95633fce20"
integrity sha512-fCh+rOK6z+/tsdkTbOE+e7f84P6ObnIRQrCCrnu21E4X05hPeradikIkRMhJdxn4NWrxitfZskQDd37TR/lsNQ==
dependencies:
"@glimmer/reference" "^0.84.3"
"@glimmer/syntax" "^0.84.3"
"@glimmer/validator" "^0.84.3"
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
async-promise-queue "^1.0.5"
colors "^1.4.0"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
commander "^8.3.0"
globby "^11.0.3"
ora "^5.4.0"
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
slash "^3.0.0"
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
tmp "^0.2.1"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
workerpool "^6.4.0"
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
emoji-regex@^8.0.0:
version "8.0.0"
resolved "https://registry.yarnpkg.com/emoji-regex/-/emoji-regex-8.0.0.tgz#e818fd69ce5ccfcb404594f842963bf53164cc37"
integrity sha512-MSjYzcWNOA0ewAHpz0MxpYFvwg6yjy1NG3xteoqz644VCo/RPgnr1/GGt+ic3iJTzQ8Eu3TdM14SawnVUmGE6A==
Support for Ember Template linting
2020-02-05 11:33:15 -05:00
DEV: Bump `@mixer/parallel-prettier` (#19053)
2022-11-16 15:38:57 -05:00
end-of-stream@^1.1.0, end-of-stream@^1.4.1:
Update javascripts (#9907)
2020-05-28 12:15:13 -04:00
version "1.4.4"
resolved "https://registry.yarnpkg.com/end-of-stream/-/end-of-stream-1.4.4.tgz#5ae64a5f45057baf3626ec14da0ca5e4b2431eb0"
integrity sha512-+uw1inIHVPQoaVuHzRyXd21icM+cnt4CzD5rW+NC1wjOUSTOs+Te7FOv7AhN7vS9x/oIyhLP5PR1H+phQAHu5Q==
DEV: upgrades from Ember 2.13 to Ember 3.5.1 (#6808) Co-Authored-By: Bianca Nenciu <nbianca@users.noreply.github.com> Co-Authored-By: David Taylor <david@taylorhq.com>
2019-01-10 05:06:01 -05:00
dependencies:
once "^1.4.0"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
ensure-posix-path@^1.0.0, ensure-posix-path@^1.0.1, ensure-posix-path@^1.1.0:
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
version "1.1.1"
resolved "https://registry.yarnpkg.com/ensure-posix-path/-/ensure-posix-path-1.1.1.tgz#3c62bdb19fa4681544289edb2b382adc029179ce"
integrity sha512-VWU0/zXzVbeJNXvME/5EmLuEj2TauvoaTz6aFYK1Z92JCBlDlZ3Gu0tuGR42kpW1754ywTs+QB0g5TP0oj9Zaw==
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
entities@~2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/entities/-/entities-2.1.0.tgz#992d3129cf7df6870b96c57858c249a120f8b8b5"
integrity sha512-hCx1oky9PFrJ611mf0ifBLBRW8lUUVRlFolb5gWRfIELabBlbp9xZvrqZLZAs+NxFnbfQoeGd8wDkygjg7U85w==
DEV: introduces documentation for chat (#19772) Note this commit also slightly changes internal API: channel instead of getChannel and updateCurrentUserChannelNotificationsSettings instead of updateCurrentUserChatChannelNotificationsSettings. Also destroyChannel takes a second param which is the name confirmation instead of an optional object containing this confirmation. This is to enforce the fact that it's required. In the future a top level jsdoc config file could be used instead of the hack tempfile, but while it's only an experiment for chat, it's probably good enough.
2023-01-18 06:36:16 -05:00
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
errlop@^2.0.0:
version "2.2.0"
resolved "https://registry.yarnpkg.com/errlop/-/errlop-2.2.0.tgz#1ff383f8f917ae328bebb802d6ca69666a42d21b"
integrity sha512-e64Qj9+4aZzjzzFpZC7p5kmm/ccCrbLhAJplhsDXQFs87XTsXwOpH4s1Io2s90Tau/8r2j9f4l/thhDevRjzxw==
DEV: Consolidate and update jsconfig, and add types packages (#23824) These updates significantly improve IDE tooling for imports across the Discourse core codebase, and also for framework packages. The `@types/ember-*` packages are a temporary solution until we get onto Ember 5, which ships its types in the main package. The previous approach of having jsconfig files in each package directory did work, but once you start adding all the possible interlinks between them, we hit the file count limit of VSCode's tooling (because it counts every file for every jsconfig its referenced in). Having one file at the root means that a single file can apply to all core packages and plugins. Long-term, to get the same functionality for all themes/plugins, we may need to look at building/publishing a Discourse types package which can be added to theme/plugin package.json files for development purposes.
2023-10-18 07:13:20 -04:00
es-abstract@^1.22.1:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
version "1.22.2"
resolved "https://registry.yarnpkg.com/es-abstract/-/es-abstract-1.22.2.tgz#90f7282d91d0ad577f505e423e52d4c1d93c1b8a"
integrity sha512-YoxfFcDmhjOgWPWsV13+2RNjq1F6UQnfs+8TftwNqtzlmFzEXvlUwdrNrYeaizfjQzRMxkZ6ElWMOJIFKdVqwA==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
dependencies:
array-buffer-byte-length "^1.0.0"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
arraybuffer.prototype.slice "^1.0.2"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
available-typed-arrays "^1.0.5"
call-bind "^1.0.2"
es-set-tostringtag "^2.0.1"
es-to-primitive "^1.2.1"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
function.prototype.name "^1.1.6"
get-intrinsic "^1.2.1"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
get-symbol-description "^1.0.0"
globalthis "^1.0.3"
gopd "^1.0.1"
has "^1.0.3"
has-property-descriptors "^1.0.0"
has-proto "^1.0.1"
has-symbols "^1.0.3"
internal-slot "^1.0.5"
is-array-buffer "^3.0.2"
is-callable "^1.2.7"
is-negative-zero "^2.0.2"
is-regex "^1.1.4"
is-shared-array-buffer "^1.0.2"
is-string "^1.0.7"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
is-typed-array "^1.1.12"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
is-weakref "^1.0.2"
object-inspect "^1.12.3"
object-keys "^1.1.1"
object.assign "^4.1.4"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
regexp.prototype.flags "^1.5.1"
safe-array-concat "^1.0.1"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
safe-regex-test "^1.0.0"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
string.prototype.trim "^1.2.8"
string.prototype.trimend "^1.0.7"
string.prototype.trimstart "^1.0.7"
typed-array-buffer "^1.0.0"
typed-array-byte-length "^1.0.0"
typed-array-byte-offset "^1.0.0"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
typed-array-length "^1.0.4"
unbox-primitive "^1.0.2"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
which-typed-array "^1.1.11"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
es-set-tostringtag@^2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/es-set-tostringtag/-/es-set-tostringtag-2.0.1.tgz#338d502f6f674301d710b80c8592de8a15f09cd8"
integrity sha512-g3OMbtlwY3QewlqAiMLI47KywjWZoEytKr8pf6iTC8uJq5bIAH52Z9pnQ8pVL6whrCto53JZDuUIsifGeLorTg==
dependencies:
get-intrinsic "^1.1.3"
has "^1.0.3"
has-tostringtag "^1.0.0"
es-to-primitive@^1.2.1:
version "1.2.1"
resolved "https://registry.yarnpkg.com/es-to-primitive/-/es-to-primitive-1.2.1.tgz#e55cd4c9cdc188bcefb03b366c736323fc5c898a"
integrity sha512-QCOllgZJtaUo9miYBcLChTUaHNjJF3PYs1VidD7AwiEj1kYxKeQTctLAezAOH5ZKRH0g2IgPn6KwB4IT8iRpvA==
dependencies:
is-callable "^1.1.4"
is-date-object "^1.0.1"
is-symbol "^1.0.2"
DEV: Use esbuild to make DiscourseJsProcessor (#23223) Reverts e2705df and re-lands #23187 and #23219. The issue was incorrect order of execution of Rails' `assets:precompile` task in our own precompilation stack. Co-authored-by: David Taylor <david@taylorhq.com>
2023-08-24 10:36:22 -04:00
esbuild@^0.19.2:
version "0.19.2"
resolved "https://registry.yarnpkg.com/esbuild/-/esbuild-0.19.2.tgz#b1541828a89dfb6f840d38538767c6130dca2aac"
integrity sha512-G6hPax8UbFakEj3hWO0Vs52LQ8k3lnBhxZWomUJDxfz3rZTLqF5k/FCzuNdLx2RbpBiQQF9H9onlDDH1lZsnjg==
optionalDependencies:
"@esbuild/android-arm" "0.19.2"
"@esbuild/android-arm64" "0.19.2"
"@esbuild/android-x64" "0.19.2"
"@esbuild/darwin-arm64" "0.19.2"
"@esbuild/darwin-x64" "0.19.2"
"@esbuild/freebsd-arm64" "0.19.2"
"@esbuild/freebsd-x64" "0.19.2"
"@esbuild/linux-arm" "0.19.2"
"@esbuild/linux-arm64" "0.19.2"
"@esbuild/linux-ia32" "0.19.2"
"@esbuild/linux-loong64" "0.19.2"
"@esbuild/linux-mips64el" "0.19.2"
"@esbuild/linux-ppc64" "0.19.2"
"@esbuild/linux-riscv64" "0.19.2"
"@esbuild/linux-s390x" "0.19.2"
"@esbuild/linux-x64" "0.19.2"
"@esbuild/netbsd-x64" "0.19.2"
"@esbuild/openbsd-x64" "0.19.2"
"@esbuild/sunos-x64" "0.19.2"
"@esbuild/win32-arm64" "0.19.2"
"@esbuild/win32-ia32" "0.19.2"
"@esbuild/win32-x64" "0.19.2"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
escalade@^3.1.1:
version "3.1.1"
resolved "https://registry.yarnpkg.com/escalade/-/escalade-3.1.1.tgz#d8cfdc7000965c5a0174b4a82eaa5c0552742e40"
integrity sha512-k0er2gUkLf8O0zKJiAhmkTnJlTvINGv7ygDNPbeIsX/TJjGJZHuh9B2UxbsaEkmlEo9MfhrSzmhIlhRlI2GXnw==
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
escape-string-regexp@^1.0.5:
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
version "1.0.5"
resolved "https://registry.yarnpkg.com/escape-string-regexp/-/escape-string-regexp-1.0.5.tgz#1b61c0562190a8dff6ae3bb2cf0200ca130b86d4"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-vbRorB5FUQWvla16U8R/qgaFIya2qGzwDrNmCZuYKrbdSUMG6I1ZCGQRefkRVhuOkIGVne7BQ35DSfo1qvJqFg==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
DEV: introduces documentation for chat (#19772) Note this commit also slightly changes internal API: channel instead of getChannel and updateCurrentUserChannelNotificationsSettings instead of updateCurrentUserChatChannelNotificationsSettings. Also destroyChannel takes a second param which is the name confirmation instead of an optional object containing this confirmation. This is to enforce the fact that it's required. In the future a top level jsdoc config file could be used instead of the hack tempfile, but while it's only an experiment for chat, it's probably good enough.
2023-01-18 06:36:16 -05:00
escape-string-regexp@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/escape-string-regexp/-/escape-string-regexp-2.0.0.tgz#a30304e99daa32e23b2fd20f51babd07cffca344"
integrity sha512-UpzcLCXolUWcNu5HtVMHYdXJjArjsF9C0aNnquZYY4uW/Vu0miy5YoWvbV345HauVvcAUnpRuhMMcqTcGOY2+w==
FIX: Qunit tests were failing if your node was defaulting to IPV6 (#15773) This is now the default in newer node versions. The code that fails is a workaround for another error :'( This also upgrades `chrome-launcher` which helpers with debugging.
2022-02-02 10:56:03 -05:00
escape-string-regexp@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/escape-string-regexp/-/escape-string-regexp-4.0.0.tgz#14ba83a5d373e3d311e5afca29cf5bfad965bf34"
integrity sha512-TtpcNJ3XAzx3Gq8sWRzJaVajRs0uVxA2YAkdb1jm2YkPz4G6egUFAyA3n5vtEIZefPk5Wa4UXbKuS5fKkJWdgA==
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
escodegen@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/escodegen/-/escodegen-2.1.0.tgz#ba93bbb7a43986d29d6041f99f5262da773e2e17"
integrity sha512-2NlIDTwUWJN0mRPQOdtQBzbUHvdGY2P1VXSyU83Q3xKxM7WHX2Ql8dKq782Q9TgQUNOLEzEYu9bzLNj1q88I5w==
dependencies:
esprima "^4.0.1"
estraverse "^5.2.0"
esutils "^2.0.2"
optionalDependencies:
source-map "~0.6.1"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
eslint-formatter-kakoune@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/eslint-formatter-kakoune/-/eslint-formatter-kakoune-1.0.0.tgz#a95cc4fe1fbc06b84e0f2397e83f5f0b68340125"
integrity sha512-Uk/TVLt6Nf6Xoz7C1iYuZjOSdJxe5aaauGRke8JhKeJwD66Y61/pY2FjtLP04Ooq9PwV34bzrkKkU2UZ5FtDRA==
DEV: uses central eslint-config-discourse (#8150) * DEV: uses centrain eslint-config-discourse Discourse project or plugins can now have a central configuration by doing: `yarn add --dev eslint-config-discourse@latest` * adds postinstall script
2019-10-07 20:56:24 -04:00
DEV: Introduce decorator-position lint rule (#22937)
2023-08-04 07:26:06 -04:00
eslint-plugin-decorator-position@^5.0.2:
version "5.0.2"
resolved "https://registry.yarnpkg.com/eslint-plugin-decorator-position/-/eslint-plugin-decorator-position-5.0.2.tgz#c96f46d8ef0f7dbd519ff91a67ccc4b6ba30693b"
integrity sha512-wFcRfrB9zljOP1n5udg16h6ITX1jG8cnUvuFVtIqVxw5O9BTOXFHB9hvsTaqpb8JFX2dq19fH3i/ipUeFSF87w==
dependencies:
"@babel/core" "^7.18.6"
"@babel/plugin-proposal-decorators" "^7.18.6"
"@ember-data/rfc395-data" "^0.0.4"
ember-rfc176-data "^0.3.17"
snake-case "^3.0.4"
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
eslint-plugin-ember@^11.11.1:
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
version "11.11.1"
resolved "https://registry.yarnpkg.com/eslint-plugin-ember/-/eslint-plugin-ember-11.11.1.tgz#bc49d76ed8ec43e646d222f15181f4d18c3c3218"
integrity sha512-dvsDa4LkDkGqCE2bzBIguRMi1g40JVwRWMSHmn8S7toRDxSOU3M7yromgi5eSAJX2O2vEvJZ9QnR15YDbvNfVQ==
DEV: Update sub-dependencies (#22325) Achieved by running `yarn upgrade --latest` both yarn.lock directories, then reverting changes to package.json files and running `yarn` again. I also de-duped yarn.lock files with `npx yarn-deduplicate && yarn`
2023-06-29 11:08:33 -04:00
dependencies:
"@ember-data/rfc395-data" "^0.0.4"
"@glimmer/syntax" "^0.84.2"
css-tree "^2.0.4"
ember-rfc176-data "^0.3.15"
ember-template-imports "^3.4.2"
ember-template-recast "^6.1.4"
eslint-utils "^3.0.0"
estraverse "^5.2.0"
lodash.camelcase "^4.1.1"
lodash.kebabcase "^4.1.1"
magic-string "^0.30.0"
requireindex "^1.2.0"
snake-case "^3.0.3"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
eslint-plugin-simple-import-sort@^10.0.0:
version "10.0.0"
resolved "https://registry.yarnpkg.com/eslint-plugin-simple-import-sort/-/eslint-plugin-simple-import-sort-10.0.0.tgz#cc4ceaa81ba73252427062705b64321946f61351"
integrity sha512-AeTvO9UCMSNzIHRkg8S6c3RPy5YEwKWSQPx3DYghLedo2ZQxowPFLGDN1AZ2evfg6r6mjBSZSLxLFsWSu3acsw==
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
eslint-plugin-sort-class-members@^1.19.0:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
version "1.19.0"
resolved "https://registry.yarnpkg.com/eslint-plugin-sort-class-members/-/eslint-plugin-sort-class-members-1.19.0.tgz#9ad7a674c4cb477fceaddb8162515372d381c733"
integrity sha512-YayvASA1bavdPeRU9FMPnale2+Oi3aMcHGVC5EUm9b671oxm7ahvR+q8BfsU2aV+KAFezNfu47VPgdZK6gwYPw==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
eslint-scope@5.1.1:
DEV: specify eslint-config-discourse version instead of using latest (#10721) This make it easy for users to be on latest when they pull an update.
2020-09-22 10:58:01 -04:00
version "5.1.1"
resolved "https://registry.yarnpkg.com/eslint-scope/-/eslint-scope-5.1.1.tgz#e786e59a66cb92b3f6c1fb0d508aab174848f48c"
integrity sha512-2NxwbF/hZ0KpepYN0cNbo+FN6XoK7GaHlQhgx/hIZl6Va0bF45RQOOwhLIy8lQDbuCiadSLCBnH2CFYquit5bw==
Upgrade to FontAwesome 5 (take two) (#6673) * Add missing icons to set * Revert FA5 revert This reverts commit 42572ff * use new SVG syntax in locales * Noscript page changes (remove login button, center "powered by" footer text) * Cast wider net for SVG icons in settings - include any _icon setting for SVG registry (offers better support for plugin settings) - let themes store multiple pipe-delimited icons in a setting - also replaces broken onebox image icon with SVG reference in cooked post processor * interpolate icons in locales * Fix composer whisper icon alignment * Add support for stacked icons * SECURITY: enforce hostname to match discourse hostname This ensures that the hostname rails uses for various helpers always matches the Discourse hostname * load SVG sprite with pre-initializers * FIX: enable caching on SVG sprites * PERF: use JSONP for SVG sprites so they are served from CDN This avoids needing to deal with CORS for loading of the SVG Note, added the svg- prefix to the filename so we can quickly tell in dev tools what the file is * Add missing SVG sprite JSONP script to CSP * Upgrade to FA 5.5.0 * Add support for all FA4.7 icons - adds complete frontend and backend for renamed FA4.7 icons - improves performance of SvgSprite.bundle and SvgSprite.all_icons * Fix group avatar flair preview - adds an endpoint at /svg-sprites/search/:keyword - adds frontend ajax call that pulls icon in avatar flair preview even when it is not in subset * Remove FA 4.7 font files
2018-11-26 16:49:57 -05:00
dependencies:
DEV: specify eslint-config-discourse version instead of using latest (#10721) This make it easy for users to be on latest when they pull an update.
2020-09-22 10:58:01 -04:00
esrecurse "^4.3.0"
Upgrade to FontAwesome 5 (take two) (#6673) * Add missing icons to set * Revert FA5 revert This reverts commit 42572ff * use new SVG syntax in locales * Noscript page changes (remove login button, center "powered by" footer text) * Cast wider net for SVG icons in settings - include any _icon setting for SVG registry (offers better support for plugin settings) - let themes store multiple pipe-delimited icons in a setting - also replaces broken onebox image icon with SVG reference in cooked post processor * interpolate icons in locales * Fix composer whisper icon alignment * Add support for stacked icons * SECURITY: enforce hostname to match discourse hostname This ensures that the hostname rails uses for various helpers always matches the Discourse hostname * load SVG sprite with pre-initializers * FIX: enable caching on SVG sprites * PERF: use JSONP for SVG sprites so they are served from CDN This avoids needing to deal with CORS for loading of the SVG Note, added the svg- prefix to the filename so we can quickly tell in dev tools what the file is * Add missing SVG sprite JSONP script to CSP * Upgrade to FA 5.5.0 * Add support for all FA4.7 icons - adds complete frontend and backend for renamed FA4.7 icons - improves performance of SvgSprite.bundle and SvgSprite.all_icons * Fix group avatar flair preview - adds an endpoint at /svg-sprites/search/:keyword - adds frontend ajax call that pulls icon in avatar flair preview even when it is not in subset * Remove FA 4.7 font files
2018-11-26 16:49:57 -05:00
estraverse "^4.1.1"
DEV: Consolidate and update jsconfig, and add types packages (#23824) These updates significantly improve IDE tooling for imports across the Discourse core codebase, and also for framework packages. The `@types/ember-*` packages are a temporary solution until we get onto Ember 5, which ships its types in the main package. The previous approach of having jsconfig files in each package directory did work, but once you start adding all the possible interlinks between them, we hit the file count limit of VSCode's tooling (because it counts every file for every jsconfig its referenced in). Having one file at the root means that a single file can apply to all core packages and plugins. Long-term, to get the same functionality for all themes/plugins, we may need to look at building/publishing a Discourse types package which can be added to theme/plugin package.json files for development purposes.
2023-10-18 07:13:20 -04:00
eslint-scope@^7.2.2:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
version "7.2.2"
resolved "https://registry.yarnpkg.com/eslint-scope/-/eslint-scope-7.2.2.tgz#deb4f92563390f32006894af62a22dba1c46423f"
integrity sha512-dOt21O7lTMhDM+X9mB4GX+DZrZtCUJPL/wlcTqxyrx5IvO0IYtILdtrQGQp+8n5S0gwSVmOf9NQrjMOgfQZlIg==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
dependencies:
esrecurse "^4.3.0"
estraverse "^5.2.0"
eslint-utils@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/eslint-utils/-/eslint-utils-3.0.0.tgz#8aebaface7345bb33559db0a1f13a1d2d48c3672"
integrity sha512-uuQC43IGctw68pJA1RgbQS8/NP7rch6Cwd4j3ZBtgo4/8Flj4eGE7ZYSZRN3iq5pVUv6GPdW5Z1RFleo84uLDA==
dependencies:
eslint-visitor-keys "^2.0.0"
eslint-visitor-keys@^2.0.0, eslint-visitor-keys@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/eslint-visitor-keys/-/eslint-visitor-keys-2.1.0.tgz#f65328259305927392c938ed44eb0a5c9b2bd303"
integrity sha512-0rSmRBzXgDzIsD6mGdJgevzgezI534Cer5L/vyMX0kHzT/jiB43jRhd9YUlMGYLQy2zprNmoT8qasCGtY+QaKw==
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
eslint-visitor-keys@^3.3.0, eslint-visitor-keys@^3.4.1, eslint-visitor-keys@^3.4.3:
version "3.4.3"
resolved "https://registry.yarnpkg.com/eslint-visitor-keys/-/eslint-visitor-keys-3.4.3.tgz#0cd72fe8550e3c2eae156a96a4dddcd1c8ac5800"
integrity sha512-wpc+LXeiyiisxPlEkUzU6svyS1frIO3Mgxj1fdy7Pm8Ygzguax2N3Fa/D/ag1WqbOprdI+uY6wMUl8/a2G+iag==
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
eslint@^8.51.0:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
version "8.51.0"
resolved "https://registry.yarnpkg.com/eslint/-/eslint-8.51.0.tgz#4a82dae60d209ac89a5cff1604fea978ba4950f3"
integrity sha512-2WuxRZBrlwnXi+/vFSJyjMqrNjtJqiasMzehF0shoLaW7DzS3/9Yvrmq5JiT66+pNjiX4UBnLDiKHcWAr/OInA==
dependencies:
"@eslint-community/eslint-utils" "^4.2.0"
"@eslint-community/regexpp" "^4.6.1"
"@eslint/eslintrc" "^2.1.2"
"@eslint/js" "8.51.0"
"@humanwhocodes/config-array" "^0.11.11"
"@humanwhocodes/module-importer" "^1.0.1"
"@nodelib/fs.walk" "^1.2.8"
ajv "^6.12.4"
chalk "^4.0.0"
cross-spawn "^7.0.2"
debug "^4.3.2"
doctrine "^3.0.0"
escape-string-regexp "^4.0.0"
eslint-scope "^7.2.2"
eslint-visitor-keys "^3.4.3"
espree "^9.6.1"
esquery "^1.4.2"
esutils "^2.0.2"
fast-deep-equal "^3.1.3"
file-entry-cache "^6.0.1"
find-up "^5.0.0"
glob-parent "^6.0.2"
globals "^13.19.0"
graphemer "^1.4.0"
ignore "^5.2.0"
imurmurhash "^0.1.4"
is-glob "^4.0.0"
is-path-inside "^3.0.3"
js-yaml "^4.1.0"
json-stable-stringify-without-jsonify "^1.0.1"
levn "^0.4.1"
lodash.merge "^4.6.2"
minimatch "^3.1.2"
natural-compare "^1.4.0"
optionator "^0.9.3"
strip-ansi "^6.0.1"
text-table "^0.2.0"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
esm@^3.2.25:
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
version "3.2.25"
resolved "https://registry.yarnpkg.com/esm/-/esm-3.2.25.tgz#342c18c29d56157688ba5ce31f8431fbb795cc10"
integrity sha512-U1suiZ2oDVWv4zPO56S0NcR5QriEahGtdN2OR6FiOG4WJvcjBVFB0qI4+eKoWFH483PKGuLuu6V8Z4T5g63UVA==
DEV: Consolidate and update jsconfig, and add types packages (#23824) These updates significantly improve IDE tooling for imports across the Discourse core codebase, and also for framework packages. The `@types/ember-*` packages are a temporary solution until we get onto Ember 5, which ships its types in the main package. The previous approach of having jsconfig files in each package directory did work, but once you start adding all the possible interlinks between them, we hit the file count limit of VSCode's tooling (because it counts every file for every jsconfig its referenced in). Having one file at the root means that a single file can apply to all core packages and plugins. Long-term, to get the same functionality for all themes/plugins, we may need to look at building/publishing a Discourse types package which can be added to theme/plugin package.json files for development purposes.
2023-10-18 07:13:20 -04:00
espree@^9.6.0, espree@^9.6.1:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
version "9.6.1"
resolved "https://registry.yarnpkg.com/espree/-/espree-9.6.1.tgz#a2a17b8e434690a5432f2f8018ce71d331a48c6f"
integrity sha512-oruZaFkjorTpF32kDSI5/75ViwGeZginGGy2NoOSg3Q9bnwlnmDm4HLnkl0RE3n+njDXR037aY1+x58Z/zFdwQ==
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
dependencies:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
acorn "^8.9.0"
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
acorn-jsx "^5.3.2"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
eslint-visitor-keys "^3.4.1"
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
esprima@^4.0.1:
version "4.0.1"
resolved "https://registry.yarnpkg.com/esprima/-/esprima-4.0.1.tgz#13b04cdb3e6c5d19df91ab6987a8695619b0aa71"
integrity sha512-eGuFFw7Upda+g4p+QHvnW0RyTX/SVeJBDM/gCtMARO0cLuT2HcEKnTPvhjV6aGeqrCB/sbNop0Kszm0jsaWU4A==
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
esquery@^1.4.2:
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
version "1.5.0"
resolved "https://registry.yarnpkg.com/esquery/-/esquery-1.5.0.tgz#6ce17738de8577694edd7361c57182ac8cb0db0b"
integrity sha512-YQLXUplAwJgCydQ78IMJywZCceoqk1oH01OERdSAJc/7U2AylwjhSCLDEtqwg811idIS/9fIU5GjG73IgjKMVg==
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
dependencies:
estraverse "^5.1.0"
DEV: specify eslint-config-discourse version instead of using latest (#10721) This make it easy for users to be on latest when they pull an update.
2020-09-22 10:58:01 -04:00
esrecurse@^4.3.0:
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
version "4.3.0"
resolved "https://registry.yarnpkg.com/esrecurse/-/esrecurse-4.3.0.tgz#7ad7964d679abb28bee72cec63758b1c5d2c9921"
integrity sha512-KmfKL3b6G+RXvP8N1vr3Tq1kL/oCFgn2NYXEtqP8/L3pKapUA4G8cFVaoF3SU323CD4XypR/ffioHmkti6/Tag==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
dependencies:
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
estraverse "^5.2.0"
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
estraverse@^4.1.1:
DEV: uses central eslint-config-discourse (#8150) * DEV: uses centrain eslint-config-discourse Discourse project or plugins can now have a central configuration by doing: `yarn add --dev eslint-config-discourse@latest` * adds postinstall script
2019-10-07 20:56:24 -04:00
version "4.3.0"
resolved "https://registry.yarnpkg.com/estraverse/-/estraverse-4.3.0.tgz#398ad3f3c5a24948be7725e83d11a7de28cdbd1d"
integrity sha512-39nnKffWz8xN1BU/2c79n9nB9HDzo0niYUqx6xyqUnyoAnQyyWpOTdZEeiCch8BBu515t4wp9ZmgVfVhn9EBpw==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
estraverse@^5.1.0, estraverse@^5.2.0:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "5.3.0"
resolved "https://registry.yarnpkg.com/estraverse/-/estraverse-5.3.0.tgz#2eea5290702f26ab8fe5370370ff86c965d21123"
integrity sha512-MMdARuVEQziNTeJD8DgMqmhwR11BRQ/cBP+pLtYdSTnf3MIO8fFeiINEbX36ZdNlfU/7A9f3gUw49B3oQsvwBA==
Update javascripts (#9907)
2020-05-28 12:15:13 -04:00
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
esutils@^2.0.2:
DEV: uses central eslint-config-discourse (#8150) * DEV: uses centrain eslint-config-discourse Discourse project or plugins can now have a central configuration by doing: `yarn add --dev eslint-config-discourse@latest` * adds postinstall script
2019-10-07 20:56:24 -04:00
version "2.0.3"
resolved "https://registry.yarnpkg.com/esutils/-/esutils-2.0.3.tgz#74d2eb4de0b8da1293711910d50775b9b710ef64"
integrity sha512-kVscqXk4OCp68SZ0dkgEKVi6/8ij300KBWTJq32P/dYeWTSwK41WyTxalN1eRmA5Z9UU/LX9D7FWSmV9SAYx6g==
DEV: Bump `@mixer/parallel-prettier` (#19053)
2022-11-16 15:38:57 -05:00
extend@^3.0.2:
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
version "3.0.2"
resolved "https://registry.yarnpkg.com/extend/-/extend-3.0.2.tgz#f8b1136b4071fbd8eb140aff858b1019ec2915fa"
integrity sha512-fjquC59cD7CyW6urNXK0FBufkZcoiGG80wTuPujX590cB5Ttln20E2UB4S/WARVqhXffZl2LNgS+gQdPIIim/g==
DEV: Switch from puppeteer to puppeteer-core for smoke test (#15262) `puppeteer` includes a full chromium binary, which adds more than 300mb to our node_modules directory in development/test mode (and therefore the `discourse_dev` and `discourse_test` docker images). We already reach out to the system copy of Chrome for our qunit tests, and already have chrome installed in our `discourse_dev`/`discourse_test` docker images, so it's much more efficient to switch to `puppeteer-core` which doesn't include the chromium binary.
2021-12-13 04:31:49 -05:00
extract-zip@2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/extract-zip/-/extract-zip-2.0.1.tgz#663dca56fe46df890d5f131ef4a06d22bb8ba13a"
integrity sha512-GDhU9ntwuKyGXdZBUgTIe+vXnWj0fppUEtMDL0+idd5Sta8TGpHssn/eusA9mrPr9qNDym6SxAYZjNvCn/9RBg==
Add smoke test script that runs in chrome headless.
2017-12-18 03:32:58 -05:00
dependencies:
DEV: Switch from puppeteer to puppeteer-core for smoke test (#15262) `puppeteer` includes a full chromium binary, which adds more than 300mb to our node_modules directory in development/test mode (and therefore the `discourse_dev` and `discourse_test` docker images). We already reach out to the system copy of Chrome for our qunit tests, and already have chrome installed in our `discourse_dev`/`discourse_test` docker images, so it's much more efficient to switch to `puppeteer-core` which doesn't include the chromium binary.
2021-12-13 04:31:49 -05:00
debug "^4.1.1"
get-stream "^5.1.0"
Update javascripts (#9907)
2020-05-28 12:15:13 -04:00
yauzl "^2.10.0"
DEV: Switch from puppeteer to puppeteer-core for smoke test (#15262) `puppeteer` includes a full chromium binary, which adds more than 300mb to our node_modules directory in development/test mode (and therefore the `discourse_dev` and `discourse_test` docker images). We already reach out to the system copy of Chrome for our qunit tests, and already have chrome installed in our `discourse_dev`/`discourse_test` docker images, so it's much more efficient to switch to `puppeteer-core` which doesn't include the chromium binary.
2021-12-13 04:31:49 -05:00
optionalDependencies:
"@types/yauzl" "^2.9.1"
Add smoke test script that runs in chrome headless.
2017-12-18 03:32:58 -05:00
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
fast-deep-equal@^3.1.1, fast-deep-equal@^3.1.3:
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
version "3.1.3"
resolved "https://registry.yarnpkg.com/fast-deep-equal/-/fast-deep-equal-3.1.3.tgz#3a7d56b559d6cbc3eb512325244e619a65c6c525"
integrity sha512-f3qQ9oQy9j2AhBe/H9VC91wLmKBCCU/gDOnKNAYG5hswO7BLKj09Hc5HYNz9cGI++xlpDCIgDaitVs03ATR84Q==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
fast-fifo@^1.1.0, fast-fifo@^1.2.0:
Revert "DEV: FloatKit (#23541)" (#23549) This reverts commits 0623ac684a65f95ce4f5438ff47944b1dc2119f4 408e71e437ef8abf98f93e3449898bf906766b0e a32fa3b9470dde0543fcee809f2abd1f219f7336 User tips were running into some issues.
2023-09-12 13:55:12 -04:00
version "1.3.0"
resolved "https://registry.yarnpkg.com/fast-fifo/-/fast-fifo-1.3.0.tgz#03e381bcbfb29932d7c3afde6e15e83e05ab4d8b"
integrity sha512-IgfweLvEpwyA4WgiQe9Nx6VV2QkML2NkvZnk1oKnIzXgXdWxuhF7zw4DvLTPZJn6PIUneiAXPF24QmoEqHTjyw==
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
fast-glob@^3.2.9, fast-glob@^3.3.0:
version "3.3.1"
resolved "https://registry.yarnpkg.com/fast-glob/-/fast-glob-3.3.1.tgz#784b4e897340f3dbbef17413b3f11acf03c874c4"
integrity sha512-kNFPyjhh5cKjrUltxs+wFx+ZkbRaxxmZ+X0ZU31SOsxCEtP9VPgtq2teZw1DebupL5GmDaNQ6yKMMVcM41iqDg==
Support for Ember Template linting
2020-02-05 11:33:15 -05:00
dependencies:
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
"@nodelib/fs.stat" "^2.0.2"
"@nodelib/fs.walk" "^1.2.3"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
glob-parent "^5.1.2"
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
merge2 "^1.3.0"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
micromatch "^4.0.4"
Support for Ember Template linting
2020-02-05 11:33:15 -05:00
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
fast-json-stable-stringify@^2.0.0:
Update javascripts (#9907)
2020-05-28 12:15:13 -04:00
version "2.1.0"
resolved "https://registry.yarnpkg.com/fast-json-stable-stringify/-/fast-json-stable-stringify-2.1.0.tgz#874bf69c6f404c2b5d99c481341399fd55892633"
integrity sha512-lhd/wF+Lk98HZoTCtlVraHtfh5XYijIjalXck7saUtuanSDyLMxnHhSXEDJqHxD7msR8D0uCmqlkwjCV8xvwHw==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
fast-levenshtein@^2.0.6:
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
version "2.0.6"
resolved "https://registry.yarnpkg.com/fast-levenshtein/-/fast-levenshtein-2.0.6.tgz#3d8a5c66883a16a30ca8643e851f19baa7797917"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
integrity sha512-DCXu6Ifhqcks7TZKY3Hxp3y6qphY5SJZmrWMDrKcERSOXWQdMhU9Ig/PYrzyw/ul9jOIyh0N4M0tbC5hodg8dw==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
fast-ordered-set@^1.0.0:
version "1.0.3"
resolved "https://registry.yarnpkg.com/fast-ordered-set/-/fast-ordered-set-1.0.3.tgz#3fbb36634f7be79e4f7edbdb4a357dee25d184eb"
integrity sha512-MxBW4URybFszOx1YlACEoK52P6lE3xiFcPaGCUZ7QQOZ6uJXKo++Se8wa31SjcZ+NC/fdAWX7UtKEfaGgHS2Vg==
dependencies:
blank-object "^1.0.1"
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
fastq@^1.6.0:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "1.15.0"
resolved "https://registry.yarnpkg.com/fastq/-/fastq-1.15.0.tgz#d04d07c6a2a68fe4599fea8d2e103a937fae6b3a"
integrity sha512-wBrocU2LCXXa+lWBt8RoIRD89Fi8OdABODa/kEnyeyjS5aZO5/GNvI5sEINADqP/h8M29UHTHUb53sUu5Ihqdw==
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
dependencies:
reusify "^1.0.4"
Update javascripts (#9907)
2020-05-28 12:15:13 -04:00
fd-slicer@~1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/fd-slicer/-/fd-slicer-1.1.0.tgz#25c7c89cb1f9077f8891bbe61d8f390eae256f1e"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-cE1qsB/VwyQozZ+q1dGxR8LBYNZeofhEdUNGSMbQD3Gw2lAzX9Zb3uIU6Ebc/Fmyjo9AWWfnn0AUCHqtevs/8g==
Add smoke test script that runs in chrome headless.
2017-12-18 03:32:58 -05:00
dependencies:
pend "~1.2.0"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
file-entry-cache@^6.0.1:
version "6.0.1"
resolved "https://registry.yarnpkg.com/file-entry-cache/-/file-entry-cache-6.0.1.tgz#211b2dd9659cb0394b073e7323ac3c933d522027"
integrity sha512-7Gps/XWymbLk2QLYK4NzpMOrYjMhdIxXuIvy2QBsLE6ljuodKvdkWs/cpyJJ3CVIVpH0Oi1Hvg1ovbMzLdFBBg==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
dependencies:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
flat-cache "^3.0.4"
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
fill-range@^7.0.1:
version "7.0.1"
resolved "https://registry.yarnpkg.com/fill-range/-/fill-range-7.0.1.tgz#1919a6a7c75fe38b2c7c77e5198535da9acdda40"
integrity sha512-qOo9F+dMUmC2Lcb4BbVvnKJxTPjCm+RRpe4gDuGrzkL7mEVl/djYSu2OdQ2Pa302N4oqkSg9ir6jaLWJ2USVpQ==
dependencies:
to-regex-range "^5.0.1"
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
find-up@^5.0.0:
version "5.0.0"
resolved "https://registry.yarnpkg.com/find-up/-/find-up-5.0.0.tgz#4c92819ecb7083561e4f4a240a86be5198f536fc"
integrity sha512-78/PXT1wlLLDgTzDs7sjq9hzz0vXD+zn+7wypEe4fXQxCmdmqfGsEPQxmiCSQI3ajFV91bVSsvNtrJRiW6nGng==
dependencies:
locate-path "^6.0.0"
path-exists "^4.0.0"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
find-up@^6.3.0:
version "6.3.0"
resolved "https://registry.yarnpkg.com/find-up/-/find-up-6.3.0.tgz#2abab3d3280b2dc7ac10199ef324c4e002c8c790"
integrity sha512-v2ZsoEuVHYy8ZIlYqwPe/39Cy+cFDzp4dXPaxNvkEuouymu+2Jbz0PxpKarJHYJTmv2HWT3O382qY8l4jMWthw==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
dependencies:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
locate-path "^7.1.0"
path-exists "^5.0.0"
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
flat-cache@^3.0.4:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
version "3.1.1"
resolved "https://registry.yarnpkg.com/flat-cache/-/flat-cache-3.1.1.tgz#a02a15fdec25a8f844ff7cc658f03dd99eb4609b"
integrity sha512-/qM2b3LUIaIgviBQovTLvijfyOQXPtSRnRK26ksj2J7rzPIecePUIpJsZ4T02Qg+xiAEKIs5K8dsHEd+VaKa/Q==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
dependencies:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
flatted "^3.2.9"
keyv "^4.5.3"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
rimraf "^3.0.2"
DEV: Merge package.json files (#21172) This means: a single yarn.lock and removing one of the package.json files
2023-04-20 06:46:12 -04:00
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
flatted@^3.2.9:
version "3.2.9"
resolved "https://registry.yarnpkg.com/flatted/-/flatted-3.2.9.tgz#7eb4c67ca1ba34232ca9d2d93e9886e611ad7daf"
integrity sha512-36yxDn5H7OFZQla0/jFJmbIKTdZAQHngCedGxiMmpNfEZM0sdEeT+WczLQrjK6D7o2aiyLYDnkw0R3JK0Qv1RQ==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
for-each@^0.3.3:
version "0.3.3"
resolved "https://registry.yarnpkg.com/for-each/-/for-each-0.3.3.tgz#69b447e88a0a5d32c3e7084f3f1710034b21376e"
integrity sha512-jqYfLp7mo9vIyQf8ykW2v7A+2N4QjeCeI5+Dz9XraiO1ign81wjiH7Fb9vSOWvQfNtmSa4H2RoQTrrXivdUZmw==
dependencies:
is-callable "^1.1.3"
DEV: Merge package.json files (#21172) This means: a single yarn.lock and removing one of the package.json files
2023-04-20 06:46:12 -04:00
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
fs-extra@^7.0.1:
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
version "7.0.1"
resolved "https://registry.yarnpkg.com/fs-extra/-/fs-extra-7.0.1.tgz#4f189c44aa123b895f722804f55ea23eadc348e9"
integrity sha512-YJDaCJZEnBmcbw13fvdAM9AwNOJwOzrE4pqMqBq5nFiEqXUqHwlK4B+3pUw6JNvfSPtX05xFHtYy/1ni01eGCw==
dependencies:
graceful-fs "^4.1.2"
jsonfile "^4.0.0"
universalify "^0.1.0"
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
fs-extra@^8.0.1, fs-extra@^8.1.0:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "8.1.0"
resolved "https://registry.yarnpkg.com/fs-extra/-/fs-extra-8.1.0.tgz#49d43c45a88cd9677668cb7be1b46efdb8d2e1c0"
integrity sha512-yhlQgA6mnOJUKOsRUFsgJdQCvkKhcz8tlZG5HBQfReYZy46OwLcY+Zia0mtdHsOo9y/hP+CxMN0TU9QxoOtG4g==
dependencies:
graceful-fs "^4.2.0"
jsonfile "^4.0.0"
universalify "^0.1.0"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
fs-extra@^9.1.0:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
version "9.1.0"
resolved "https://registry.yarnpkg.com/fs-extra/-/fs-extra-9.1.0.tgz#5954460c764a8da2094ba3554bf839e6b9a7c86d"
integrity sha512-hcg3ZmepS30/7BSFqRvoo3DOMQu7IjqxO5nCDt+zM9XWjb33Wg7ziNT+Qvqbuc3+gWpzO02JubVyk2G4Zvo1OQ==
dependencies:
at-least-node "^1.0.0"
graceful-fs "^4.2.0"
jsonfile "^6.0.1"
universalify "^2.0.0"
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
fs-merger@^3.2.1:
version "3.2.1"
resolved "https://registry.yarnpkg.com/fs-merger/-/fs-merger-3.2.1.tgz#a225b11ae530426138294b8fbb19e82e3d4e0b3b"
integrity sha512-AN6sX12liy0JE7C2evclwoo0aCG3PFulLjrTLsJpWh/2mM+DinhpSGqYLbHBBbIW1PLRNcFhJG8Axtz8mQW3ug==
dependencies:
broccoli-node-api "^1.7.0"
broccoli-node-info "^2.1.0"
fs-extra "^8.0.1"
fs-tree-diff "^2.0.1"
walk-sync "^2.2.0"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
fs-tree-diff@^0.5.2, fs-tree-diff@^0.5.3, fs-tree-diff@^0.5.6:
version "0.5.9"
resolved "https://registry.yarnpkg.com/fs-tree-diff/-/fs-tree-diff-0.5.9.tgz#a4ec6182c2f5bd80b9b83c8e23e4522e6f5fd946"
integrity sha512-872G8ax0kHh01m9n/2KDzgYwouKza0Ad9iFltBpNykvROvf2AGtoOzPJgGx125aolGPER3JuC7uZFrQ7bG1AZw==
dependencies:
heimdalljs-logger "^0.1.7"
object-assign "^4.1.0"
path-posix "^1.0.0"
symlink-or-copy "^1.1.8"
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
fs-tree-diff@^2.0.0, fs-tree-diff@^2.0.1:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "2.0.1"
resolved "https://registry.yarnpkg.com/fs-tree-diff/-/fs-tree-diff-2.0.1.tgz#343e4745ab435ec39ebac5f9059ad919cd034afa"
integrity sha512-x+CfAZ/lJHQqwlD64pYM5QxWjzWhSjroaVsr8PW831zOApL55qPibed0c+xebaLWVr2BnHFoHdrwOv8pzt8R5A==
dependencies:
"@types/symlink-or-copy" "^1.2.0"
heimdalljs-logger "^0.1.7"
object-assign "^4.1.0"
path-posix "^1.0.0"
symlink-or-copy "^1.1.8"
fs-updater@^1.0.4:
version "1.0.4"
resolved "https://registry.yarnpkg.com/fs-updater/-/fs-updater-1.0.4.tgz#2329980f99ae9176e9a0e84f7637538a182ce63b"
integrity sha512-0pJX4mJF/qLsNEwTct8CdnnRdagfb+LmjRPJ8sO+nCnAZLW0cTmz4rTgU25n+RvTuWSITiLKrGVJceJPBIPlKg==
dependencies:
can-symlink "^1.0.0"
clean-up-path "^1.0.0"
heimdalljs "^0.2.5"
heimdalljs-logger "^0.1.9"
rimraf "^2.6.2"
Run JS test in chrome headless on Travis.
2017-12-14 21:15:04 -05:00
fs.realpath@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/fs.realpath/-/fs.realpath-1.0.0.tgz#1504ad2523158caa40db4a2787cb01411994ea4f"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-OO0pH2lK6a0hZnAdau5ItzHPI6pUlvI7jMVnxUQRtw4owF2wk8lOSabtGDCTP4Ggrg2MbGnWO9X8K1t4+fGMDw==
Run JS test in chrome headless on Travis.
2017-12-14 21:15:04 -05:00
DEV: Add uppy.js to build and project (#13645) This PR adds uppy to the project with a custom JS build and the shims needed to import it into our JS code. We need a custom build of Uppy because we do not use webpack for our JS modules/build. The only way to get what you want from Uppy is to use the webpack modules or to include the entire Uppy project including all plugins in a single JS file. This way we can just use the plugins we actually want. Future PRs will actually use Uppy!
2021-07-06 20:39:33 -04:00
function-bind@^1.1.1:
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
version "1.1.2"
resolved "https://registry.yarnpkg.com/function-bind/-/function-bind-1.1.2.tgz#2c02d864d97f3ea6c8830c464cbd11ab6eab7a1c"
integrity sha512-7XHNxH7qX9xG5mIwxkhumTox/MIRNcOgDrxWsMt2pAr23WHp6MrRlN7FBSFpCpr+oVO0F744iUgR82nJMfG2SA==
DEV: Add uppy.js to build and project (#13645) This PR adds uppy to the project with a custom JS build and the shims needed to import it into our JS code. We need a custom build of Uppy because we do not use webpack for our JS modules/build. The only way to get what you want from Uppy is to use the webpack modules or to include the entire Uppy project including all plugins in a single JS file. This way we can just use the plugins we actually want. Future PRs will actually use Uppy!
2021-07-06 20:39:33 -04:00
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
function.prototype.name@^1.1.6:
version "1.1.6"
resolved "https://registry.yarnpkg.com/function.prototype.name/-/function.prototype.name-1.1.6.tgz#cdf315b7d90ee77a4c6ee216c3c3362da07533fd"
integrity sha512-Z5kx79swU5P27WEayXM1tBi5Ze/lbIyiNgU3qyXUOf9b2rgXYyF9Dy9Cx+IQv/Lc8WCG6L82zwUPpSS9hGehIg==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
dependencies:
call-bind "^1.0.2"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
define-properties "^1.2.0"
es-abstract "^1.22.1"
functions-have-names "^1.2.3"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
functions-have-names@^1.2.3:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "1.2.3"
resolved "https://registry.yarnpkg.com/functions-have-names/-/functions-have-names-1.2.3.tgz#0404fe4ee2ba2f607f0e0ec3c80bae994133b834"
integrity sha512-xckBUXyTIqT97tq2x2AMb+g163b5JFysYk0x4qxNFwbfQkmNZoiRHb6sPzI9/QV33WeuvVYBUIiD4NzNIyqaRQ==
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
fuse.js@^6.5.3:
version "6.6.2"
resolved "https://registry.yarnpkg.com/fuse.js/-/fuse.js-6.6.2.tgz#fe463fed4b98c0226ac3da2856a415576dc9a111"
integrity sha512-cJaJkxCCxC8qIIcPBF9yGxY0W/tVZS3uEISDxhYIdtk8OL93pe+6Zj7LjCqVV4dzbqcriOZ+kQ/NE4RXZHsIGA==
gensync@^1.0.0-beta.2:
version "1.0.0-beta.2"
resolved "https://registry.yarnpkg.com/gensync/-/gensync-1.0.0-beta.2.tgz#32a6ee76c3d7f52d46b2b1ae5d93fea8580a25e0"
integrity sha512-3hN7NaskYvMDLQY55gnW3NQ+mesEAepTqlg+VEbj7zzqEMBVNhzcGYYeqFo/TlYz6eQiFcp1HcsCZO+nGgS8zg==
get-caller-file@^2.0.5:
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
version "2.0.5"
resolved "https://registry.yarnpkg.com/get-caller-file/-/get-caller-file-2.0.5.tgz#4f94412a82db32f36e3b0b9741f8a97feb031f7e"
integrity sha512-DyFP3BM/3YHTQOCUL/w0OZHR0lpKeGrxotcHWcqNEdnltqFwXVfhEBQ94eIo34AfQpo0rGki4cyIiftY06h2Fg==
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
get-func-name@^2.0.0:
Build(deps): Bump get-func-name from 2.0.0 to 2.0.2 (#23697) Bumps [get-func-name](https://github.com/chaijs/get-func-name) from 2.0.0 to 2.0.2. - [Release notes](https://github.com/chaijs/get-func-name/releases) - [Commits](https://github.com/chaijs/get-func-name/commits/v2.0.2) --- updated-dependencies: - dependency-name: get-func-name dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-09-28 05:53:07 -04:00
version "2.0.2"
resolved "https://registry.yarnpkg.com/get-func-name/-/get-func-name-2.0.2.tgz#0d7cf20cd13fda808669ffa88f4ffc7a3943fc41"
integrity sha512-8vXOvuE167CtIc3OyItco7N/dpRtBbYOsPsXCz7X/PMnlGjYjSGuZJgM1Y7mmew7BKf9BqvLX2tnOVy1BBUsxQ==
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
get-intrinsic@^1.0.2, get-intrinsic@^1.1.1, get-intrinsic@^1.1.3, get-intrinsic@^1.2.0, get-intrinsic@^1.2.1:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "1.2.1"
resolved "https://registry.yarnpkg.com/get-intrinsic/-/get-intrinsic-1.2.1.tgz#d295644fed4505fc9cde952c37ee12b477a83d82"
integrity sha512-2DcsyfABl+gVHEfCOaTrWgyt+tb6MSEGmKq+kI5HwLbIYgjgmMcV8KQ41uaKz1xxUcn9tJtgFbQUEVcEbd0FYw==
dependencies:
function-bind "^1.1.1"
has "^1.0.3"
has-proto "^1.0.1"
has-symbols "^1.0.3"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
get-stdin@^9.0.0:
version "9.0.0"
resolved "https://registry.yarnpkg.com/get-stdin/-/get-stdin-9.0.0.tgz#3983ff82e03d56f1b2ea0d3e60325f39d703a575"
integrity sha512-dVKBjfWisLAicarI2Sf+JuBE/DghV4UzNAVe9yhEJuzeREd3JhOTE9cUaJTeSa77fsbQUK3pcOpJfM59+VKZaA==
Update javascripts (#9907)
2020-05-28 12:15:13 -04:00
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
get-stream@^5.1.0:
DEV: Switch from puppeteer to puppeteer-core for smoke test (#15262) `puppeteer` includes a full chromium binary, which adds more than 300mb to our node_modules directory in development/test mode (and therefore the `discourse_dev` and `discourse_test` docker images). We already reach out to the system copy of Chrome for our qunit tests, and already have chrome installed in our `discourse_dev`/`discourse_test` docker images, so it's much more efficient to switch to `puppeteer-core` which doesn't include the chromium binary.
2021-12-13 04:31:49 -05:00
version "5.2.0"
resolved "https://registry.yarnpkg.com/get-stream/-/get-stream-5.2.0.tgz#4966a1795ee5ace65e706c4b7beb71257d6e22d3"
integrity sha512-nBF+F1rAZVCu/p7rjzgA+Yb4lfYXrpl7a6VmJrU8wF9I1CKvP/QwPNZHnOlwbTkY6dvtFIzFMSyQXbLoTQPRpA==
dependencies:
pump "^3.0.0"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
get-symbol-description@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/get-symbol-description/-/get-symbol-description-1.0.0.tgz#7fdb81c900101fbd564dd5f1a30af5aadc1e58d6"
integrity sha512-2EmdH1YvIQiZpltCNgkuiUnyukzxM/R6NDJX31Ke3BG1Nq5b0S2PhX59UKi9vZpPDQVdqn+1IcaAwnzTT5vCjw==
dependencies:
call-bind "^1.0.2"
get-intrinsic "^1.1.1"
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
get-uri@^6.0.1:
version "6.0.1"
resolved "https://registry.yarnpkg.com/get-uri/-/get-uri-6.0.1.tgz#cff2ba8d456c3513a04b70c45de4dbcca5b1527c"
integrity sha512-7ZqONUVqaabogsYNWlYj0t3YZaL6dhuEueZXGF+/YVmf6dHmaFg8/6psJKqhx9QykIDKzpGcy2cn4oV4YC7V/Q==
dependencies:
basic-ftp "^5.0.2"
data-uri-to-buffer "^5.0.1"
debug "^4.3.4"
fs-extra "^8.1.0"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
glob-parent@^5.1.2:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
version "5.1.2"
resolved "https://registry.yarnpkg.com/glob-parent/-/glob-parent-5.1.2.tgz#869832c58034fe68a4093c17dc15e8340d8401c4"
integrity sha512-AOIgSQCepiJYwP3ARnGx+5VnTu2HBYdzbGP45eLw1vr3zB3vZLeyed1sC9hnbcOc9/SrMyM5RPQrkGz4aS9Zow==
Support for Ember Template linting
2020-02-05 11:33:15 -05:00
dependencies:
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
is-glob "^4.0.1"
Support for Ember Template linting
2020-02-05 11:33:15 -05:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
glob-parent@^6.0.2:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
version "6.0.2"
resolved "https://registry.yarnpkg.com/glob-parent/-/glob-parent-6.0.2.tgz#6d237d99083950c79290f24c7642a3de9a28f9e3"
integrity sha512-XxwI8EOhVQgWp6iDL+3b0r86f4d6AX6zSU55HfB4ydCEuXLXc5FcYeOu+nnGftS4TEju/11rt4KJPTMgbfmv4A==
dependencies:
is-glob "^4.0.3"
DEV: Bump `@mixer/parallel-prettier` (#19053)
2022-11-16 15:38:57 -05:00
glob-stream@^7.0.0:
version "7.0.0"
resolved "https://registry.yarnpkg.com/glob-stream/-/glob-stream-7.0.0.tgz#1c42227d5c0bc1aba20f36ee9b09cef7f194dc00"
integrity sha512-evR4kvr6s0Yo5t4CD4H171n4T8XcnPFznvsbeN8K9FPzc0Q0wYqcOWyGtck2qcvJSLXKnU6DnDyfmbDDabYvRQ==
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
dependencies:
DEV: Bump `@mixer/parallel-prettier` (#19053)
2022-11-16 15:38:57 -05:00
extend "^3.0.2"
glob "^7.2.0"
glob-parent "^6.0.2"
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
is-negated-glob "^1.0.0"
DEV: Bump `@mixer/parallel-prettier` (#19053)
2022-11-16 15:38:57 -05:00
ordered-read-streams "^1.0.1"
pumpify "^2.0.1"
readable-stream "^3.6.0"
remove-trailing-separator "^1.1.0"
to-absolute-glob "^2.0.2"
unique-stream "^2.3.1"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
glob@^5.0.10:
version "5.0.15"
resolved "https://registry.yarnpkg.com/glob/-/glob-5.0.15.tgz#1bc936b9e02f4a603fcc222ecf7633d30b8b93b1"
integrity sha512-c9IPMazfRITpmAAKi22dK1VKxGDX9ehhqfABDriL/lzO92xcUKEJPQHrVA/2YHSNFB4iFlykVmWvwo48nr3OxA==
dependencies:
inflight "^1.0.4"
inherits "2"
minimatch "2 || 3"
once "^1.3.0"
path-is-absolute "^1.0.0"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
glob@^7.1.3, glob@^7.2.0:
DEV: Bump `@mixer/parallel-prettier` (#19053)
2022-11-16 15:38:57 -05:00
version "7.2.3"
resolved "https://registry.yarnpkg.com/glob/-/glob-7.2.3.tgz#b8df0fb802bbfa8e89bd1d938b4e16578ed44f2b"
integrity sha512-nFR0zLpU2YCaRxwoCJvL6UvCH2JFyFVIvwTLsIf21AuHlMskA1hhTdk+LlYJtOlYt9v6dvszD2BGRqBL+iQK9Q==
DEV: Add uppy.js to build and project (#13645) This PR adds uppy to the project with a custom JS build and the shims needed to import it into our JS code. We need a custom build of Uppy because we do not use webpack for our JS modules/build. The only way to get what you want from Uppy is to use the webpack modules or to include the entire Uppy project including all plugins in a single JS file. This way we can just use the plugins we actually want. Future PRs will actually use Uppy!
2021-07-06 20:39:33 -04:00
dependencies:
fs.realpath "^1.0.0"
inflight "^1.0.4"
inherits "2"
DEV: Bump `@mixer/parallel-prettier` (#19053)
2022-11-16 15:38:57 -05:00
minimatch "^3.1.1"
DEV: Add uppy.js to build and project (#13645) This PR adds uppy to the project with a custom JS build and the shims needed to import it into our JS code. We need a custom build of Uppy because we do not use webpack for our JS modules/build. The only way to get what you want from Uppy is to use the webpack modules or to include the entire Uppy project including all plugins in a single JS file. This way we can just use the plugins we actually want. Future PRs will actually use Uppy!
2021-07-06 20:39:33 -04:00
once "^1.3.0"
path-is-absolute "^1.0.0"
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
globals@^11.1.0:
DEV: uses central eslint-config-discourse (#8150) * DEV: uses centrain eslint-config-discourse Discourse project or plugins can now have a central configuration by doing: `yarn add --dev eslint-config-discourse@latest` * adds postinstall script
2019-10-07 20:56:24 -04:00
version "11.12.0"
resolved "https://registry.yarnpkg.com/globals/-/globals-11.12.0.tgz#ab8795338868a0babd8525758018c2a7eb95c42e"
integrity sha512-WOBp/EEGUiIsJSp7wcv/y6MO+lV9UoncWqxuFfm8eBwzWNgyfBd6Gz+IeKQ9jCmyhoH99g15M3T+QaVHFjizVA==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
globals@^13.19.0, globals@^13.23.0:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
version "13.23.0"
resolved "https://registry.yarnpkg.com/globals/-/globals-13.23.0.tgz#ef31673c926a0976e1f61dab4dca57e0c0a8af02"
integrity sha512-XAmF0RjlrjY23MA51q3HltdlGxUpXPvg0GioKiD9X6HD28iMjo2dKC8Vqwm7lne4GNr78+RHTfliktR6ZH09wA==
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
dependencies:
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
type-fest "^0.20.2"
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
globalthis@^1.0.3:
version "1.0.3"
resolved "https://registry.yarnpkg.com/globalthis/-/globalthis-1.0.3.tgz#5852882a52b80dc301b0660273e1ed082f0b6ccf"
integrity sha512-sFdI5LyBiNTHjRd7cGPWapiHWMOXKyuBNX/cWJ3NfzrZQVa8GI/8cofCl74AOVqq9W5kNmguTIzJ/1s2gyI9wA==
dependencies:
define-properties "^1.1.3"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
globby@^11.0.3:
version "11.1.0"
resolved "https://registry.yarnpkg.com/globby/-/globby-11.1.0.tgz#bd4be98bb042f83d796f7e3811991fbe82a0d34b"
integrity sha512-jhIXaOzy1sb8IyocaruWSn1TjmnBVs8Ayhcy83rmxNJ8q2uWKCAj3CnJY+KpGSXCueAPc0i05kVvVKtP1t9S3g==
Support for Ember Template linting
2020-02-05 11:33:15 -05:00
dependencies:
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
array-union "^2.1.0"
dir-glob "^3.0.1"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
fast-glob "^3.2.9"
ignore "^5.2.0"
merge2 "^1.4.1"
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
slash "^3.0.0"
Support for Ember Template linting
2020-02-05 11:33:15 -05:00
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
globby@^13.2.2:
version "13.2.2"
resolved "https://registry.yarnpkg.com/globby/-/globby-13.2.2.tgz#63b90b1bf68619c2135475cbd4e71e66aa090592"
integrity sha512-Y1zNGV+pzQdh7H39l9zgB4PJqjRNqydvdYCDG4HFXM4XuvSaQQlEc91IU1yALL8gUTDomgBAfz3XJdmUS+oo0w==
Support for Ember Template linting
2020-02-05 11:33:15 -05:00
dependencies:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
dir-glob "^3.0.1"
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
fast-glob "^3.3.0"
ignore "^5.2.4"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
merge2 "^1.4.1"
slash "^4.0.0"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
gopd@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/gopd/-/gopd-1.0.1.tgz#29ff76de69dac7489b7c0918a5788e56477c332c"
integrity sha512-d65bNlIadxvpb/A2abVdlqKqV563juRnZ1Wtk6s1sIR8uNsXR70xqIzVqxVf1eTqDunwT2MkczEeaezCKTZhwA==
dependencies:
get-intrinsic "^1.1.3"
graceful-fs@^4.1.2, graceful-fs@^4.1.6, graceful-fs@^4.1.9, graceful-fs@^4.2.0, graceful-fs@^4.2.4:
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
version "4.2.11"
resolved "https://registry.yarnpkg.com/graceful-fs/-/graceful-fs-4.2.11.tgz#4183e4e8bf08bb6e05bbb2f7d2e0c8f712ca40e3"
integrity sha512-RbJ5/jmFcNNCcDV5o9eTnBLJ/HszWV0P73bc+Ff4nS/rJj+YaS6IGyiOL0VoBYX+l1Wrl3k63h/KrH+nhJ0XvQ==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
graphemer@^1.4.0:
version "1.4.0"
resolved "https://registry.yarnpkg.com/graphemer/-/graphemer-1.4.0.tgz#fb2f1d55e0e3a1849aeffc90c4fa0dd53a0e66c6"
integrity sha512-EtKwoO6kxCL9WO5xipiHTZlSzBm7WLT627TqC/uVRd0HKmq8NXyebnNYxDoBi7wt8eTWrUrKXCOVaFq9x1kgag==
Support for Ember Template linting
2020-02-05 11:33:15 -05:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
has-bigints@^1.0.1, has-bigints@^1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/has-bigints/-/has-bigints-1.0.2.tgz#0871bd3e3d51626f6ca0966668ba35d5602d6eaa"
integrity sha512-tSvCKtBr9lkF0Ex0aQiP9N+OpV4zi2r/Nee5VkRDbaqv35RLYMzbwQfFSZZH0kR+Rd6302UJZ2p/bJCEoR3VoQ==
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
use yarn to manage test vendor dependencies, upgrade sinon to v6.3.5
2018-10-04 11:06:14 -04:00
has-flag@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/has-flag/-/has-flag-3.0.0.tgz#b5d454dc2199ae225699f3467e5a07f3b955bafd"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-sKJf1+ceQBr4SMkvQnBDNDtf4TXpVhVGateu0t918bl30FnbE2m4vNLX+VWe/dpjlb+HugGYzW7uQXH98HPEYw==
use yarn to manage test vendor dependencies, upgrade sinon to v6.3.5
2018-10-04 11:06:14 -04:00
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
has-flag@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/has-flag/-/has-flag-4.0.0.tgz#944771fd9c81c81265c4d6941860da06bb59479b"
integrity sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
has-property-descriptors@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/has-property-descriptors/-/has-property-descriptors-1.0.0.tgz#610708600606d36961ed04c196193b6a607fa861"
integrity sha512-62DVLZGoiEBDHQyqG4w9xCuZ7eJEwNmJRWw2VY84Oedb7WFcA27fiEVe8oUQx9hAUJ4ekurquucTGwsyO1XGdQ==
dependencies:
get-intrinsic "^1.1.1"
has-proto@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/has-proto/-/has-proto-1.0.1.tgz#1885c1305538958aff469fef37937c22795408e0"
integrity sha512-7qE+iP+O+bgF9clE5+UoBFzE65mlBiVj3tKCrlNQ0Ogwm0BjpT/gK4SlLYDMybDh5I3TCTKnPPa0oMG7JDYrhg==
has-symbols@^1.0.2, has-symbols@^1.0.3:
version "1.0.3"
resolved "https://registry.yarnpkg.com/has-symbols/-/has-symbols-1.0.3.tgz#bb7b2c4349251dce87b125f7bdf874aa7c8b39f8"
integrity sha512-l3LCuF6MgDNwTDKkdYGEihYjt5pRPbEg46rtlmnSPlUbgmB8LOIrKJbYYFBSbnPaJexMKtiPO8hmeRjRz2Td+A==
has-tostringtag@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/has-tostringtag/-/has-tostringtag-1.0.0.tgz#7e133818a7d394734f941e73c3d3f9291e658b25"
integrity sha512-kFjcSNhnlGV1kyoGk7OXKSawH5JOb/LzUc5w9B02hOTO0dfFRjbHQKvg1d6cf3HbeUmtU9VbbV3qzZ2Teh97WQ==
dependencies:
has-symbols "^1.0.2"
DEV: Remove unused legacy dependencies
2022-06-18 14:30:12 -04:00
has@^1.0.3:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
version "1.0.4"
resolved "https://registry.yarnpkg.com/has/-/has-1.0.4.tgz#2eb2860e000011dae4f1406a86fe80e530fb2ec6"
integrity sha512-qdSAmqLF6209RFj4VVItywPMbm3vWylknmB3nvNiUIs72xAimcM8nVYxYr7ncvZq5qzk9MKIZR8ijqD/1QuYjQ==
DEV: Add uppy.js to build and project (#13645) This PR adds uppy to the project with a custom JS build and the shims needed to import it into our JS code. We need a custom build of Uppy because we do not use webpack for our JS modules/build. The only way to get what you want from Uppy is to use the webpack modules or to include the entire Uppy project including all plugins in a single JS file. This way we can just use the plugins we actually want. Future PRs will actually use Uppy!
2021-07-06 20:39:33 -04:00
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
hash-for-dep@^1.5.0, hash-for-dep@^1.5.1:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "1.5.1"
resolved "https://registry.yarnpkg.com/hash-for-dep/-/hash-for-dep-1.5.1.tgz#497754b39bee2f1c4ade4521bfd2af0a7c1196e3"
integrity sha512-/dQ/A2cl7FBPI2pO0CANkvuuVi/IFS5oTyJ0PsOb6jW6WbVW1js5qJXMJTNbWHXBIPdFTWFbabjB+mE0d+gelw==
dependencies:
broccoli-kitchen-sink-helpers "^0.3.1"
heimdalljs "^0.2.3"
heimdalljs-logger "^0.1.7"
path-root "^0.1.1"
resolve "^1.10.0"
resolve-package-path "^1.0.11"
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
heimdalljs-logger@^0.1.10, heimdalljs-logger@^0.1.7, heimdalljs-logger@^0.1.9:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "0.1.10"
resolved "https://registry.yarnpkg.com/heimdalljs-logger/-/heimdalljs-logger-0.1.10.tgz#90cad58aabb1590a3c7e640ddc6a4cd3a43faaf7"
integrity sha512-pO++cJbhIufVI/fmB/u2Yty3KJD0TqNPecehFae0/eps0hkZ3b4Zc/PezUMOpYuHFQbA7FxHZxa305EhmjLj4g==
dependencies:
debug "^2.2.0"
heimdalljs "^0.2.6"
heimdalljs@^0.2.0, heimdalljs@^0.2.1, heimdalljs@^0.2.3, heimdalljs@^0.2.5, heimdalljs@^0.2.6:
version "0.2.6"
resolved "https://registry.yarnpkg.com/heimdalljs/-/heimdalljs-0.2.6.tgz#b0eebabc412813aeb9542f9cc622cb58dbdcd9fe"
integrity sha512-o9bd30+5vLBvBtzCPwwGqpry2+n0Hi6H1+qwt6y+0kwRHGGF8TFIhJPmnuM0xO97zaKrDZMwO/V56fAnn8m/tA==
dependencies:
rsvp "~3.2.1"
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
http-proxy-agent@^7.0.0:
version "7.0.0"
resolved "https://registry.yarnpkg.com/http-proxy-agent/-/http-proxy-agent-7.0.0.tgz#e9096c5afd071a3fce56e6252bb321583c124673"
integrity sha512-+ZT+iBxVUQ1asugqnD6oWoRiS25AkjNfG085dKJGtGxkdwLQrMKU5wJr2bOOFAXzKcTuqq+7fZlTMgG3SRfIYQ==
Add smoke test script that runs in chrome headless.
2017-12-18 03:32:58 -05:00
dependencies:
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
agent-base "^7.1.0"
debug "^4.3.4"
Revert "DEV: FloatKit (#23541)" (#23549) This reverts commits 0623ac684a65f95ce4f5438ff47944b1dc2119f4 408e71e437ef8abf98f93e3449898bf906766b0e a32fa3b9470dde0543fcee809f2abd1f219f7336 User tips were running into some issues.
2023-09-12 13:55:12 -04:00
https-proxy-agent@^7.0.0:
version "7.0.1"
resolved "https://registry.yarnpkg.com/https-proxy-agent/-/https-proxy-agent-7.0.1.tgz#0277e28f13a07d45c663633841e20a40aaafe0ab"
integrity sha512-Eun8zV0kcYS1g19r78osiQLEFIRspRUDd9tIfBCTBPBeMieF/EsJNL8VI3xOIdYRDEkjQnqOYPsZ2DsWsVsFwQ==
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
dependencies:
agent-base "^7.0.2"
DEV: Switch from puppeteer to puppeteer-core for smoke test (#15262) `puppeteer` includes a full chromium binary, which adds more than 300mb to our node_modules directory in development/test mode (and therefore the `discourse_dev` and `discourse_test` docker images). We already reach out to the system copy of Chrome for our qunit tests, and already have chrome installed in our `discourse_dev`/`discourse_test` docker images, so it's much more efficient to switch to `puppeteer-core` which doesn't include the chromium binary.
2021-12-13 04:31:49 -05:00
debug "4"
Add smoke test script that runs in chrome headless.
2017-12-18 03:32:58 -05:00
DEV: Remove unused legacy dependencies
2022-06-18 14:30:12 -04:00
ieee754@^1.1.13:
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
version "1.2.1"
resolved "https://registry.yarnpkg.com/ieee754/-/ieee754-1.2.1.tgz#8eb7a10a63fff25d15a57b001586d177d1b0d352"
integrity sha512-dcyqhDvX1C46lXZcVqCpK+FtMRQVdIMN6/Df5js2zouUsqG7I6sFxitIC+7KYK29KdXOLHdu9zL4sFnoVQnqaA==
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
ignore@^5.1.8, ignore@^5.2.0, ignore@^5.2.4:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "5.2.4"
resolved "https://registry.yarnpkg.com/ignore/-/ignore-5.2.4.tgz#a291c0c6178ff1b960befe47fcdec301674a6324"
integrity sha512-MAb38BcSbH0eHNBxn7ql2NH/kX33OkB3lZ1BNdh7ENeRChHTYsTvWrMubiIAMNS2llXEEgZ1MUOBtXChP3kaFQ==
DEV: Don't lint core files when target == plugins (#10259) * DEV: Don't lint core files when target == plugins * Prettier the plugin/*.js files * Update eslintignore/prettierignore * Add eslint-plugin-ember and eslint-plugin-node * Properly lint all js files in all plugins * LINT: run prettier on test/*.js files * DEV: Run prettier checks on test/*.js files * ESLint plugins' assets/javascripts and test/javascripts directories only
2020-08-25 05:40:40 -04:00
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
import-cwd@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/import-cwd/-/import-cwd-3.0.0.tgz#20845547718015126ea9b3676b7592fb8bd4cf92"
integrity sha512-4pnzH16plW+hgvRECbDWpQl3cqtvSofHWh44met7ESfZ8UZOWWddm8hEyDTqREJ9RbYHY8gi8DqmaelApoOGMg==
dependencies:
import-from "^3.0.0"
DEV: Consolidate and update jsconfig, and add types packages (#23824) These updates significantly improve IDE tooling for imports across the Discourse core codebase, and also for framework packages. The `@types/ember-*` packages are a temporary solution until we get onto Ember 5, which ships its types in the main package. The previous approach of having jsconfig files in each package directory did work, but once you start adding all the possible interlinks between them, we hit the file count limit of VSCode's tooling (because it counts every file for every jsconfig its referenced in). Having one file at the root means that a single file can apply to all core packages and plugins. Long-term, to get the same functionality for all themes/plugins, we may need to look at building/publishing a Discourse types package which can be added to theme/plugin package.json files for development purposes.
2023-10-18 07:13:20 -04:00
import-fresh@^3.2.1:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
version "3.3.0"
resolved "https://registry.yarnpkg.com/import-fresh/-/import-fresh-3.3.0.tgz#37162c25fcb9ebaa2e6e53d5b4d88ce17d9e0c2b"
integrity sha512-veYYhQa+D1QBKznvhUHxb8faxlrwUnxseDAbAp457E0wLNio2bOSKnjYDhMj+YiAq61xrMGhQk9iXVk5FzgQMw==
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
dependencies:
parent-module "^1.0.0"
resolve-from "^4.0.0"
Support for Ember Template linting
2020-02-05 11:33:15 -05:00
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
import-from@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/import-from/-/import-from-3.0.0.tgz#055cfec38cd5a27d8057ca51376d7d3bf0891966"
integrity sha512-CiuXOFFSzkU5x/CR0+z7T91Iht4CXgfCxVOFRhh2Zyhg5wOpWvvDLQUsWl+gcN+QscYBjez8hDCt85O7RLDttQ==
dependencies:
DEV: Merge package.json files (#21172) This means: a single yarn.lock and removing one of the package.json files
2023-04-20 06:46:12 -04:00
resolve-from "^5.0.0"
imurmurhash@^0.1.4:
version "0.1.4"
resolved "https://registry.yarnpkg.com/imurmurhash/-/imurmurhash-0.1.4.tgz#9218b9b2b928a238b13dc4fb6b6d576f231453ea"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-JmXMZ6wuvDmLiHEml9ykzqO6lwFbof0GG4IkcGaENdCRDDmMVnny7s5HsIgHCbaq0w2MyPhDqkhTUgS2LU2PHA==
DEV: Merge package.json files (#21172) This means: a single yarn.lock and removing one of the package.json files
2023-04-20 06:46:12 -04:00
inflight@^1.0.4:
version "1.0.6"
resolved "https://registry.yarnpkg.com/inflight/-/inflight-1.0.6.tgz#49bd6331d7d02d0c09bc910a1075ba8165b56df9"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-k92I/b08q4wvFscXCLvqfsHCrjrF7yiXsQuIVvVE7N82W3+aqpzuUdBbfhWcy/FZR3/4IgflMgKLOsvPDrGCJA==
DEV: Merge package.json files (#21172) This means: a single yarn.lock and removing one of the package.json files
2023-04-20 06:46:12 -04:00
dependencies:
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
once "^1.3.0"
wrappy "1"
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
inherits@2, inherits@^2.0.3, inherits@^2.0.4, inherits@~2.0.3:
version "2.0.4"
resolved "https://registry.yarnpkg.com/inherits/-/inherits-2.0.4.tgz#0fa2c64f932917c3433a0ded55363aae37416b7c"
integrity sha512-k/vGaX4/Yla3WzyMCvTQOXYeIHvqOKtnqBduzTHpzpQZzAskKMhZ2K+EnBiSM9zGSoIFeMpXKxa4dYeZIQqewQ==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
inherits@2.0.3:
version "2.0.3"
resolved "https://registry.yarnpkg.com/inherits/-/inherits-2.0.3.tgz#633c2c83e3da42a502f52466022480f4208261de"
integrity sha512-x00IRNXNy63jwGkJmzPigoySHbaqpNuzKbBOmzK+g2OdZpQ9w+sxCN+VSB3ja7IAge2OP2qpfxTjeNcyjmW1uw==
Run JS test in chrome headless on Travis.
2017-12-14 21:15:04 -05:00
DEV: Consolidate and update jsconfig, and add types packages (#23824) These updates significantly improve IDE tooling for imports across the Discourse core codebase, and also for framework packages. The `@types/ember-*` packages are a temporary solution until we get onto Ember 5, which ships its types in the main package. The previous approach of having jsconfig files in each package directory did work, but once you start adding all the possible interlinks between them, we hit the file count limit of VSCode's tooling (because it counts every file for every jsconfig its referenced in). Having one file at the root means that a single file can apply to all core packages and plugins. Long-term, to get the same functionality for all themes/plugins, we may need to look at building/publishing a Discourse types package which can be added to theme/plugin package.json files for development purposes.
2023-10-18 07:13:20 -04:00
internal-slot@^1.0.5:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "1.0.5"
resolved "https://registry.yarnpkg.com/internal-slot/-/internal-slot-1.0.5.tgz#f2a2ee21f668f8627a4667f309dc0f4fb6674986"
integrity sha512-Y+R5hJrzs52QCG2laLn4udYVnxsfny9CpOhNhUvk/SSSVyF6T27FzRbF0sroPidSu3X8oEAkOn2K804mjpt6UQ==
dependencies:
get-intrinsic "^1.2.0"
has "^1.0.3"
side-channel "^1.0.4"
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
ip@^1.1.8:
version "1.1.8"
resolved "https://registry.yarnpkg.com/ip/-/ip-1.1.8.tgz#ae05948f6b075435ed3307acce04629da8cdbf48"
integrity sha512-PuExPYUiu6qMBQb4l06ecm6T6ujzhmh+MeJcW9wa89PoAz5pvd4zPgN5WJV104mb6S2T1AwNIAaB70JNrLQWhg==
ip@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/ip/-/ip-2.0.0.tgz#4cf4ab182fee2314c75ede1276f8c80b479936da"
integrity sha512-WKa+XuLG1A1R0UWhl2+1XQSi+fZWMsYKffMZTTYsiZaUD8k2yDAj5atimTUD2TZkyCkNEeYE5NhFZmupOGtjYQ==
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
is-absolute@^1.0.0:
DEV: Merge package.json files (#21172) This means: a single yarn.lock and removing one of the package.json files
2023-04-20 06:46:12 -04:00
version "1.0.0"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
resolved "https://registry.yarnpkg.com/is-absolute/-/is-absolute-1.0.0.tgz#395e1ae84b11f26ad1795e73c17378e48a301576"
integrity sha512-dOWoqflvcydARa360Gvv18DZ/gRuHKi2NU/wU5X1ZFzdYfH29nkiNZsF3mp4OJ3H4yo9Mx8A/uAGNzpzPN3yBA==
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
dependencies:
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
is-relative "^1.0.0"
is-windows "^1.0.1"
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
is-array-buffer@^3.0.1, is-array-buffer@^3.0.2:
version "3.0.2"
resolved "https://registry.yarnpkg.com/is-array-buffer/-/is-array-buffer-3.0.2.tgz#f2653ced8412081638ecb0ebbd0c41c6e0aecbbe"
integrity sha512-y+FyyR/w8vfIRq4eQcM1EYgSTnmHXPqaF+IgzgraytCFq5Xh8lllDVmAZolPJiZttZLeFSINPYMaEJ7/vWUa1w==
dependencies:
call-bind "^1.0.2"
get-intrinsic "^1.2.0"
is-typed-array "^1.1.10"
is-bigint@^1.0.1:
version "1.0.4"
resolved "https://registry.yarnpkg.com/is-bigint/-/is-bigint-1.0.4.tgz#08147a1875bc2b32005d41ccd8291dffc6691df3"
integrity sha512-zB9CruMamjym81i2JZ3UMn54PKGsQzsJeo6xvN3HJJ4CAsQNB6iRutp2To77OfCNuoxspsIhzaPoO1zyCEhFOg==
dependencies:
has-bigints "^1.0.1"
is-boolean-object@^1.1.0:
version "1.1.2"
resolved "https://registry.yarnpkg.com/is-boolean-object/-/is-boolean-object-1.1.2.tgz#5c6dc200246dd9321ae4b885a114bb1f75f63719"
integrity sha512-gDYaKHJmnj4aWxyj6YHyXVpdQawtVLHU5cb+eztPGczf6cjuTdwve5ZIEfgXqH4e57An1D1AKf8CZ3kYrQRqYA==
dependencies:
call-bind "^1.0.2"
has-tostringtag "^1.0.0"
is-callable@^1.1.3, is-callable@^1.1.4, is-callable@^1.2.7:
version "1.2.7"
resolved "https://registry.yarnpkg.com/is-callable/-/is-callable-1.2.7.tgz#3bc2a85ea742d9e36205dcacdd72ca1fdc51b055"
integrity sha512-1BC0BVFhS/p0qtw6enp8e+8OD0UrK0oFLztSjNzhcKA3WDuJxxAPXzPuPtKkjEY9UUoEWlX/8fgKeu2S8i9JTA==
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
is-core-module@^2.13.0:
version "2.13.0"
resolved "https://registry.yarnpkg.com/is-core-module/-/is-core-module-2.13.0.tgz#bb52aa6e2cbd49a30c2ba68c42bf3435ba6072db"
integrity sha512-Z7dk6Qo8pOCp3l4tsX2C5ZVas4V+UxwQodwZhLopL91TX8UyyHEXafPcyoeeWuLrwzHcr3igO78wNLwHJHsMCQ==
DEV: Add uppy.js to build and project (#13645) This PR adds uppy to the project with a custom JS build and the shims needed to import it into our JS code. We need a custom build of Uppy because we do not use webpack for our JS modules/build. The only way to get what you want from Uppy is to use the webpack modules or to include the entire Uppy project including all plugins in a single JS file. This way we can just use the plugins we actually want. Future PRs will actually use Uppy!
2021-07-06 20:39:33 -04:00
dependencies:
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
has "^1.0.3"
DEV: Add uppy.js to build and project (#13645) This PR adds uppy to the project with a custom JS build and the shims needed to import it into our JS code. We need a custom build of Uppy because we do not use webpack for our JS modules/build. The only way to get what you want from Uppy is to use the webpack modules or to include the entire Uppy project including all plugins in a single JS file. This way we can just use the plugins we actually want. Future PRs will actually use Uppy!
2021-07-06 20:39:33 -04:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
is-date-object@^1.0.1:
version "1.0.5"
resolved "https://registry.yarnpkg.com/is-date-object/-/is-date-object-1.0.5.tgz#0841d5536e724c25597bf6ea62e1bd38298df31f"
integrity sha512-9YQaSxsAiSwcvS33MBk3wTCVnWK+HhF8VZR2jRxehM16QcVOdHqPn4VPHmRK4lSr38n9JriurInLcP90xsYNfQ==
dependencies:
has-tostringtag "^1.0.0"
Update javascripts (#9907)
2020-05-28 12:15:13 -04:00
is-docker@^2.0.0:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "2.2.1"
resolved "https://registry.yarnpkg.com/is-docker/-/is-docker-2.2.1.tgz#33eeabe23cfe86f14bde4408a02c0cfb853acdaa"
integrity sha512-F+i2BKsFrH66iaUFc0woD8sLy8getkwTwtOBjvs56Cx4CgJDeKQeqfz8wAYiSb8JOprWhHH5p77PbmYCvvUuXQ==
Update javascripts (#9907)
2020-05-28 12:15:13 -04:00
DEV: Bump `@mixer/parallel-prettier` (#19053)
2022-11-16 15:38:57 -05:00
is-extglob@^2.1.1:
Manage qunit via yarn.
2018-09-11 03:07:28 -04:00
version "2.1.1"
resolved "https://registry.yarnpkg.com/is-extglob/-/is-extglob-2.1.1.tgz#a88c02535791f02ed37c76a1b9ea9773c833f8c2"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-SbKbANkN603Vi4jEZv49LeVJMn4yGwsbzZworEoyEiutsN3nJYdbO36zfhGJ6QEDpOZIFkDtnq5JRxmvl3jsoQ==
Manage qunit via yarn.
2018-09-11 03:07:28 -04:00
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
is-fullwidth-code-point@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/is-fullwidth-code-point/-/is-fullwidth-code-point-3.0.0.tgz#f116f8064fe90b3f7844a38997c0b75051269f1d"
integrity sha512-zymm5+u+sCsSWyD9qNaejV3DFvhCKclKdizYaJUuHA83RLjb7nSuGnddCHGv0hk+KY7BMAlsWeK4Ueg6EV6XQg==
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
is-glob@^4.0.0, is-glob@^4.0.1, is-glob@^4.0.3:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
version "4.0.3"
resolved "https://registry.yarnpkg.com/is-glob/-/is-glob-4.0.3.tgz#64f61e42cbbb2eec2071a9dac0b28ba1e65d5084"
integrity sha512-xelSayHH36ZgE7ZWhli7pW34hNbNl8Ojv5KVmkJD4hBdD3th8Tfk9vYasLM+mXWOZhFkgZfxhLSnrwRr4elSSg==
Support for Ember Template linting
2020-02-05 11:33:15 -05:00
dependencies:
is-extglob "^2.1.1"
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
is-interactive@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/is-interactive/-/is-interactive-1.0.0.tgz#cea6e6ae5c870a7b0a0004070b7b587e0252912e"
integrity sha512-2HvIEKRoqS62guEC+qBjpvRubdX910WCMuJTZ+I9yvqKU2/12eSL549HMwtabb4oupdj2sMP50k+XJfB/8JE6w==
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
is-negated-glob@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/is-negated-glob/-/is-negated-glob-1.0.0.tgz#6910bca5da8c95e784b5751b976cf5a10fee36d2"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-czXVVn/QEmgvej1f50BZ648vUI+em0xqMq2Sn+QncCLN4zj1UAxlT+kw/6ggQTOaZPd1HqKQGEqbpQVtJucWug==
is-negative-zero@^2.0.2:
version "2.0.2"
resolved "https://registry.yarnpkg.com/is-negative-zero/-/is-negative-zero-2.0.2.tgz#7bf6f03a28003b8b3965de3ac26f664d765f3150"
integrity sha512-dqJvarLawXsFbNDeJW7zAz8ItJ9cd28YufuuFzh0G8pNHjJMnY08Dv7sYX2uF5UpQOwieAeOExEYAWWfu7ZZUA==
is-number-object@^1.0.4:
version "1.0.7"
resolved "https://registry.yarnpkg.com/is-number-object/-/is-number-object-1.0.7.tgz#59d50ada4c45251784e9904f5246c742f07a42fc"
integrity sha512-k1U0IRzLMo7ZlYIfzRu23Oh6MiIFasgpb9X76eqfFZAqwH44UI4KTBvBYIZ1dSL9ZzChTB9ShHfLkR4pdW5krQ==
dependencies:
has-tostringtag "^1.0.0"
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
is-number@^7.0.0:
version "7.0.0"
resolved "https://registry.yarnpkg.com/is-number/-/is-number-7.0.0.tgz#7535345b896734d5f80c4d06c50955527a14f12b"
integrity sha512-41Cifkg6e8TylSpdtTpeLVMqvSBEVzTttHvERD741+pnZ8ANv0004MRL43QKPDlK9cGvNp6NZWZUBlbGXYxxng==
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
is-path-inside@^3.0.3:
version "3.0.3"
resolved "https://registry.yarnpkg.com/is-path-inside/-/is-path-inside-3.0.3.tgz#d231362e53a07ff2b0e0ea7fed049161ffd16283"
integrity sha512-Fd4gABb+ycGAmKou8eMftCupSir5lRxqf4aD/vd0cD2qc4HL07OjCeuHMr8Ro4CoMaeCKDB0/ECBOVWjTwUvPQ==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
is-regex@^1.1.4:
version "1.1.4"
resolved "https://registry.yarnpkg.com/is-regex/-/is-regex-1.1.4.tgz#eef5663cd59fa4c0ae339505323df6854bb15958"
integrity sha512-kvRdxDsxZjhzUX07ZnLydzS1TU/TJlTUHHY4YLL87e37oUA49DfkLqgy+VjFocowy29cKvcSiu+kIv728jTTVg==
dependencies:
call-bind "^1.0.2"
has-tostringtag "^1.0.0"
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
is-relative@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/is-relative/-/is-relative-1.0.0.tgz#a1bb6935ce8c5dba1e8b9754b9b2dcc020e2260d"
integrity sha512-Kw/ReK0iqwKeu0MITLFuj0jbPAmEiOsIwyIXvvbfa6QfmN9pkD1M+8pdk7Rl/dTKbH34/XBFMbgD4iMJhLQbGA==
dependencies:
is-unc-path "^1.0.0"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
is-shared-array-buffer@^1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/is-shared-array-buffer/-/is-shared-array-buffer-1.0.2.tgz#8f259c573b60b6a32d4058a1a07430c0a7344c79"
integrity sha512-sqN2UDu1/0y6uvXyStCOzyhAjCSlHceFoMKJW8W9EU9cvic/QdsZ0kEU93HEy3IUEFZIiH/3w+AH/UQbPHNdhA==
dependencies:
call-bind "^1.0.2"
is-string@^1.0.5, is-string@^1.0.7:
version "1.0.7"
resolved "https://registry.yarnpkg.com/is-string/-/is-string-1.0.7.tgz#0dd12bf2006f255bb58f695110eff7491eebc0fd"
integrity sha512-tE2UXzivje6ofPW7l23cjDOMa09gb7xlAqG6jG5ej6uPV32TlWP3NKPigtaGeHNu9fohccRYvIiZMfOOnOYUtg==
dependencies:
has-tostringtag "^1.0.0"
is-symbol@^1.0.2, is-symbol@^1.0.3:
version "1.0.4"
resolved "https://registry.yarnpkg.com/is-symbol/-/is-symbol-1.0.4.tgz#a6dac93b635b063ca6872236de88910a57af139c"
integrity sha512-C/CPBqKWnvdcxqIARxyOh4v1UUEOCHpgDa0WYgpKDFMszcrPcffg5uhwSgPCLD2WWxmq6isisz87tzT01tuGhg==
dependencies:
has-symbols "^1.0.2"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
is-typed-array@^1.1.10, is-typed-array@^1.1.12, is-typed-array@^1.1.9:
version "1.1.12"
resolved "https://registry.yarnpkg.com/is-typed-array/-/is-typed-array-1.1.12.tgz#d0bab5686ef4a76f7a73097b95470ab199c57d4a"
integrity sha512-Z14TF2JNG8Lss5/HMqt0//T9JeHXttXy5pH/DBU4vi98ozO2btxzq9MwYDZYnKwU8nRsz/+GVFVRDq3DkVuSPg==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
dependencies:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
which-typed-array "^1.1.11"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
is-unc-path@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/is-unc-path/-/is-unc-path-1.0.0.tgz#d731e8898ed090a12c352ad2eaed5095ad322c9d"
integrity sha512-mrGpVd0fs7WWLfVsStvgF6iEJnbjDFZh9/emhRDcGWTduTfNHd9CHeUwH3gYIjdbwo4On6hunkztwOaAw0yllQ==
dependencies:
unc-path-regex "^0.1.2"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
is-unicode-supported@^0.1.0:
version "0.1.0"
resolved "https://registry.yarnpkg.com/is-unicode-supported/-/is-unicode-supported-0.1.0.tgz#3f26c76a809593b52bfa2ecb5710ed2779b522a7"
integrity sha512-knxG2q4UC3u8stRGyAVJCOdxFmv5DZiRcdlIaAQXAbSfJya+OhopNotLQrstBhququ4ZpuKbDc/8S6mgXgPFPw==
Update javascripts (#9907)
2020-05-28 12:15:13 -04:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
is-weakref@^1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/is-weakref/-/is-weakref-1.0.2.tgz#9529f383a9338205e89765e0392efc2f100f06f2"
integrity sha512-qctsuLZmIQ0+vSSMfoVvyFe2+GSEvnmZ2ezTup1SBse9+twCCeial6EEi3Nc2KFcf6+qz2FBPnjXsk8xhKSaPQ==
dependencies:
call-bind "^1.0.2"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
is-windows@^1.0.1:
Manage qunit via yarn.
2018-09-11 03:07:28 -04:00
version "1.0.2"
resolved "https://registry.yarnpkg.com/is-windows/-/is-windows-1.0.2.tgz#d1850eb9791ecd18e6182ce12a30f396634bb19d"
Update yarn.lock with integrity hashes This should prevent the stable version of yarn from rewriting the lock file all the time.
2018-10-04 05:21:13 -04:00
integrity sha512-eXK1UInq2bPmjyX6e3VHIzMLobc4J94i4AWn+Hpq3OU5KkrRC96OAcR3PRJ/pGu6m8TRnBHP9dkXQVsT/COVIA==
Manage qunit via yarn.
2018-09-11 03:07:28 -04:00
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
is-wsl@^2.2.0:
Update javascripts (#9907)
2020-05-28 12:15:13 -04:00
version "2.2.0"
resolved "https://registry.yarnpkg.com/is-wsl/-/is-wsl-2.2.0.tgz#74a4c76e77ca9fd3f932f290c17ea326cd157271"
integrity sha512-fKzAra0rGJUUBwGBgNkHZuToZcn+TtXHpeCgmkMJMMYx1sQDYaCSyjJBSCa2nH1DGm7s3n1oBnohoVTBaN7Lww==
dependencies:
is-docker "^2.0.0"
Run JS test in chrome headless on Travis.
2017-12-14 21:15:04 -05:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
isarray@1.0.0, isarray@^1.0.0, isarray@~1.0.0:
Add smoke test script that runs in chrome headless.
2017-12-18 03:32:58 -05:00
version "1.0.0"
resolved "https://registry.yarnpkg.com/isarray/-/isarray-1.0.0.tgz#bb935d48582cba168c06834957a54a3e07124f11"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-VLghIWNM6ELQzo7zwmcg0NmTVyWKYjvIeM83yjp0wRDTmUnrM678fQbcKBo6n2CJEF0szoG//ytg+TKla89ALQ==
Add smoke test script that runs in chrome headless.
2017-12-18 03:32:58 -05:00
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
isarray@^2.0.5:
version "2.0.5"
resolved "https://registry.yarnpkg.com/isarray/-/isarray-2.0.5.tgz#8af1e4c1221244cc62459faf38940d4e644a5723"
integrity sha512-xHjhDr3cNBK0BzdUJSPXZntQUx/mwMS5Rw4A7lPJ90XGAO6ISP/ePDNuo0vhqOZU+UD5JoodwCAAoZQd3FeAKw==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
isexe@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/isexe/-/isexe-2.0.0.tgz#e8fbf374dc556ff8947a10dcb0572d633f2cfa10"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-RHxMLp9lnKHGHRng9QFhRCMbYAcVpn69smSGcq3f36xjgVVWThj4qqLbTLlq7Ssj8B+fIQ1EuCEGI2lKsyQeIw==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
isobject@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/isobject/-/isobject-2.1.0.tgz#f065561096a3f1da2ef46272f815c840d87e0c89"
integrity sha512-+OUdGJlgjOBZDfxnDjYYG6zp487z0JGNQq3cYQYg5f5hKR+syHMsaztzGeml/4kGG55CSpKSpWTY+jYGgsHLgA==
dependencies:
isarray "1.0.0"
istextorbinary@2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/istextorbinary/-/istextorbinary-2.1.0.tgz#dbed2a6f51be2f7475b68f89465811141b758874"
integrity sha512-kT1g2zxZ5Tdabtpp9VSdOzW9lb6LXImyWbzbQeTxoRtHhurC9Ej9Wckngr2+uepPL09ky/mJHmN9jeJPML5t6A==
dependencies:
binaryextensions "1 || 2"
editions "^1.1.1"
textextensions "1 || 2"
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
istextorbinary@^2.5.1:
version "2.6.0"
resolved "https://registry.yarnpkg.com/istextorbinary/-/istextorbinary-2.6.0.tgz#60776315fb0fa3999add276c02c69557b9ca28ab"
integrity sha512-+XRlFseT8B3L9KyjxxLjfXSLMuErKDsd8DBNrsaxoViABMEZlOSCstwmw0qpoFX3+U6yWU1yhLudAe6/lETGGA==
dependencies:
binaryextensions "^2.1.2"
editions "^2.2.0"
textextensions "^2.5.0"
js-string-escape@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/js-string-escape/-/js-string-escape-1.0.1.tgz#e2625badbc0d67c7533e9edc1068c587ae4137ef"
integrity sha512-Smw4xcfIQ5LVjAOuJCvN/zIodzA/BBSsluuoSykP+lUvScIi4U6RJLfwHet5cxFnCswUjISV8oAXaqaJDY3chg==
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
js-tokens@^4.0.0:
Upgrade to FontAwesome 5 (take two) (#6673) * Add missing icons to set * Revert FA5 revert This reverts commit 42572ff * use new SVG syntax in locales * Noscript page changes (remove login button, center "powered by" footer text) * Cast wider net for SVG icons in settings - include any _icon setting for SVG registry (offers better support for plugin settings) - let themes store multiple pipe-delimited icons in a setting - also replaces broken onebox image icon with SVG reference in cooked post processor * interpolate icons in locales * Fix composer whisper icon alignment * Add support for stacked icons * SECURITY: enforce hostname to match discourse hostname This ensures that the hostname rails uses for various helpers always matches the Discourse hostname * load SVG sprite with pre-initializers * FIX: enable caching on SVG sprites * PERF: use JSONP for SVG sprites so they are served from CDN This avoids needing to deal with CORS for loading of the SVG Note, added the svg- prefix to the filename so we can quickly tell in dev tools what the file is * Add missing SVG sprite JSONP script to CSP * Upgrade to FA 5.5.0 * Add support for all FA4.7 icons - adds complete frontend and backend for renamed FA4.7 icons - improves performance of SvgSprite.bundle and SvgSprite.all_icons * Fix group avatar flair preview - adds an endpoint at /svg-sprites/search/:keyword - adds frontend ajax call that pulls icon in avatar flair preview even when it is not in subset * Remove FA 4.7 font files
2018-11-26 16:49:57 -05:00
version "4.0.0"
resolved "https://registry.yarnpkg.com/js-tokens/-/js-tokens-4.0.0.tgz#19203fb59991df98e3a287050d4647cdeaf32499"
integrity sha512-RdJUflcE3cUzKiMqQgsCu06FPu9UdIJO0beYbPhHN4k6apgJtifcoCtT9bcxOpYBtpD2kCM6Sbzg4CausW/PKQ==
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
js-yaml@^4.1.0:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
version "4.1.0"
resolved "https://registry.yarnpkg.com/js-yaml/-/js-yaml-4.1.0.tgz#c1fb65f8f5017901cdd2c951864ba18458a10602"
integrity sha512-wpxZs9NoxZaJESJGIZTyDEaYpl0FKSA+FB9aJiyemKhMwkxQg63h4T1KJgUGHpTqPDNRcmmYLugrRjJlBtWvRA==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
dependencies:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
argparse "^2.0.1"
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
DEV: introduces documentation for chat (#19772) Note this commit also slightly changes internal API: channel instead of getChannel and updateCurrentUserChannelNotificationsSettings instead of updateCurrentUserChatChannelNotificationsSettings. Also destroyChannel takes a second param which is the name confirmation instead of an optional object containing this confirmation. This is to enforce the fact that it's required. In the future a top level jsdoc config file could be used instead of the hack tempfile, but while it's only an experiment for chat, it's probably good enough.
2023-01-18 06:36:16 -05:00
js2xmlparser@^4.0.2:
version "4.0.2"
resolved "https://registry.yarnpkg.com/js2xmlparser/-/js2xmlparser-4.0.2.tgz#2a1fdf01e90585ef2ae872a01bc169c6a8d5e60a"
integrity sha512-6n4D8gLlLf1n5mNLQPRfViYzu9RATblzPEtm1SthMX1Pjao0r9YI9nw7ZIfRxQMERS87mcswrg+r/OYrPRX6jA==
dependencies:
xmlcreate "^2.0.4"
DEV: Chat service object initial implementation (#19814) This is a combined work of Martin Brennan, Loïc Guitaut, and Joffrey Jaffeux. --- This commit implements a base service object when working in chat. The documentation is available at https://discourse.github.io/discourse/chat/backend/Chat/Service.html Generating documentation has been made as part of this commit with a bigger goal in mind of generally making it easier to dive into the chat project. Working with services generally involves 3 parts: - The service object itself, which is a series of steps where few of them are specialized (model, transaction, policy) ```ruby class UpdateAge include Chat::Service::Base model :user, :fetch_user policy :can_see_user contract step :update_age class Contract attribute :age, :integer end def fetch_user(user_id:, **) User.find_by(id: user_id) end def can_see_user(guardian:, **) guardian.can_see_user(user) end def update_age(age:, **) user.update!(age: age) end end ``` - The `with_service` controller helper, handling success and failure of the service within a service and making easy to return proper response to it from the controller ```ruby def update with_service(UpdateAge) do on_success { render_serialized(result.user, BasicUserSerializer, root: "user") } end end ``` - Rspec matchers and steps inspector, improving the dev experience while creating specs for a service ```ruby RSpec.describe(UpdateAge) do subject(:result) do described_class.call(guardian: guardian, user_id: user.id, age: age) end fab!(:user) { Fabricate(:user) } fab!(:current_user) { Fabricate(:admin) } let(:guardian) { Guardian.new(current_user) } let(:age) { 1 } it { expect(user.reload.age).to eq(age) } end ``` Note in case of unexpected failure in your spec, the output will give all the relevant information: ``` 1) UpdateAge when no channel_id is given is expected to fail to find a model named 'user' Failure/Error: it { is_expected.to fail_to_find_a_model(:user) } Expected model 'foo' (key: 'result.model.user') was not found in the result object. [1/4] [model] 'user' ❌ [2/4] [policy] 'can_see_user' [3/4] [contract] 'default' [4/4] [step] 'update_age' /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/update_age.rb:32:in `fetch_user': missing keyword: :user_id (ArgumentError) from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:202:in `instance_exec' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:202:in `call' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:219:in `call' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:417:in `block in run!' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:417:in `each' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:417:in `run!' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:411:in `run' from <internal:kernel>:90:in `tap' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:302:in `call' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/spec/services/update_age_spec.rb:15:in `block (3 levels) in <main>' ```
2023-02-13 07:09:57 -05:00
jsdoc@^3.6.3:
version "3.6.11"
resolved "https://registry.yarnpkg.com/jsdoc/-/jsdoc-3.6.11.tgz#8bbb5747e6f579f141a5238cbad4e95e004458ce"
integrity sha512-8UCU0TYeIYD9KeLzEcAu2q8N/mx9O3phAGl32nmHlE0LpaJL71mMkP4d+QE5zWfNt50qheHtOZ0qoxVrsX5TUg==
DEV: introduces documentation for chat (#19772) Note this commit also slightly changes internal API: channel instead of getChannel and updateCurrentUserChannelNotificationsSettings instead of updateCurrentUserChatChannelNotificationsSettings. Also destroyChannel takes a second param which is the name confirmation instead of an optional object containing this confirmation. This is to enforce the fact that it's required. In the future a top level jsdoc config file could be used instead of the hack tempfile, but while it's only an experiment for chat, it's probably good enough.
2023-01-18 06:36:16 -05:00
dependencies:
DEV: Chat service object initial implementation (#19814) This is a combined work of Martin Brennan, Loïc Guitaut, and Joffrey Jaffeux. --- This commit implements a base service object when working in chat. The documentation is available at https://discourse.github.io/discourse/chat/backend/Chat/Service.html Generating documentation has been made as part of this commit with a bigger goal in mind of generally making it easier to dive into the chat project. Working with services generally involves 3 parts: - The service object itself, which is a series of steps where few of them are specialized (model, transaction, policy) ```ruby class UpdateAge include Chat::Service::Base model :user, :fetch_user policy :can_see_user contract step :update_age class Contract attribute :age, :integer end def fetch_user(user_id:, **) User.find_by(id: user_id) end def can_see_user(guardian:, **) guardian.can_see_user(user) end def update_age(age:, **) user.update!(age: age) end end ``` - The `with_service` controller helper, handling success and failure of the service within a service and making easy to return proper response to it from the controller ```ruby def update with_service(UpdateAge) do on_success { render_serialized(result.user, BasicUserSerializer, root: "user") } end end ``` - Rspec matchers and steps inspector, improving the dev experience while creating specs for a service ```ruby RSpec.describe(UpdateAge) do subject(:result) do described_class.call(guardian: guardian, user_id: user.id, age: age) end fab!(:user) { Fabricate(:user) } fab!(:current_user) { Fabricate(:admin) } let(:guardian) { Guardian.new(current_user) } let(:age) { 1 } it { expect(user.reload.age).to eq(age) } end ``` Note in case of unexpected failure in your spec, the output will give all the relevant information: ``` 1) UpdateAge when no channel_id is given is expected to fail to find a model named 'user' Failure/Error: it { is_expected.to fail_to_find_a_model(:user) } Expected model 'foo' (key: 'result.model.user') was not found in the result object. [1/4] [model] 'user' ❌ [2/4] [policy] 'can_see_user' [3/4] [contract] 'default' [4/4] [step] 'update_age' /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/update_age.rb:32:in `fetch_user': missing keyword: :user_id (ArgumentError) from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:202:in `instance_exec' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:202:in `call' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:219:in `call' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:417:in `block in run!' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:417:in `each' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:417:in `run!' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:411:in `run' from <internal:kernel>:90:in `tap' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:302:in `call' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/spec/services/update_age_spec.rb:15:in `block (3 levels) in <main>' ```
2023-02-13 07:09:57 -05:00
"@babel/parser" "^7.9.4"
"@types/markdown-it" "^12.2.3"
bluebird "^3.7.2"
catharsis "^0.9.0"
escape-string-regexp "^2.0.0"
js2xmlparser "^4.0.2"
klaw "^3.0.0"
markdown-it "^12.3.2"
markdown-it-anchor "^8.4.1"
marked "^4.0.10"
mkdirp "^1.0.4"
requizzle "^0.2.3"
strip-json-comments "^3.1.0"
taffydb "2.6.2"
underscore "~1.13.2"
DEV: introduces documentation for chat (#19772) Note this commit also slightly changes internal API: channel instead of getChannel and updateCurrentUserChannelNotificationsSettings instead of updateCurrentUserChatChannelNotificationsSettings. Also destroyChannel takes a second param which is the name confirmation instead of an optional object containing this confirmation. This is to enforce the fact that it's required. In the future a top level jsdoc config file could be used instead of the hack tempfile, but while it's only an experiment for chat, it's probably good enough.
2023-01-18 06:36:16 -05:00
jsdoc@^4.0.0:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "4.0.2"
resolved "https://registry.yarnpkg.com/jsdoc/-/jsdoc-4.0.2.tgz#a1273beba964cf433ddf7a70c23fd02c3c60296e"
integrity sha512-e8cIg2z62InH7azBBi3EsSEqrKx+nUtAS5bBcYTSpZFA+vhNPyhv8PTFZ0WsjOPDj04/dOLlm08EDcQJDqaGQg==
DEV: introduces documentation for chat (#19772) Note this commit also slightly changes internal API: channel instead of getChannel and updateCurrentUserChannelNotificationsSettings instead of updateCurrentUserChatChannelNotificationsSettings. Also destroyChannel takes a second param which is the name confirmation instead of an optional object containing this confirmation. This is to enforce the fact that it's required. In the future a top level jsdoc config file could be used instead of the hack tempfile, but while it's only an experiment for chat, it's probably good enough.
2023-01-18 06:36:16 -05:00
dependencies:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
"@babel/parser" "^7.20.15"
DEV: introduces documentation for chat (#19772) Note this commit also slightly changes internal API: channel instead of getChannel and updateCurrentUserChannelNotificationsSettings instead of updateCurrentUserChatChannelNotificationsSettings. Also destroyChannel takes a second param which is the name confirmation instead of an optional object containing this confirmation. This is to enforce the fact that it's required. In the future a top level jsdoc config file could be used instead of the hack tempfile, but while it's only an experiment for chat, it's probably good enough.
2023-01-18 06:36:16 -05:00
"@jsdoc/salty" "^0.2.1"
"@types/markdown-it" "^12.2.3"
bluebird "^3.7.2"
catharsis "^0.9.0"
escape-string-regexp "^2.0.0"
js2xmlparser "^4.0.2"
klaw "^3.0.0"
markdown-it "^12.3.2"
markdown-it-anchor "^8.4.1"
marked "^4.0.10"
mkdirp "^1.0.4"
requizzle "^0.2.3"
strip-json-comments "^3.1.0"
underscore "~1.13.2"
Upgrade puppeteer which was accidentally downgraded.
2018-06-07 02:03:01 -04:00
jsesc@^2.5.1:
Upgrade to FontAwesome 5 (take two) (#6673) * Add missing icons to set * Revert FA5 revert This reverts commit 42572ff * use new SVG syntax in locales * Noscript page changes (remove login button, center "powered by" footer text) * Cast wider net for SVG icons in settings - include any _icon setting for SVG registry (offers better support for plugin settings) - let themes store multiple pipe-delimited icons in a setting - also replaces broken onebox image icon with SVG reference in cooked post processor * interpolate icons in locales * Fix composer whisper icon alignment * Add support for stacked icons * SECURITY: enforce hostname to match discourse hostname This ensures that the hostname rails uses for various helpers always matches the Discourse hostname * load SVG sprite with pre-initializers * FIX: enable caching on SVG sprites * PERF: use JSONP for SVG sprites so they are served from CDN This avoids needing to deal with CORS for loading of the SVG Note, added the svg- prefix to the filename so we can quickly tell in dev tools what the file is * Add missing SVG sprite JSONP script to CSP * Upgrade to FA 5.5.0 * Add support for all FA4.7 icons - adds complete frontend and backend for renamed FA4.7 icons - improves performance of SvgSprite.bundle and SvgSprite.all_icons * Fix group avatar flair preview - adds an endpoint at /svg-sprites/search/:keyword - adds frontend ajax call that pulls icon in avatar flair preview even when it is not in subset * Remove FA 4.7 font files
2018-11-26 16:49:57 -05:00
version "2.5.2"
resolved "https://registry.yarnpkg.com/jsesc/-/jsesc-2.5.2.tgz#80564d2e483dacf6e8ef209650a67df3f0c283a4"
integrity sha512-OYu7XEzjkCQ3C5Ps3QIZsQfNpqoJyZZA99wd9aWd05NCtC5pWOkShK2mkL6HXQR6/Cy2lbNdPlZBpuQHXE63gA==
Upgrade puppeteer which was accidentally downgraded.
2018-06-07 02:03:01 -04:00
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
json-buffer@3.0.1:
version "3.0.1"
resolved "https://registry.yarnpkg.com/json-buffer/-/json-buffer-3.0.1.tgz#9338802a30d3b6605fbe0613e094008ca8c05a13"
integrity sha512-4bV5BfR2mqfQTJm+V5tPPdf+ZpuhiIvTuAB5g8kcrXOZpTT/QwwVRWBywX1ozr6lEuPdbHxwaJlm9G6mI2sfSQ==
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
json-schema-traverse@^0.4.1:
version "0.4.1"
resolved "https://registry.yarnpkg.com/json-schema-traverse/-/json-schema-traverse-0.4.1.tgz#69f6a87d9513ab8bb8fe63bdb0979c448e684660"
integrity sha512-xbbCH5dCYU5T8LcEhhuh7HJ88HXuW3qsI3Y0zOZFKfZEHcpWiHU/Jxzk629Brsab/mMiHQti9wMP+845RPe3Vg==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
json-stable-stringify-without-jsonify@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/json-stable-stringify-without-jsonify/-/json-stable-stringify-without-jsonify-1.0.1.tgz#9db7b59496ad3f3cfef30a75142d2d930ad72651"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-Bdboy+l7tA3OGW6FjyFHWkP5LuByj1Tk33Ljyq0axyzdk9//JSi2u3fP1QSmd1KNwq6VOKYGlAu87CisVir6Pw==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
json5@^2.2.3:
DEV: Update json5, remove an unused lockfile (#19732)
2023-01-04 17:15:49 -05:00
version "2.2.3"
resolved "https://registry.yarnpkg.com/json5/-/json5-2.2.3.tgz#78cd6f1a19bdc12b73db5ad0c61efd66c1e29283"
integrity sha512-XmOWe7eyHYH14cLdVPoyg+GOH3rYX++KpzrylJwSW98t3Nk+U8XOl8FWKOgwtzdb8lXGf6zYwDUzeHMWfxasyg==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
jsonfile@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/jsonfile/-/jsonfile-4.0.0.tgz#8771aae0799b64076b76640fca058f9c10e33ecb"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
integrity sha512-m6F1R3z8jjlf2imQHS2Qez5sjKWQzbuuhuJ/FKYFRZvPE3PuHcSMVZzfsLhGVOkfd20obL5SWEBew5ShlquNxg==
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
optionalDependencies:
graceful-fs "^4.1.6"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
jsonfile@^6.0.1:
version "6.1.0"
resolved "https://registry.yarnpkg.com/jsonfile/-/jsonfile-6.1.0.tgz#bc55b2634793c679ec6403094eb13698a6ec0aae"
integrity sha512-5dgndWOriYSm5cnYaJNhalLNDKOqFwyDB/rr1E9ZsGciGvKPs8R2xYGCacuf3z6K1YKDz182fd+fY3cn3pMqXQ==
dependencies:
universalify "^2.0.0"
optionalDependencies:
graceful-fs "^4.1.6"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
keyv@^4.5.3:
version "4.5.4"
resolved "https://registry.yarnpkg.com/keyv/-/keyv-4.5.4.tgz#a879a99e29452f942439f2a405e3af8b31d4de93"
integrity sha512-oxVHkHR/EJf2CNXnWxRLW6mg7JyCCUcG0DtEGmL2ctUo1PNTin1PUil+r/+4r5MpVgC/fn1kjsx7mjSujKqIpw==
dependencies:
json-buffer "3.0.1"
DEV: introduces documentation for chat (#19772) Note this commit also slightly changes internal API: channel instead of getChannel and updateCurrentUserChannelNotificationsSettings instead of updateCurrentUserChatChannelNotificationsSettings. Also destroyChannel takes a second param which is the name confirmation instead of an optional object containing this confirmation. This is to enforce the fact that it's required. In the future a top level jsdoc config file could be used instead of the hack tempfile, but while it's only an experiment for chat, it's probably good enough.
2023-01-18 06:36:16 -05:00
klaw@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/klaw/-/klaw-3.0.0.tgz#b11bec9cf2492f06756d6e809ab73a2910259146"
integrity sha512-0Fo5oir+O9jnXu5EefYbVK+mHMBeEVEy2cmctR1O1NECcCkPRreJKrS6Qt/j3KC2C148Dfo9i3pCmCMsdqGr0g==
dependencies:
graceful-fs "^4.1.9"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
language-subtag-registry@^0.3.20:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
version "0.3.22"
resolved "https://registry.yarnpkg.com/language-subtag-registry/-/language-subtag-registry-0.3.22.tgz#2e1500861b2e457eba7e7ae86877cbd08fa1fd1d"
integrity sha512-tN0MCzyWnoz/4nHS6uxdlFWoUZT7ABptwKPQ52Ea7URk6vll88bWBVhodtnlfEuCcKWNGoc+uGbw1cwa9IKh/w==
DEV: Update ember-template-lint (#22242)
2023-06-22 16:54:46 -04:00
language-tags@^1.0.8:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
version "1.0.9"
resolved "https://registry.yarnpkg.com/language-tags/-/language-tags-1.0.9.tgz#1ffdcd0ec0fafb4b1be7f8b11f306ad0f9c08777"
integrity sha512-MbjN408fEndfiQXbFQ1vnd+1NoLDsnQW41410oQBXiyXDMYH5z505juWa4KUE1LqxRC7DgOgZDbKLxHIwm27hA==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
dependencies:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
language-subtag-registry "^0.3.20"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
Revert "DEV: FloatKit (#23541)" (#23549) This reverts commits 0623ac684a65f95ce4f5438ff47944b1dc2119f4 408e71e437ef8abf98f93e3449898bf906766b0e a32fa3b9470dde0543fcee809f2abd1f219f7336 User tips were running into some issues.
2023-09-12 13:55:12 -04:00
lefthook-darwin-arm64@1.4.3:
version "1.4.3"
resolved "https://registry.yarnpkg.com/lefthook-darwin-arm64/-/lefthook-darwin-arm64-1.4.3.tgz#b253fbc20041815010da66e8588faf4bbd75c0aa"
integrity sha512-ZFsgIzN+Z0c4RpMMHU/M4J43XFyXYGZI8r0GG4jqVMX+prDBIb/6vpgMdZxK5IozRUmnfLGQPXcVokE9WBHSOg==
lefthook-darwin-x64@1.4.3:
version "1.4.3"
resolved "https://registry.yarnpkg.com/lefthook-darwin-x64/-/lefthook-darwin-x64-1.4.3.tgz#5afa63f7a18cf89495895fc1321cdd749825bf9c"
integrity sha512-O6ZesdJ9MStI38gNfJh0ShExIf0KyHG1lR32F9FUFklFwhcquRM+uIDyDqVCxU3UWqmKwcbTk9AJWMjQZGPLxQ==
lefthook-freebsd-arm64@1.4.3:
version "1.4.3"
resolved "https://registry.yarnpkg.com/lefthook-freebsd-arm64/-/lefthook-freebsd-arm64-1.4.3.tgz#070141ccc981658bd7545f40b14814b410f2930e"
integrity sha512-6swb+98Qs6P9V9Rcd2lHWH2LunFEk+kfIPpf6oiPrOHnw3OkfFhQLmawX425Ari7Y9qy9gfDoNe/0/IR7YGmGw==
lefthook-freebsd-x64@1.4.3:
version "1.4.3"
resolved "https://registry.yarnpkg.com/lefthook-freebsd-x64/-/lefthook-freebsd-x64-1.4.3.tgz#47b4e7cf4c0459b1152e605c047541ec3eec5f0b"
integrity sha512-+58NARATypmIj0kDutd29ozywr6IeA0lVBxsVzq7C5ycYrd31iNak3lnaEvNJvdj5fGVNEL9X7XRojylthZlAg==
lefthook-linux-arm64@1.4.3:
version "1.4.3"
resolved "https://registry.yarnpkg.com/lefthook-linux-arm64/-/lefthook-linux-arm64-1.4.3.tgz#b3caae33a20cc2665ec047a098e7b4e4498d63d1"
integrity sha512-gAWJQEhgheOfPu579fhlcNNm3KoJbNkT11AATKHlFu+esyiCxI8xZVpGwDQVMphO7s43FKbkQJSvIM4tElb6FQ==
lefthook-linux-x64@1.4.3:
version "1.4.3"
resolved "https://registry.yarnpkg.com/lefthook-linux-x64/-/lefthook-linux-x64-1.4.3.tgz#ac2990e23a4c39bf774e4094f33c0fbaef79129c"
integrity sha512-mVv/amRqX81nQcizhRRx/X6KKNIkMUG4HdDItWkDazwLAviZ2zv8TRcSaEYBOpriP/dBZm8gt6EhzPpfoWtcJw==
lefthook-windows-arm64@1.4.3:
version "1.4.3"
resolved "https://registry.yarnpkg.com/lefthook-windows-arm64/-/lefthook-windows-arm64-1.4.3.tgz#dc0dcfea32badab031183bdc8cd91bda929cee9b"
integrity sha512-ccClPTC7AvhcbyT6pLzdV8K8e/P0T7p/THGRtcyjkKIU0IS89k95VazDlt22QPzUTc8UMNCQyZ1XY4UDx295jw==
lefthook-windows-x64@1.4.3:
version "1.4.3"
resolved "https://registry.yarnpkg.com/lefthook-windows-x64/-/lefthook-windows-x64-1.4.3.tgz#795b1215969c7d0d4007f89bfe660cfc2736075c"
integrity sha512-q1K5kycfqTYLm5/pOCiAFa+hoSFt/29QjHVZAWRmk/nKDIf8MvTWX0tdaEx7/VJuG3cgQT1jM+xiTwSmNUXTKg==
DEV: Upgrade "lefthook" and skip hooks during merge/rebase (#18910) The old lefthook package was deprecated a long time ago and skipping hooks during merge/rebase makes those git commands a lot faster.
2022-11-07 11:13:21 -05:00
lefthook@^1.2.0:
Revert "DEV: FloatKit (#23541)" (#23549) This reverts commits 0623ac684a65f95ce4f5438ff47944b1dc2119f4 408e71e437ef8abf98f93e3449898bf906766b0e a32fa3b9470dde0543fcee809f2abd1f219f7336 User tips were running into some issues.
2023-09-12 13:55:12 -04:00
version "1.4.3"
resolved "https://registry.yarnpkg.com/lefthook/-/lefthook-1.4.3.tgz#cedfd13f13c87a974ea5e055853c7fae0c6df11e"
integrity sha512-zvhAJ9wDQW7F27XYWRfx72L6LuPLu49be+sRUF+DKku1IGT+x3eHjQ9k70pt65lnEq1X8Xl/Xygm3Kwi/piOYg==
DEV: Upgrade "lefthook" and skip hooks during merge/rebase (#18910) The old lefthook package was deprecated a long time ago and skipping hooks during merge/rebase makes those git commands a lot faster.
2022-11-07 11:13:21 -05:00
optionalDependencies:
Revert "DEV: FloatKit (#23541)" (#23549) This reverts commits 0623ac684a65f95ce4f5438ff47944b1dc2119f4 408e71e437ef8abf98f93e3449898bf906766b0e a32fa3b9470dde0543fcee809f2abd1f219f7336 User tips were running into some issues.
2023-09-12 13:55:12 -04:00
lefthook-darwin-arm64 "1.4.3"
lefthook-darwin-x64 "1.4.3"
lefthook-freebsd-arm64 "1.4.3"
lefthook-freebsd-x64 "1.4.3"
lefthook-linux-arm64 "1.4.3"
lefthook-linux-x64 "1.4.3"
lefthook-windows-arm64 "1.4.3"
lefthook-windows-x64 "1.4.3"
DEV: Upgrade "lefthook" and skip hooks during merge/rebase (#18910) The old lefthook package was deprecated a long time ago and skipping hooks during merge/rebase makes those git commands a lot faster.
2022-11-07 11:13:21 -05:00
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
levn@^0.4.1:
version "0.4.1"
resolved "https://registry.yarnpkg.com/levn/-/levn-0.4.1.tgz#ae4562c007473b932a6200d403268dd2fffc6ade"
integrity sha512-+bT2uH4E5LGE7h/n3evcS/sQlJXCpIp6ym8OWJ5eV6+67Dsql/LaaT7qJBAt2rzfoa/5QBGBhxDix1dMt2kQKQ==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
dependencies:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
prelude-ls "^1.2.1"
type-check "~0.4.0"
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
Run JS test in chrome headless on Travis.
2017-12-14 21:15:04 -05:00
lighthouse-logger@^1.0.0:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "1.4.2"
resolved "https://registry.yarnpkg.com/lighthouse-logger/-/lighthouse-logger-1.4.2.tgz#aef90f9e97cd81db367c7634292ee22079280aaa"
integrity sha512-gPWxznF6TKmUHrOQjlVo2UbaL2EJ71mb2CCeRs/2qBpi4L/g4LUVc9+3lKQ6DTUZwJswfM7ainGrLO1+fOqa2g==
Run JS test in chrome headless on Travis.
2017-12-14 21:15:04 -05:00
dependencies:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
debug "^2.6.9"
marky "^1.2.2"
line-column@^1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/line-column/-/line-column-1.0.2.tgz#d25af2936b6f4849172b312e4792d1d987bc34a2"
integrity sha512-Ktrjk5noGYlHsVnYWh62FLVs4hTb8A3e+vucNZMgPeAOITdshMSgv4cCZQeRDjm7+goqmo6+liZwTXo+U3sVww==
dependencies:
isarray "^1.0.0"
isobject "^2.0.0"
Run JS test in chrome headless on Travis.
2017-12-14 21:15:04 -05:00
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
linkify-it@^3.0.1:
version "3.0.3"
resolved "https://registry.yarnpkg.com/linkify-it/-/linkify-it-3.0.3.tgz#a98baf44ce45a550efb4d49c769d07524cc2fa2e"
integrity sha512-ynTsyrFSdE5oZ/O9GEf00kPngmOfVwazR5GKDq6EYfhlpFug3J2zybX56a2PRRpc9P+FuSoGNAwjlbDs9jJBPQ==
DEV: introduces documentation for chat (#19772) Note this commit also slightly changes internal API: channel instead of getChannel and updateCurrentUserChannelNotificationsSettings instead of updateCurrentUserChatChannelNotificationsSettings. Also destroyChannel takes a second param which is the name confirmation instead of an optional object containing this confirmation. This is to enforce the fact that it's required. In the future a top level jsdoc config file could be used instead of the hack tempfile, but while it's only an experiment for chat, it's probably good enough.
2023-01-18 06:36:16 -05:00
dependencies:
uc.micro "^1.0.1"
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
lint-to-the-future-ember-template@^1.1.1:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "1.2.0"
resolved "https://registry.yarnpkg.com/lint-to-the-future-ember-template/-/lint-to-the-future-ember-template-1.2.0.tgz#d27cba1669ea569787fb1ef86a2d7953249cad6d"
integrity sha512-MtbF3OITW2fh900RU08TQsrGt5ljvzYklvV3SEli4o1RqQ5oM4+yTsU4irvO3usmuO4C1lpXUAGZ6az7kqeXxw==
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
dependencies:
esm "^3.2.25"
import-cwd "^3.0.0"
walk-sync "^2.2.0"
lint-to-the-future-eslint@^2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/lint-to-the-future-eslint/-/lint-to-the-future-eslint-2.0.1.tgz#63a044db5af5f2f81c6abc0bb79ceec305d814e8"
integrity sha512-p9I4Z8ncSroU6fPZfZ6d/qnbUqLbJJLg8Lzub0db/02rdO3TXMuP+/P4dFWs0VVVAC1wL+ctSZ3Z0bJttK6oKg==
dependencies:
import-cwd "^3.0.0"
semver "^7.3.5"
walk-sync "^3.0.0"
lint-to-the-future@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/lint-to-the-future/-/lint-to-the-future-2.0.0.tgz#32f0b2e18762fd041f9433f71ab30274a07ac24c"
integrity sha512-gutEHLC1w5Ivh4nKQTuNV9lwnXKuUtwZ1kWOhVZVAhs6dsw71IBzS28+Kt1KiNFCds/TVkbj4OFQ2sXQaPtrkg==
dependencies:
chai "^4.3.6"
commander "^9.4.1"
fs-extra "^7.0.1"
import-cwd "^3.0.0"
node-fetch "^2.6.0"
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
locate-path@^6.0.0:
version "6.0.0"
resolved "https://registry.yarnpkg.com/locate-path/-/locate-path-6.0.0.tgz#55321eb309febbc59c4801d931a72452a681d286"
integrity sha512-iPZK6eYjbxRu3uB4/WZ3EsEIMJFMqAoopl3R+zuq0UjcAm/MO6KCweDgPfP3elTztoKP3KtnVHxTn2NHBSDVUw==
dependencies:
p-locate "^5.0.0"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
locate-path@^7.1.0:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "7.2.0"
resolved "https://registry.yarnpkg.com/locate-path/-/locate-path-7.2.0.tgz#69cb1779bd90b35ab1e771e1f2f89a202c2a8a8a"
integrity sha512-gvVijfZvn7R+2qyPX8mAuKcFGDf6Nc61GdvGafQsHL0sBIxfKzA+usWn4GFC/bk+QdwPUD4kWFJLhElipq+0VA==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
dependencies:
p-locate "^6.0.0"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
lodash.camelcase@^4.1.1:
version "4.3.0"
resolved "https://registry.yarnpkg.com/lodash.camelcase/-/lodash.camelcase-4.3.0.tgz#b28aa6288a2b9fc651035c7711f65ab6190331a6"
integrity sha512-TwuEnCnxbc3rAvhf/LbG7tJUDzhqXyFnv3dtzLOPgCG/hODL7WFnsbwktkD7yUV0RrreP/l1PALq/YSg6VvjlA==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
lodash.kebabcase@^4.1.1:
version "4.1.1"
resolved "https://registry.yarnpkg.com/lodash.kebabcase/-/lodash.kebabcase-4.1.1.tgz#8489b1cb0d29ff88195cceca448ff6d6cc295c36"
integrity sha512-N8XRTIMMqqDgSy4VLKPnJ/+hpGZN+PHQiJnSenYqPaVV/NCqEogTnAdZLQiGKhxX+JCs8waWq2t1XHWKOmlY8g==
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
lodash.merge@^4.6.2:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
version "4.6.2"
resolved "https://registry.yarnpkg.com/lodash.merge/-/lodash.merge-4.6.2.tgz#558aa53b43b661e1925a0afdfa36a9a1085fe57a"
integrity sha512-0KpjqXRVvrYyCsX1swR/XTK0va6VQkQM6MNo7PqW77ByjAhoARA8EfrP1N4+KlKj8YS0ZUCtRT/YUuhyYDujIQ==
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
lodash@^4.17.14, lodash@^4.17.15, lodash@^4.17.21:
DEV: Update lodash from 4.17.15 to 4.17.21 (#13045) We're dropping lodash from core after the next release, but until then let's keep it up to date.
2021-05-12 12:07:23 -04:00
version "4.17.21"
resolved "https://registry.yarnpkg.com/lodash/-/lodash-4.17.21.tgz#679591c564c3bffaae8454cf0b3df370c3d6911c"
integrity sha512-v2kDEe57lecTulaDIuNTPy3Ry4gLGJ6Z1O3vE1krgXZNrsQ+LFTGHVxVjcXPs17LhbZVGedAJv8XZ1tvj5FvSg==
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
log-symbols@^4.1.0:
version "4.1.0"
resolved "https://registry.yarnpkg.com/log-symbols/-/log-symbols-4.1.0.tgz#3fbdbb95b4683ac9fc785111e792e558d4abd503"
integrity sha512-8XPvpAA8uyhfteu8pIvQxpJZ7SYYdpUivZpGy6sFsBuKRY/7rQGavedeB8aK+Zkyq6upMFVL/9AW6vOYzfRyLg==
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
dependencies:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
chalk "^4.1.0"
is-unicode-supported "^0.1.0"
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
loupe@^2.3.1:
version "2.3.6"
resolved "https://registry.yarnpkg.com/loupe/-/loupe-2.3.6.tgz#76e4af498103c532d1ecc9be102036a21f787b53"
integrity sha512-RaPMZKiMy8/JruncMU5Bt6na1eftNoo++R4Y+N2FrxkDVTrGvcyzFTsaGif4QTeKESheMGegbhw6iUAq+5A8zA==
dependencies:
get-func-name "^2.0.0"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
lower-case@^2.0.2:
version "2.0.2"
resolved "https://registry.yarnpkg.com/lower-case/-/lower-case-2.0.2.tgz#6fa237c63dbdc4a82ca0fd882e4722dc5e634e28"
integrity sha512-7fm3l3NAF9WfN6W3JOmf5drwpVqX78JtoGJ3A6W0a6ZnldM41w2fV5D490psKFTpMds8TJse/eHLFFsNHHjHgg==
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
dependencies:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
tslib "^2.0.3"
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
lru-cache@^5.1.1:
version "5.1.1"
resolved "https://registry.yarnpkg.com/lru-cache/-/lru-cache-5.1.1.tgz#1da27e6710271947695daf6848e847f01d84b920"
integrity sha512-KpNARQA3Iwv+jTA0utUVVbrh+Jlrr1Fv0e56GGzAFOXN7dk/FviaDW8LHmK52DlcH4WP2n6gI8vN1aesBFgo9w==
dependencies:
yallist "^3.0.2"
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
lru-cache@^6.0.0:
version "6.0.0"
resolved "https://registry.yarnpkg.com/lru-cache/-/lru-cache-6.0.0.tgz#6d6fe6570ebd96aaf90fcad1dafa3b2566db3a94"
integrity sha512-Jo6dJ04CmSjuznwJSS3pUeWmd/H0ffTlkXXgwZi+eq1UCmqQwCh+eLsYOYCwY991i2Fah4h1BEMCx4qThGbsiA==
dependencies:
yallist "^4.0.0"
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
lru-cache@^7.14.1:
version "7.18.3"
resolved "https://registry.yarnpkg.com/lru-cache/-/lru-cache-7.18.3.tgz#f793896e0fd0e954a59dfdd82f0773808df6aa89"
integrity sha512-jumlc0BIUrS3qJGgIkWZsyfAM7NCWiBcCDhnd+3NNM5KbBmLTgHVfWBcg6W+rLUsIpzpERPsvwUP7CckAQSOoA==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
magic-string@^0.25.7:
version "0.25.9"
resolved "https://registry.yarnpkg.com/magic-string/-/magic-string-0.25.9.tgz#de7f9faf91ef8a1c91d02c2e5314c8277dbcdd1c"
integrity sha512-RmF0AsMzgt25qzqqLc1+MbHmhdx0ojF2Fvs4XnOqz2ZOBXzzkEwc/dJQZCYHAn7v1jbVOjAZfK8msRn4BxO4VQ==
dependencies:
sourcemap-codec "^1.4.8"
magic-string@^0.30.0:
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
version "0.30.5"
resolved "https://registry.yarnpkg.com/magic-string/-/magic-string-0.30.5.tgz#1994d980bd1c8835dc6e78db7cbd4ae4f24746f9"
integrity sha512-7xlpfBaQaP/T6Vh8MO/EqXSW5En6INHEvEXQiuff7Gku0PWjU3uf6w/j9o7O+SpB5fOAkrI5HeoNgwjEO0pFsA==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
dependencies:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
"@jridgewell/sourcemap-codec" "^1.4.15"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
Use Yarn to manage dependencies, cleanup unused bootstrap libs (#6436)
2018-10-03 10:15:43 -04:00
magnific-popup@1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/magnific-popup/-/magnific-popup-1.1.0.tgz#3e7362c5bd18f6785fe99e59d013e20af33d3049"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-ghSa/1TKsOUL6ZlHfcfFCoB9Wms2nqaDdBEPh6QX9jFYQyMkUu7ciU1mrxedWWq4NM2m1C/llhHKLt6GKRYOzg==
Use Yarn to manage dependencies, cleanup unused bootstrap libs (#6436)
2018-10-03 10:15:43 -04:00
DEV: introduces documentation for chat (#19772) Note this commit also slightly changes internal API: channel instead of getChannel and updateCurrentUserChannelNotificationsSettings instead of updateCurrentUserChatChannelNotificationsSettings. Also destroyChannel takes a second param which is the name confirmation instead of an optional object containing this confirmation. This is to enforce the fact that it's required. In the future a top level jsdoc config file could be used instead of the hack tempfile, but while it's only an experiment for chat, it's probably good enough.
2023-01-18 06:36:16 -05:00
markdown-it-anchor@^8.4.1:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "8.6.7"
resolved "https://registry.yarnpkg.com/markdown-it-anchor/-/markdown-it-anchor-8.6.7.tgz#ee6926daf3ad1ed5e4e3968b1740eef1c6399634"
integrity sha512-FlCHFwNnutLgVTflOYHPW2pPcl2AACqVzExlkGQNsi4CJgqOHN7YTgDd4LuhgN1BFO3TS0vLAruV1Td6dwWPJA==
DEV: introduces documentation for chat (#19772) Note this commit also slightly changes internal API: channel instead of getChannel and updateCurrentUserChannelNotificationsSettings instead of updateCurrentUserChatChannelNotificationsSettings. Also destroyChannel takes a second param which is the name confirmation instead of an optional object containing this confirmation. This is to enforce the fact that it's required. In the future a top level jsdoc config file could be used instead of the hack tempfile, but while it's only an experiment for chat, it's probably good enough.
2023-01-18 06:36:16 -05:00
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
markdown-it@^12.3.2:
version "12.3.2"
resolved "https://registry.yarnpkg.com/markdown-it/-/markdown-it-12.3.2.tgz#bf92ac92283fe983fe4de8ff8abfb5ad72cd0c90"
integrity sha512-TchMembfxfNVpHkbtriWltGWc+m3xszaRD0CZup7GFFhzIgQqxIfn3eGj1yZpfuflzPvfkt611B2Q/Bsk1YnGg==
DEV: introduces documentation for chat (#19772) Note this commit also slightly changes internal API: channel instead of getChannel and updateCurrentUserChannelNotificationsSettings instead of updateCurrentUserChatChannelNotificationsSettings. Also destroyChannel takes a second param which is the name confirmation instead of an optional object containing this confirmation. This is to enforce the fact that it's required. In the future a top level jsdoc config file could be used instead of the hack tempfile, but while it's only an experiment for chat, it's probably good enough.
2023-01-18 06:36:16 -05:00
dependencies:
argparse "^2.0.1"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
entities "~2.1.0"
linkify-it "^3.0.1"
DEV: introduces documentation for chat (#19772) Note this commit also slightly changes internal API: channel instead of getChannel and updateCurrentUserChannelNotificationsSettings instead of updateCurrentUserChatChannelNotificationsSettings. Also destroyChannel takes a second param which is the name confirmation instead of an optional object containing this confirmation. This is to enforce the fact that it's required. In the future a top level jsdoc config file could be used instead of the hack tempfile, but while it's only an experiment for chat, it's probably good enough.
2023-01-18 06:36:16 -05:00
mdurl "^1.0.1"
uc.micro "^1.0.5"
DEV: Chat service object initial implementation (#19814) This is a combined work of Martin Brennan, Loïc Guitaut, and Joffrey Jaffeux. --- This commit implements a base service object when working in chat. The documentation is available at https://discourse.github.io/discourse/chat/backend/Chat/Service.html Generating documentation has been made as part of this commit with a bigger goal in mind of generally making it easier to dive into the chat project. Working with services generally involves 3 parts: - The service object itself, which is a series of steps where few of them are specialized (model, transaction, policy) ```ruby class UpdateAge include Chat::Service::Base model :user, :fetch_user policy :can_see_user contract step :update_age class Contract attribute :age, :integer end def fetch_user(user_id:, **) User.find_by(id: user_id) end def can_see_user(guardian:, **) guardian.can_see_user(user) end def update_age(age:, **) user.update!(age: age) end end ``` - The `with_service` controller helper, handling success and failure of the service within a service and making easy to return proper response to it from the controller ```ruby def update with_service(UpdateAge) do on_success { render_serialized(result.user, BasicUserSerializer, root: "user") } end end ``` - Rspec matchers and steps inspector, improving the dev experience while creating specs for a service ```ruby RSpec.describe(UpdateAge) do subject(:result) do described_class.call(guardian: guardian, user_id: user.id, age: age) end fab!(:user) { Fabricate(:user) } fab!(:current_user) { Fabricate(:admin) } let(:guardian) { Guardian.new(current_user) } let(:age) { 1 } it { expect(user.reload.age).to eq(age) } end ``` Note in case of unexpected failure in your spec, the output will give all the relevant information: ``` 1) UpdateAge when no channel_id is given is expected to fail to find a model named 'user' Failure/Error: it { is_expected.to fail_to_find_a_model(:user) } Expected model 'foo' (key: 'result.model.user') was not found in the result object. [1/4] [model] 'user' ❌ [2/4] [policy] 'can_see_user' [3/4] [contract] 'default' [4/4] [step] 'update_age' /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/update_age.rb:32:in `fetch_user': missing keyword: :user_id (ArgumentError) from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:202:in `instance_exec' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:202:in `call' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:219:in `call' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:417:in `block in run!' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:417:in `each' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:417:in `run!' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:411:in `run' from <internal:kernel>:90:in `tap' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:302:in `call' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/spec/services/update_age_spec.rb:15:in `block (3 levels) in <main>' ```
2023-02-13 07:09:57 -05:00
marked@^4.0.10:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "4.3.0"
resolved "https://registry.yarnpkg.com/marked/-/marked-4.3.0.tgz#796362821b019f734054582038b116481b456cf3"
integrity sha512-PRsaiG84bK+AMvxziE/lCFss8juXjNaWzVbN5tXAm4XjeaS9NAHhop+PjQxz2A9h8Q4M/xGmzP8vqNwy6JeK0A==
DEV: introduces documentation for chat (#19772) Note this commit also slightly changes internal API: channel instead of getChannel and updateCurrentUserChannelNotificationsSettings instead of updateCurrentUserChatChannelNotificationsSettings. Also destroyChannel takes a second param which is the name confirmation instead of an optional object containing this confirmation. This is to enforce the fact that it's required. In the future a top level jsdoc config file could be used instead of the hack tempfile, but while it's only an experiment for chat, it's probably good enough.
2023-01-18 06:36:16 -05:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
marky@^1.2.2:
version "1.2.5"
resolved "https://registry.yarnpkg.com/marky/-/marky-1.2.5.tgz#55796b688cbd72390d2d399eaaf1832c9413e3c0"
integrity sha512-q9JtQJKjpsVxCRVgQ+WapguSbKC3SQ5HEzFGPAJMStgh3QjCawp00UKv3MTTAArTmGmmPUvllHZoNbZ3gs0I+Q==
matcher-collection@^1.0.0, matcher-collection@^1.1.1:
version "1.1.2"
resolved "https://registry.yarnpkg.com/matcher-collection/-/matcher-collection-1.1.2.tgz#1076f506f10ca85897b53d14ef54f90a5c426838"
integrity sha512-YQ/teqaOIIfUHedRam08PB3NK7Mjct6BvzRnJmpGDm8uFXpNr1sbY4yuflI5JcEs6COpYA0FpRQhSDBf1tT95g==
dependencies:
minimatch "^3.0.2"
Upgrade to FontAwesome 5 (take two) (#6673) * Add missing icons to set * Revert FA5 revert This reverts commit 42572ff * use new SVG syntax in locales * Noscript page changes (remove login button, center "powered by" footer text) * Cast wider net for SVG icons in settings - include any _icon setting for SVG registry (offers better support for plugin settings) - let themes store multiple pipe-delimited icons in a setting - also replaces broken onebox image icon with SVG reference in cooked post processor * interpolate icons in locales * Fix composer whisper icon alignment * Add support for stacked icons * SECURITY: enforce hostname to match discourse hostname This ensures that the hostname rails uses for various helpers always matches the Discourse hostname * load SVG sprite with pre-initializers * FIX: enable caching on SVG sprites * PERF: use JSONP for SVG sprites so they are served from CDN This avoids needing to deal with CORS for loading of the SVG Note, added the svg- prefix to the filename so we can quickly tell in dev tools what the file is * Add missing SVG sprite JSONP script to CSP * Upgrade to FA 5.5.0 * Add support for all FA4.7 icons - adds complete frontend and backend for renamed FA4.7 icons - improves performance of SvgSprite.bundle and SvgSprite.all_icons * Fix group avatar flair preview - adds an endpoint at /svg-sprites/search/:keyword - adds frontend ajax call that pulls icon in avatar flair preview even when it is not in subset * Remove FA 4.7 font files
2018-11-26 16:49:57 -05:00
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
matcher-collection@^2.0.0, matcher-collection@^2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/matcher-collection/-/matcher-collection-2.0.1.tgz#90be1a4cf58d6f2949864f65bb3b0f3e41303b29"
integrity sha512-daE62nS2ZQsDg9raM0IlZzLmI2u+7ZapXBwdoeBUKAYERPDDIc0qNqA8E0Rp2D+gspKR7BgIFP52GeujaGXWeQ==
dependencies:
"@types/minimatch" "^3.0.3"
minimatch "^3.0.2"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
mdn-data@2.0.30:
version "2.0.30"
resolved "https://registry.yarnpkg.com/mdn-data/-/mdn-data-2.0.30.tgz#ce4df6f80af6cfbe218ecd5c552ba13c4dfa08cc"
integrity sha512-GaqWWShW4kv/G9IEucWScBx9G1/vsFZZJUO+tD26M8J8z3Kw5RDQjaoZe03YAClgeS/SWPOcb4nkFBTEi5DUEA==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
DEV: introduces documentation for chat (#19772) Note this commit also slightly changes internal API: channel instead of getChannel and updateCurrentUserChannelNotificationsSettings instead of updateCurrentUserChatChannelNotificationsSettings. Also destroyChannel takes a second param which is the name confirmation instead of an optional object containing this confirmation. This is to enforce the fact that it's required. In the future a top level jsdoc config file could be used instead of the hack tempfile, but while it's only an experiment for chat, it's probably good enough.
2023-01-18 06:36:16 -05:00
mdurl@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/mdurl/-/mdurl-1.0.1.tgz#fe85b2ec75a59037f2adfec100fd6c601761152e"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
integrity sha512-/sKlQJCBYVY9Ers9hqzKou4H6V5UWc/M59TH2dvkt+84itfnq7uFOMLpOiOS4ujvHP4etln18fmIxA5R5fll0g==
DEV: Merge package.json files (#21172) This means: a single yarn.lock and removing one of the package.json files
2023-04-20 06:46:12 -04:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
merge-trees@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/merge-trees/-/merge-trees-2.0.0.tgz#a560d796e566c5d9b2c40472a2967cca48d85161"
integrity sha512-5xBbmqYBalWqmhYm51XlohhkmVOua3VAUrrWh8t9iOkaLpS6ifqm/UVuUjQCeDVJ9Vx3g2l6ihfkbLSTeKsHbw==
dependencies:
fs-updater "^1.0.4"
heimdalljs "^0.2.5"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
merge2@^1.3.0, merge2@^1.4.1:
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
version "1.4.1"
resolved "https://registry.yarnpkg.com/merge2/-/merge2-1.4.1.tgz#4368892f885e907455a6fd7dc55c0c9d404990ae"
integrity sha512-8q7VEgMJW4J8tcfVPy8g09NcQwZdbwFEqhe/WZkoIzjn/3TGDwtOCYtXGxA3O8tPzpczCCDgv+P2P5y00ZJOOg==
Support for Ember Template linting
2020-02-05 11:33:15 -05:00
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
micromatch@^4.0.4, micromatch@^4.0.5:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
version "4.0.5"
resolved "https://registry.yarnpkg.com/micromatch/-/micromatch-4.0.5.tgz#bc8999a7cbbf77cdc89f132f6e467051b49090c6"
integrity sha512-DMy+ERcEW2q8Z2Po+WNXuw3c5YaUSFjAO5GsJqfEl7UjvtIuFKO6ZrKvcItdy98dwFI2N1tg3zNIdKaQT+aNdA==
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
dependencies:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
braces "^3.0.2"
picomatch "^2.3.1"
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
mimic-fn@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/mimic-fn/-/mimic-fn-2.1.0.tgz#7ed2c2ccccaf84d3ffcb7a69b57711fc2083401b"
integrity sha512-OqbOk5oEQeAZ8WXWydlu9HJjz9WVdEIvamMCcXmuqUYjTknH/sqsWvhQ3vgwKFRR1HpjvNBKQ37nbJgYzGqGcg==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
"minimatch@2 || 3", minimatch@^3.0.0, minimatch@^3.0.2, minimatch@^3.0.4, minimatch@^3.0.5, minimatch@^3.1.1, minimatch@^3.1.2:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
version "3.1.2"
resolved "https://registry.yarnpkg.com/minimatch/-/minimatch-3.1.2.tgz#19cd194bfd3e428f049a70817c038d89ab4be35b"
integrity sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw==
Run JS test in chrome headless on Travis.
2017-12-14 21:15:04 -05:00
dependencies:
brace-expansion "^1.1.7"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
minimist@^1.2.6:
version "1.2.8"
resolved "https://registry.yarnpkg.com/minimist/-/minimist-1.2.8.tgz#c1a464e7693302e082a075cee0c057741ac4772c"
integrity sha512-2yyAR8qBkN3YuheJanUpWC5U3bb5osDywNB8RzDVlDwDHbocAJveqqj1u8+SVD7jkWT4yvsHCpWqqWqAxb0zCA==
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
mitt@3.0.1:
version "3.0.1"
resolved "https://registry.yarnpkg.com/mitt/-/mitt-3.0.1.tgz#ea36cf0cc30403601ae074c8f77b7092cdab36d1"
integrity sha512-vKivATfr97l2/QBCYAkXYDbrIWPM2IIKEl7YPhjCvKlG3kE2gm+uBo6nEXK3M5/Ffh/FLpKExzOQ3JJoJGFKBw==
DEV: Add uppy.js to build and project (#13645) This PR adds uppy to the project with a custom JS build and the shims needed to import it into our JS code. We need a custom build of Uppy because we do not use webpack for our JS modules/build. The only way to get what you want from Uppy is to use the webpack modules or to include the entire Uppy project including all plugins in a single JS file. This way we can just use the plugins we actually want. Future PRs will actually use Uppy!
2021-07-06 20:39:33 -04:00
mkdirp-classic@^0.5.2:
version "0.5.3"
resolved "https://registry.yarnpkg.com/mkdirp-classic/-/mkdirp-classic-0.5.3.tgz#fa10c9115cc6d8865be221ba47ee9bed78601113"
integrity sha512-gKLcREMhtuZRwRAfqP3RFW+TK4JqApVBtOIftVgjuABpAtpxhPGaDcfvbhNvD0B8iD1oUr/txX35NjcaY6Ns/A==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
mkdirp@^0.5.0, mkdirp@^0.5.1:
version "0.5.6"
resolved "https://registry.yarnpkg.com/mkdirp/-/mkdirp-0.5.6.tgz#7def03d2432dcae4ba1d611445c48396062255f6"
integrity sha512-FP+p8RB8OWpF3YZBCrP5gtADmtXApB5AMLn+vdyA+PyxCjrCs00mjyUozssO33cwDeT3wNGdLxJ5M//YqtHAJw==
dependencies:
minimist "^1.2.6"
DEV: introduces documentation for chat (#19772) Note this commit also slightly changes internal API: channel instead of getChannel and updateCurrentUserChannelNotificationsSettings instead of updateCurrentUserChatChannelNotificationsSettings. Also destroyChannel takes a second param which is the name confirmation instead of an optional object containing this confirmation. This is to enforce the fact that it's required. In the future a top level jsdoc config file could be used instead of the hack tempfile, but while it's only an experiment for chat, it's probably good enough.
2023-01-18 06:36:16 -05:00
mkdirp@^1.0.4:
version "1.0.4"
resolved "https://registry.yarnpkg.com/mkdirp/-/mkdirp-1.0.4.tgz#3eb5ed62622756d79a5f0e2a221dfebad75c2f7e"
integrity sha512-vVqVZQyf3WLx2Shd0qJ9xuvqgAyKPLAiqITEtqW0oIUjzo3PePDd6fW9iFz30ef7Ysp/oiWqbhszeGWW2T6Gzw==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
mktemp@~0.4.0:
version "0.4.0"
resolved "https://registry.yarnpkg.com/mktemp/-/mktemp-0.4.0.tgz#6d0515611c8a8c84e484aa2000129b98e981ff0b"
integrity sha512-IXnMcJ6ZyTuhRmJSjzvHSRhlVPiN9Jwc6e59V0bEJ0ba6OBeX2L0E+mRN1QseeOF4mM+F1Rit6Nh7o+rl2Yn/A==
DEV: Update moment-timezone (#22284)
2023-06-26 20:09:13 -04:00
moment-timezone@0.5.43:
version "0.5.43"
resolved "https://registry.yarnpkg.com/moment-timezone/-/moment-timezone-0.5.43.tgz#3dd7f3d0c67f78c23cd1906b9b2137a09b3c4790"
integrity sha512-72j3aNyuIsDxdF1i7CEgV2FfxM1r6aaqJyLB2vwb33mXYyoyLly+F1zbWqhA3/bVIoJ4szlUoMbUnVdid32NUQ==
DEV: Yarn-manage moment and moment-timezone libraries
2019-02-12 13:57:52 -05:00
dependencies:
DEV: Update moment-timezone (#22284)
2023-06-26 20:09:13 -04:00
moment "^2.29.4"
DEV: Yarn-manage moment and moment-timezone libraries
2019-02-12 13:57:52 -05:00
DEV: Update moment-timezone (#22284)
2023-06-26 20:09:13 -04:00
moment@2.29.4, moment@^2.29.4:
DEV: Update moment.js (#18207) Closes #18176
2022-09-12 04:56:39 -04:00
version "2.29.4"
resolved "https://registry.yarnpkg.com/moment/-/moment-2.29.4.tgz#3dbe052889fe7c1b2ed966fcb3a77328964ef108"
integrity sha512-5LC9SOxjSc2HF6vO2CyuTDNivEdoz2IvyJJGj6X8DJ0eFyfszE0QiEd+iXmBvUP3WHxSjFH/vIsA0EN00cgr8w==
DEV: Yarn-manage moment and moment-timezone libraries
2019-02-12 13:57:52 -05:00
Run JS test in chrome headless on Travis.
2017-12-14 21:15:04 -05:00
ms@2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/ms/-/ms-2.0.0.tgz#5608aeadfc00be6c2901df5f9861788de0d597c8"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-Tpp60P6IUJDTuOq/5Z8cdskzJujfwqfOTkrwIwj7IRISpnkJnT6SyJ4PCPnGMoFjC9ddhal5KVIYtAt97ix05A==
Run JS test in chrome headless on Travis.
2017-12-14 21:15:04 -05:00
DEV: Switch from puppeteer to puppeteer-core for smoke test (#15262) `puppeteer` includes a full chromium binary, which adds more than 300mb to our node_modules directory in development/test mode (and therefore the `discourse_dev` and `discourse_test` docker images). We already reach out to the system copy of Chrome for our qunit tests, and already have chrome installed in our `discourse_dev`/`discourse_test` docker images, so it's much more efficient to switch to `puppeteer-core` which doesn't include the chromium binary.
2021-12-13 04:31:49 -05:00
ms@2.1.2:
Build(deps): Bump https-proxy-agent from 2.2.1 to 2.2.4 (#9453) Bumps [https-proxy-agent](https://github.com/TooTallNate/node-https-proxy-agent) from 2.2.1 to 2.2.4. - [Release notes](https://github.com/TooTallNate/node-https-proxy-agent/releases) - [Commits](https://github.com/TooTallNate/node-https-proxy-agent/compare/2.2.1...2.2.4) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2020-04-17 11:31:11 -04:00
version "2.1.2"
resolved "https://registry.yarnpkg.com/ms/-/ms-2.1.2.tgz#d09d1f357b443f493382a8eb3ccd183872ae6009"
integrity sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==
Upgrade to FontAwesome 5 (take two) (#6673) * Add missing icons to set * Revert FA5 revert This reverts commit 42572ff * use new SVG syntax in locales * Noscript page changes (remove login button, center "powered by" footer text) * Cast wider net for SVG icons in settings - include any _icon setting for SVG registry (offers better support for plugin settings) - let themes store multiple pipe-delimited icons in a setting - also replaces broken onebox image icon with SVG reference in cooked post processor * interpolate icons in locales * Fix composer whisper icon alignment * Add support for stacked icons * SECURITY: enforce hostname to match discourse hostname This ensures that the hostname rails uses for various helpers always matches the Discourse hostname * load SVG sprite with pre-initializers * FIX: enable caching on SVG sprites * PERF: use JSONP for SVG sprites so they are served from CDN This avoids needing to deal with CORS for loading of the SVG Note, added the svg- prefix to the filename so we can quickly tell in dev tools what the file is * Add missing SVG sprite JSONP script to CSP * Upgrade to FA 5.5.0 * Add support for all FA4.7 icons - adds complete frontend and backend for renamed FA4.7 icons - improves performance of SvgSprite.bundle and SvgSprite.all_icons * Fix group avatar flair preview - adds an endpoint at /svg-sprites/search/:keyword - adds frontend ajax call that pulls icon in avatar flair preview even when it is not in subset * Remove FA 4.7 font files
2018-11-26 16:49:57 -05:00
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
natural-compare@^1.4.0:
version "1.4.0"
resolved "https://registry.yarnpkg.com/natural-compare/-/natural-compare-1.4.0.tgz#4abebfeed7541f2c27acfb29bdbbd15c8d5ba4f7"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-OWND8ei3VtNC9h7V60qff3SVobHr996CTwgxubgyQYEpg290h9J0buyECNNJexkFm5sOajh5G116RYA1c8ZMSw==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
netmask@^2.0.2:
version "2.0.2"
resolved "https://registry.yarnpkg.com/netmask/-/netmask-2.0.2.tgz#8b01a07644065d536383835823bc52004ebac5e7"
integrity sha512-dBpDMdxv9Irdq66304OLfEmQ9tbNRFnFTuZiLo+bD+r332bBmMJ8GBLXklIXXgxd3+v9+KUnZaUR5PJMa75Gsg==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
no-case@^3.0.4:
version "3.0.4"
resolved "https://registry.yarnpkg.com/no-case/-/no-case-3.0.4.tgz#d361fd5c9800f558551a8369fc0dcd4662b6124d"
integrity sha512-fgAN3jGAh+RoxUGZHTSOLJIqUc2wmoBwGR4tbpNAKmmovFoWq0OdRkb0VkldReO2a2iBT/OEulG9XSUc10r3zg==
DEV: Don't lint core files when target == plugins (#10259) * DEV: Don't lint core files when target == plugins * Prettier the plugin/*.js files * Update eslintignore/prettierignore * Add eslint-plugin-ember and eslint-plugin-node * Properly lint all js files in all plugins * LINT: run prettier on test/*.js files * DEV: Run prettier checks on test/*.js files * ESLint plugins' assets/javascripts and test/javascripts directories only
2020-08-25 05:40:40 -04:00
dependencies:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
lower-case "^2.0.2"
tslib "^2.0.3"
DEV: Don't lint core files when target == plugins (#10259) * DEV: Don't lint core files when target == plugins * Prettier the plugin/*.js files * Update eslintignore/prettierignore * Add eslint-plugin-ember and eslint-plugin-node * Properly lint all js files in all plugins * LINT: run prettier on test/*.js files * DEV: Run prettier checks on test/*.js files * ESLint plugins' assets/javascripts and test/javascripts directories only
2020-08-25 05:40:40 -04:00
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
node-fetch@^2.6.0, node-fetch@^2.6.12:
Revert "DEV: FloatKit (#23541)" (#23549) This reverts commits 0623ac684a65f95ce4f5438ff47944b1dc2119f4 408e71e437ef8abf98f93e3449898bf906766b0e a32fa3b9470dde0543fcee809f2abd1f219f7336 User tips were running into some issues.
2023-09-12 13:55:12 -04:00
version "2.6.12"
resolved "https://registry.yarnpkg.com/node-fetch/-/node-fetch-2.6.12.tgz#02eb8e22074018e3d5a83016649d04df0e348fba"
integrity sha512-C/fGU2E8ToujUivIO0H+tpQ6HWo4eEmchoPIoXtxCrVghxdKq+QOHqEZW7tuP3KlV3bC8FRMO5nMCC7Zm1VP6g==
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
dependencies:
whatwg-url "^5.0.0"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
node-releases@^2.0.13:
version "2.0.13"
resolved "https://registry.yarnpkg.com/node-releases/-/node-releases-2.0.13.tgz#d5ed1627c23e3461e819b02e57b75e4899b1c81d"
integrity sha512-uYr7J37ae/ORWdZeQ1xxMJe3NtdmqMC/JZK+geofDrkLUApKRHPd18/TxtBOJ4A0/+uUIliorNrfYV6s1b02eQ==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
object-assign@^4.1.0:
version "4.1.1"
resolved "https://registry.yarnpkg.com/object-assign/-/object-assign-4.1.1.tgz#2109adc7965887cfc05cbbd442cac8bfbb360863"
integrity sha512-rJgTQnkUnH1sFw8yT6VSU3zD3sWmu6sZhIseY8VX+GRu3P6F7Fu+JNDoXfklElbLJSnc3FUQHVe4cU5hj+BcUg==
object-inspect@^1.12.3, object-inspect@^1.9.0:
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
version "1.13.0"
resolved "https://registry.yarnpkg.com/object-inspect/-/object-inspect-1.13.0.tgz#42695d3879e1cd5bda6df5062164d80c996e23e2"
integrity sha512-HQ4J+ic8hKrgIt3mqk6cVOVrW2ozL4KdvHlqpBv9vDYWx9ysAgENAdvy4FoGF+KFdhR7nQTNm5J0ctAeOwn+3g==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
object-keys@^1.1.1:
version "1.1.1"
resolved "https://registry.yarnpkg.com/object-keys/-/object-keys-1.1.1.tgz#1c47f272df277f3b1daf061677d9c82e2322c60e"
integrity sha512-NuAESUOUMrlIXOfHKzD6bpPu3tYt3xvjNdRIQ+FeT0lNb4K8WR70CaDxhuNguS2XG+GjkyMwOzsN5ZktImfhLA==
object.assign@^4.1.4:
version "4.1.4"
resolved "https://registry.yarnpkg.com/object.assign/-/object.assign-4.1.4.tgz#9673c7c7c351ab8c4d0b516f4343ebf4dfb7799f"
integrity sha512-1mxKf0e58bvyjSCtKYY4sRe9itRk3PJpquJOjeIkz885CczcI4IvJJDLPS72oowuSh+pBxUFROpX+TU++hxhZQ==
dependencies:
call-bind "^1.0.2"
define-properties "^1.1.4"
has-symbols "^1.0.3"
object-keys "^1.1.1"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
DEV: upgrades from Ember 2.13 to Ember 3.5.1 (#6808) Co-Authored-By: Bianca Nenciu <nbianca@users.noreply.github.com> Co-Authored-By: David Taylor <david@taylorhq.com>
2019-01-10 05:06:01 -05:00
once@^1.3.0, once@^1.3.1, once@^1.4.0:
Run JS test in chrome headless on Travis.
2017-12-14 21:15:04 -05:00
version "1.4.0"
resolved "https://registry.yarnpkg.com/once/-/once-1.4.0.tgz#583b1aa775961d4b113ac17d9c50baef9dd76bd1"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-lNaJgI+2Q5URQBkccEKHTQOPaXdUxnZZElQTZY0MFUAuaEqe1E+Nyvgdz/aIyNi6Z9MzO5dv1H8n58/GELp3+w==
Run JS test in chrome headless on Travis.
2017-12-14 21:15:04 -05:00
dependencies:
wrappy "1"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
onetime@^5.1.0:
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
version "5.1.2"
resolved "https://registry.yarnpkg.com/onetime/-/onetime-5.1.2.tgz#d0e96ebb56b07476df1dd9c4806e5237985ca45e"
integrity sha512-kbpaSSGJTWdAY5KPVeMOKXSrPtr8C8C7wodJbcsd51jRnmD+GZu8Y0VoU6Dm5Z4vWr0Ig/1NKuWRKf7j5aaYSg==
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
dependencies:
mimic-fn "^2.1.0"
DEV: Consolidate and update jsconfig, and add types packages (#23824) These updates significantly improve IDE tooling for imports across the Discourse core codebase, and also for framework packages. The `@types/ember-*` packages are a temporary solution until we get onto Ember 5, which ships its types in the main package. The previous approach of having jsconfig files in each package directory did work, but once you start adding all the possible interlinks between them, we hit the file count limit of VSCode's tooling (because it counts every file for every jsconfig its referenced in). Having one file at the root means that a single file can apply to all core packages and plugins. Long-term, to get the same functionality for all themes/plugins, we may need to look at building/publishing a Discourse types package which can be added to theme/plugin package.json files for development purposes.
2023-10-18 07:13:20 -04:00
optionator@^0.9.3:
DEV: Update sub-dependencies (#22325) Achieved by running `yarn upgrade --latest` both yarn.lock directories, then reverting changes to package.json files and running `yarn` again. I also de-duped yarn.lock files with `npx yarn-deduplicate && yarn`
2023-06-29 11:08:33 -04:00
version "0.9.3"
resolved "https://registry.yarnpkg.com/optionator/-/optionator-0.9.3.tgz#007397d44ed1872fdc6ed31360190f81814e2c64"
integrity sha512-JjCoypp+jKn1ttEFExxhetCKeJt9zhAgAve5FXHixTvFDW/5aEktX9bufBKLRRMdU7bNtpLfcGu94B3cdEJgjg==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
dependencies:
DEV: Update sub-dependencies (#22325) Achieved by running `yarn upgrade --latest` both yarn.lock directories, then reverting changes to package.json files and running `yarn` again. I also de-duped yarn.lock files with `npx yarn-deduplicate && yarn`
2023-06-29 11:08:33 -04:00
"@aashutoshrathi/word-wrap" "^1.2.3"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
deep-is "^0.1.3"
fast-levenshtein "^2.0.6"
levn "^0.4.1"
prelude-ls "^1.2.1"
type-check "^0.4.0"
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
ora@^5.3.0, ora@^5.4.0:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
version "5.4.1"
resolved "https://registry.yarnpkg.com/ora/-/ora-5.4.1.tgz#1b2678426af4ac4a509008e5e4ac9e9959db9e18"
integrity sha512-5b6Y85tPxZZ7QytO+BQzysW31HJku27cRIlkbAXaNx+BdcVi+LlRFmVXzeF6a7JCwJpyw5c4b+YSVImQIrBpuQ==
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
dependencies:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
bl "^4.1.0"
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
chalk "^4.1.0"
cli-cursor "^3.1.0"
cli-spinners "^2.5.0"
is-interactive "^1.0.0"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
is-unicode-supported "^0.1.0"
log-symbols "^4.1.0"
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
strip-ansi "^6.0.0"
wcwidth "^1.0.1"
DEV: Bump `@mixer/parallel-prettier` (#19053)
2022-11-16 15:38:57 -05:00
ordered-read-streams@^1.0.1:
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
version "1.0.1"
resolved "https://registry.yarnpkg.com/ordered-read-streams/-/ordered-read-streams-1.0.1.tgz#77c0cb37c41525d64166d990ffad7ec6a0e1363e"
DEV: Bump `@mixer/parallel-prettier` (#19053)
2022-11-16 15:38:57 -05:00
integrity sha512-Z87aSjx3r5c0ZB7bcJqIgIRX5bxR7A4aSzvIbaxd0oTkWBCOoKfuGHiKj60CHVUgg1Phm5yMZzBdt8XqRs73Mw==
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
dependencies:
readable-stream "^2.0.1"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
os-tmpdir@~1.0.1:
version "1.0.2"
resolved "https://registry.yarnpkg.com/os-tmpdir/-/os-tmpdir-1.0.2.tgz#bbe67406c79aa85c5cfec766fe5734555dfa1274"
integrity sha512-D2FR03Vir7FIu45XBY20mTb+/ZSWB00sjU9jdQXt83gDrI4Ztz5Fs7/yy74g2N5SVQY4xY1qDr4rNddwYRVX0g==
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
p-limit@^3.0.2:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "3.1.0"
resolved "https://registry.yarnpkg.com/p-limit/-/p-limit-3.1.0.tgz#e1daccbe78d0d1388ca18c64fea38e3e57e3706b"
integrity sha512-TYOanM3wGwNGsZN2cVTYPArw454xnXj5qmWF1bEoAc4+cU/ol7GVh7odevjp1FNHduHc3KZMcFduxU5Xc6uJRQ==
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
dependencies:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
yocto-queue "^0.1.0"
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
p-limit@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/p-limit/-/p-limit-4.0.0.tgz#914af6544ed32bfa54670b061cafcbd04984b644"
integrity sha512-5b0R4txpzjPWVw/cXXUResoD4hb6U/x9BH08L7nw+GN1sezDzPdxeRvpc9c433fZhBan/wusjbCsqwqm4EIBIQ==
dependencies:
yocto-queue "^1.0.0"
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
p-locate@^5.0.0:
version "5.0.0"
resolved "https://registry.yarnpkg.com/p-locate/-/p-locate-5.0.0.tgz#83c8315c6785005e3bd021839411c9e110e6d834"
integrity sha512-LaNjtRWUBY++zB5nE/NwcaoMylSPk+S+ZHNB1TzdbMJMny6dynpAGt7X/tl/QYq3TIeE6nxHppbo2LGymrG5Pw==
dependencies:
p-limit "^3.0.2"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
p-locate@^6.0.0:
version "6.0.0"
resolved "https://registry.yarnpkg.com/p-locate/-/p-locate-6.0.0.tgz#3da9a49d4934b901089dca3302fa65dc5a05c04f"
integrity sha512-wPrq66Llhl7/4AGC6I+cqxT07LhXvWL08LNXz1fENOw0Ap4sRZZ/gZpTTJ5jpurzzzfS2W/Ge9BY3LgLjCShcw==
dependencies:
p-limit "^4.0.0"
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
pac-proxy-agent@^7.0.0:
Revert "DEV: FloatKit (#23541)" (#23549) This reverts commits 0623ac684a65f95ce4f5438ff47944b1dc2119f4 408e71e437ef8abf98f93e3449898bf906766b0e a32fa3b9470dde0543fcee809f2abd1f219f7336 User tips were running into some issues.
2023-09-12 13:55:12 -04:00
version "7.0.0"
resolved "https://registry.yarnpkg.com/pac-proxy-agent/-/pac-proxy-agent-7.0.0.tgz#db42120c64292685dafaf2bd921e223c56bfb13b"
integrity sha512-t4tRAMx0uphnZrio0S0Jw9zg3oDbz1zVhQ/Vy18FjLfP1XOLNUEjaVxYCYRI6NS+BsMBXKIzV6cTLOkO9AtywA==
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
dependencies:
"@tootallnate/quickjs-emscripten" "^0.23.0"
agent-base "^7.0.2"
debug "^4.3.4"
get-uri "^6.0.1"
http-proxy-agent "^7.0.0"
Revert "DEV: FloatKit (#23541)" (#23549) This reverts commits 0623ac684a65f95ce4f5438ff47944b1dc2119f4 408e71e437ef8abf98f93e3449898bf906766b0e a32fa3b9470dde0543fcee809f2abd1f219f7336 User tips were running into some issues.
2023-09-12 13:55:12 -04:00
https-proxy-agent "^7.0.0"
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
pac-resolver "^7.0.0"
Revert "DEV: FloatKit (#23541)" (#23549) This reverts commits 0623ac684a65f95ce4f5438ff47944b1dc2119f4 408e71e437ef8abf98f93e3449898bf906766b0e a32fa3b9470dde0543fcee809f2abd1f219f7336 User tips were running into some issues.
2023-09-12 13:55:12 -04:00
socks-proxy-agent "^8.0.1"
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
pac-resolver@^7.0.0:
version "7.0.0"
resolved "https://registry.yarnpkg.com/pac-resolver/-/pac-resolver-7.0.0.tgz#79376f1ca26baf245b96b34c339d79bff25e900c"
integrity sha512-Fd9lT9vJbHYRACT8OhCbZBbxr6KRSawSovFpy8nDGshaK99S/EBhVIHp9+crhxrsZOuvLpgL1n23iyPg6Rl2hg==
dependencies:
degenerator "^5.0.0"
ip "^1.1.8"
netmask "^2.0.2"
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
parent-module@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/parent-module/-/parent-module-1.0.1.tgz#691d2709e78c79fae3a156622452d00762caaaa2"
integrity sha512-GQ2EWRpQV8/o+Aw8YqtfZZPfNRWZYkbidE9k5rpl/hC3vtHHBfGm2Ifi6qWV+coDGkrUKZAxE3Lot5kcsRlh+g==
dependencies:
callsites "^3.0.0"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
parse-static-imports@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/parse-static-imports/-/parse-static-imports-1.1.0.tgz#ae2f18f18da1a993080ae406a5219455c0bbad5d"
integrity sha512-HlxrZcISCblEV0lzXmAHheH/8qEkKgmqkdxyHTPbSqsTUV8GzqmN1L+SSti+VbNPfbBO3bYLPHDiUs2avbAdbA==
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
path-exists@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/path-exists/-/path-exists-4.0.0.tgz#513bdbe2d3b95d7762e8c1137efa195c6c61b5b3"
integrity sha512-ak9Qy5Q7jYb2Wwcey5Fpvg2KoAc/ZIhLSLOSBmRmygPsGwkVVt0fZa0qrtMz+m6tJTAHfZQ8FnmB4MG4LWy7/w==
Support for Ember Template linting
2020-02-05 11:33:15 -05:00
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
path-exists@^5.0.0:
version "5.0.0"
resolved "https://registry.yarnpkg.com/path-exists/-/path-exists-5.0.0.tgz#a6aad9489200b21fab31e49cf09277e5116fb9e7"
integrity sha512-RjhtfwJOxzcFmNOi6ltcbcu4Iu+FL3zEj83dk4kAS+fVpTxXLO1b38RvJgT/0QwvV/L3aY9TAnyv0EOqW4GoMQ==
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
path-is-absolute@^1.0.0:
Run JS test in chrome headless on Travis.
2017-12-14 21:15:04 -05:00
version "1.0.1"
resolved "https://registry.yarnpkg.com/path-is-absolute/-/path-is-absolute-1.0.1.tgz#174b9268735534ffbc7ace6bf53a5a9e1b5c5f5f"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-AVbw3UJ2e9bq64vSaS9Am0fje1Pa8pbGqTTsmXfaIiMpnr5DlDhfJOuLj9Sf95ZPVDAUerDfEk88MPmPe7UCQg==
Run JS test in chrome headless on Travis.
2017-12-14 21:15:04 -05:00
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
path-key@^3.1.0:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
version "3.1.1"
resolved "https://registry.yarnpkg.com/path-key/-/path-key-3.1.1.tgz#581f6ade658cbba65a0d3380de7753295054f375"
integrity sha512-ojmeN0qd+y0jszEtoY48r0Peq5dwMEkIlCOu6Q5f41lfkswXuKtYrhgoTpLnyIcHm24Uhqx+5Tqm2InSwLhE6Q==
DEV: upgrades from Ember 2.13 to Ember 3.5.1 (#6808) Co-Authored-By: Bianca Nenciu <nbianca@users.noreply.github.com> Co-Authored-By: David Taylor <david@taylorhq.com>
2019-01-10 05:06:01 -05:00
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
path-parse@^1.0.7:
version "1.0.7"
resolved "https://registry.yarnpkg.com/path-parse/-/path-parse-1.0.7.tgz#fbc114b60ca42b30d9daf5858e4bd68bbedb6735"
integrity sha512-LDJzPVEEEPR+y48z93A0Ed0yXb8pAByGWo/k5YYdYgpY2/2EsOsksJrq7lOHxryrVOn1ejG6oAp8ahvOIQD8sw==
Manage qunit via yarn.
2018-09-11 03:07:28 -04:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
path-posix@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/path-posix/-/path-posix-1.0.0.tgz#06b26113f56beab042545a23bfa88003ccac260f"
integrity sha512-1gJ0WpNIiYcQydgg3Ed8KzvIqTsDpNwq+cjBCssvBtuTWjEqY1AW+i+OepiEMqDCzyro9B2sLAe4RBPajMYFiA==
path-root-regex@^0.1.0:
version "0.1.2"
resolved "https://registry.yarnpkg.com/path-root-regex/-/path-root-regex-0.1.2.tgz#bfccdc8df5b12dc52c8b43ec38d18d72c04ba96d"
integrity sha512-4GlJ6rZDhQZFE0DPVKh0e9jmZ5egZfxTkp7bcRDuPlJXbAwhxcl2dINPUAsjLdejqaLsCeg8axcLjIbvBjN4pQ==
path-root@^0.1.1:
version "0.1.1"
resolved "https://registry.yarnpkg.com/path-root/-/path-root-0.1.1.tgz#9a4a6814cac1c0cd73360a95f32083c8ea4745b7"
integrity sha512-QLcPegTHF11axjfojBIoDygmS2E3Lf+8+jI6wOVmNVenrKSo3mFdSGiIgdSHenczw3wPtlVMQaFVwGmM7BJdtg==
dependencies:
path-root-regex "^0.1.0"
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
path-type@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/path-type/-/path-type-4.0.0.tgz#84ed01c0a7ba380afe09d90a8c180dcd9d03043b"
integrity sha512-gDKb8aZMDeD/tZWs9P6+q0J9Mwkdl6xMV8TjnGP3qJVJ06bdMgkbBlLU8IdfOsIsFz2BW1rNVT3XuNEl8zPAvw==
Support for Ember Template linting
2020-02-05 11:33:15 -05:00
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
pathval@^1.1.1:
version "1.1.1"
resolved "https://registry.yarnpkg.com/pathval/-/pathval-1.1.1.tgz#8534e77a77ce7ac5a2512ea21e0fdb8fcf6c3d8d"
integrity sha512-Dp6zGqpTdETdR63lehJYPeIOqpiNBNtc7BpWSLrOje7UaIsE5aY92r/AunQA7rsXvet3lrJ3JnZX29UPTKXyKQ==
Add smoke test script that runs in chrome headless.
2017-12-18 03:32:58 -05:00
pend@~1.2.0:
version "1.2.0"
resolved "https://registry.yarnpkg.com/pend/-/pend-1.2.0.tgz#7a57eb550a6783f9115331fcf4663d5c8e007a50"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-F3asv42UuXchdzt+xXqfW1OGlVBe+mxa2mqI0pg5yAHZPvFmY3Y6drSf/GQ1A86WgWEN9Kzh/WrgKa6iGcHXLg==
Add smoke test script that runs in chrome headless.
2017-12-18 03:32:58 -05:00
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
picocolors@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/picocolors/-/picocolors-1.0.0.tgz#cb5bdc74ff3f51892236eaf79d68bc44564ab81c"
integrity sha512-1fygroTLlHu66zi26VoTDv8yRgm0Fccecssto+MhsZ0D/DGW2sm8E8AjW7NU5VVTRt5GxbeZ5qBuJr+HyLYkjQ==
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
picomatch@^2.3.1:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
version "2.3.1"
resolved "https://registry.yarnpkg.com/picomatch/-/picomatch-2.3.1.tgz#3ba3833733646d9d3e4995946c1365a67fb07a42"
integrity sha512-JU3teHTNjmE2VCGFzuY8EXzCDVwEqB2a8fsIvwaStHhAWJEeVd1o1QD80CU6+ZdEXXSLbSsuLwJjkCBWqRQUVA==
Support for Ember Template linting
2020-02-05 11:33:15 -05:00
DEV: Bump pikaday (#19060)
2022-11-16 12:59:15 -05:00
pikaday@1.8.2:
version "1.8.2"
resolved "https://registry.yarnpkg.com/pikaday/-/pikaday-1.8.2.tgz#72cc73fab7ccc068cbdf7dcaa1ce400fcfd894e3"
integrity sha512-TNtsE+34BIax3WtkB/qqu5uepV1McKYEgvL3kWzU7aqPCpMEN6rBF3AOwu4WCwAealWlBGobXny/9kJb49C1ew==
Use Yarn to manage dependencies, cleanup unused bootstrap libs (#6436)
2018-10-03 10:15:43 -04:00
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
prelude-ls@^1.2.1:
version "1.2.1"
resolved "https://registry.yarnpkg.com/prelude-ls/-/prelude-ls-1.2.1.tgz#debc6489d7a6e6b0e7611888cec880337d316396"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
integrity sha512-vkcDPrRZo1QZLbn5RLGPpg/WmIQ65qoWWhcGKf/b5eplkkarX0m9z8ppCat4mlOqUsWpyNuYgO3VRyrYHSzX5g==
DEV: Merge package.json files (#21172) This means: a single yarn.lock and removing one of the package.json files
2023-04-20 06:46:12 -04:00
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
prettier-plugin-ember-template-tag@^0.3.2:
version "0.3.2"
resolved "https://registry.yarnpkg.com/prettier-plugin-ember-template-tag/-/prettier-plugin-ember-template-tag-0.3.2.tgz#dcf4e402951d6766a9880308ea6a405c9ea5a5f1"
integrity sha512-L/15ujsvuOpuIB9y9XJJs/QOPgdot76T0U1Q34C19igS1lsaL/cdRw8rXIVC5Z2x362yZI33Qodo//7kK7ItkA==
dependencies:
"@babel/core" "^7.20.12"
"@glimmer/syntax" "^0.84.2"
ember-cli-htmlbars "^6.2.0"
ember-template-imports "^3.4.1"
prettier "^2.8.3"
ts-replace-all "^1.0.0"
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
prettier@^2.0.4, prettier@^2.8.3, prettier@^2.8.8:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "2.8.8"
resolved "https://registry.yarnpkg.com/prettier/-/prettier-2.8.8.tgz#e8c5d7e98a4305ffe3de2e1fc4aca1a71c28b1da"
integrity sha512-tdN8qQGvNjw4CHbY+XXk0JgCXn9QiF21a55rBe5LJAU+kDyC4WQn4+awm2Xfk2lQMk5fKup9XgzTZtGkjBdP9Q==
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
Manage qunit via yarn.
2018-09-11 03:07:28 -04:00
process-nextick-args@~2.0.0:
Update javascripts (#9907)
2020-05-28 12:15:13 -04:00
version "2.0.1"
resolved "https://registry.yarnpkg.com/process-nextick-args/-/process-nextick-args-2.0.1.tgz#7820d9b16120cc55ca9ae7792680ae7dba6d7fe2"
integrity sha512-3ouUOpQhtgrbOa17J7+uxOTpITYWaGP7/AhoR3+A+/1e9skrzelGi/dXzEYyvbxubEF6Wn2ypscTKiKJFFn1ag==
Manage qunit via yarn.
2018-09-11 03:07:28 -04:00
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
progress@2.0.3:
DEV: Fix the smoke test
2019-05-21 13:01:29 -04:00
version "2.0.3"
resolved "https://registry.yarnpkg.com/progress/-/progress-2.0.3.tgz#7e8cf8d8f5b8f239c1bc68beb4eb78567d572ef8"
integrity sha512-7PiHtLll5LdnKIMw100I+8xJXR5gW2QwWYkT6iJva0bXitZKa/XMrSbdmg3r2Xnaidz9Qumd0VPaMrZlF9V9sA==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
promise-map-series@^0.2.1:
version "0.2.3"
resolved "https://registry.yarnpkg.com/promise-map-series/-/promise-map-series-0.2.3.tgz#c2d377afc93253f6bd03dbb77755eb88ab20a847"
integrity sha512-wx9Chrutvqu1N/NHzTayZjE1BgIwt6SJykQoCOic4IZ9yUDjKyVYrpLa/4YCNsV61eRENfs29hrEquVuB13Zlw==
dependencies:
rsvp "^3.0.14"
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
promise-map-series@^0.3.0:
version "0.3.0"
resolved "https://registry.yarnpkg.com/promise-map-series/-/promise-map-series-0.3.0.tgz#41873ca3652bb7a042b387d538552da9b576f8a1"
integrity sha512-3npG2NGhTc8BWBolLLf8l/92OxMGaRLbqvIh9wjCHhDXNvk4zsxaTaCpiCunW09qWPrN2zeNSNwRLVBrQQtutA==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
proper-lockfile@^4.1.2:
version "4.1.2"
resolved "https://registry.yarnpkg.com/proper-lockfile/-/proper-lockfile-4.1.2.tgz#c8b9de2af6b2f1601067f98e01ac66baa223141f"
integrity sha512-TjNPblN4BwAWMXU8s9AEz4JmQxnD1NNL7bNOY/AKUzyamc379FWASUhc/K1pL2noVb+XmZKLL68cjzLsiOAMaA==
dependencies:
graceful-fs "^4.2.4"
retry "^0.12.0"
signal-exit "^3.0.2"
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
proxy-agent@6.3.0:
version "6.3.0"
resolved "https://registry.yarnpkg.com/proxy-agent/-/proxy-agent-6.3.0.tgz#72f7bb20eb06049db79f7f86c49342c34f9ba08d"
integrity sha512-0LdR757eTj/JfuU7TL2YCuAZnxWXu3tkJbg4Oq3geW/qFNT/32T0sp2HnZ9O0lMR4q3vwAt0+xCA8SR0WAD0og==
dependencies:
agent-base "^7.0.2"
debug "^4.3.4"
http-proxy-agent "^7.0.0"
https-proxy-agent "^7.0.0"
lru-cache "^7.14.1"
pac-proxy-agent "^7.0.0"
proxy-from-env "^1.1.0"
socks-proxy-agent "^8.0.1"
proxy-from-env@^1.1.0:
Update javascripts (#9907)
2020-05-28 12:15:13 -04:00
version "1.1.0"
resolved "https://registry.yarnpkg.com/proxy-from-env/-/proxy-from-env-1.1.0.tgz#e102f16ca355424865755d2c9e8ea4f24d58c3e2"
integrity sha512-D+zkORCbA9f1tdWRK0RaCR3GPv50cMxcrz4X8k5LTSUD1Dkw47mKJEZQNunItRTkWwgtaUSo1RVFRIG9ZXiFYg==
Add smoke test script that runs in chrome headless.
2017-12-18 03:32:58 -05:00
DEV: upgrades from Ember 2.13 to Ember 3.5.1 (#6808) Co-Authored-By: Bianca Nenciu <nbianca@users.noreply.github.com> Co-Authored-By: David Taylor <david@taylorhq.com>
2019-01-10 05:06:01 -05:00
pump@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/pump/-/pump-3.0.0.tgz#b4a2116815bde2f4e1ea602354e8c75565107a64"
integrity sha512-LwZy+p3SFs1Pytd/jYct4wpv49HiYCqd9Rlc5ZVdk0V+8Yzv6jR5Blk3TRmPL1ft69TxP0IMZGJ+WPFU2BFhww==
dependencies:
end-of-stream "^1.1.0"
once "^1.3.1"
DEV: Bump `@mixer/parallel-prettier` (#19053)
2022-11-16 15:38:57 -05:00
pumpify@^2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/pumpify/-/pumpify-2.0.1.tgz#abfc7b5a621307c728b551decbbefb51f0e4aa1e"
integrity sha512-m7KOje7jZxrmutanlkS1daj1dS6z6BgslzOXmcSEpIlCxM3VJH7lG5QLeck/6hgF6F4crFf01UtQmNsJfweTAw==
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
dependencies:
DEV: Bump `@mixer/parallel-prettier` (#19053)
2022-11-16 15:38:57 -05:00
duplexify "^4.1.1"
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
inherits "^2.0.3"
DEV: Bump `@mixer/parallel-prettier` (#19053)
2022-11-16 15:38:57 -05:00
pump "^3.0.0"
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
punycode@^2.1.0:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "2.3.0"
resolved "https://registry.yarnpkg.com/punycode/-/punycode-2.3.0.tgz#f67fa67c94da8f4d0cfff981aee4118064199b8f"
integrity sha512-rRV+zQD8tVFys26lAGR9WUuS4iUAngJScM+ZRSKtvl5tKeZ2t5bvdNFdNHBW9FWR4guGHlgmsZ1G7BSm2wTbuA==
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
puppeteer-core@^21.0.3:
Revert "DEV: FloatKit (#23541)" (#23549) This reverts commits 0623ac684a65f95ce4f5438ff47944b1dc2119f4 408e71e437ef8abf98f93e3449898bf906766b0e a32fa3b9470dde0543fcee809f2abd1f219f7336 User tips were running into some issues.
2023-09-12 13:55:12 -04:00
version "21.0.3"
resolved "https://registry.yarnpkg.com/puppeteer-core/-/puppeteer-core-21.0.3.tgz#201bfbf18a9467dbedb10c3c2c9c43462bb9bb84"
integrity sha512-AGvopfkA0jLbW5Ba0m6kBuvRIpLo76PXUK3zJYkXOr9NI1LknJESyai6TtXc6GUSewMkinmyEDx1pFgq900hqg==
DEV: Switch from puppeteer to puppeteer-core for smoke test (#15262) `puppeteer` includes a full chromium binary, which adds more than 300mb to our node_modules directory in development/test mode (and therefore the `discourse_dev` and `discourse_test` docker images). We already reach out to the system copy of Chrome for our qunit tests, and already have chrome installed in our `discourse_dev`/`discourse_test` docker images, so it's much more efficient to switch to `puppeteer-core` which doesn't include the chromium binary.
2021-12-13 04:31:49 -05:00
dependencies:
Revert "DEV: FloatKit (#23541)" (#23549) This reverts commits 0623ac684a65f95ce4f5438ff47944b1dc2119f4 408e71e437ef8abf98f93e3449898bf906766b0e a32fa3b9470dde0543fcee809f2abd1f219f7336 User tips were running into some issues.
2023-09-12 13:55:12 -04:00
"@puppeteer/browsers" "1.6.0"
chromium-bidi "0.4.20"
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
cross-fetch "4.0.0"
DEV: Update puppeteer, fix deprecations, lint (#16616) 1. Updates puppeteer to x 2. Fixes deprecations: ``` waitFor is deprecated and will be removed in a future release. See https://github.com/puppeteer/puppeteer/issues/6214 for details and how to migrate your code. ``` 3. Lints/prettyfies the smoke_test.js file
2022-05-03 14:58:58 -04:00
debug "4.3.4"
Revert "DEV: FloatKit (#23541)" (#23549) This reverts commits 0623ac684a65f95ce4f5438ff47944b1dc2119f4 408e71e437ef8abf98f93e3449898bf906766b0e a32fa3b9470dde0543fcee809f2abd1f219f7336 User tips were running into some issues.
2023-09-12 13:55:12 -04:00
devtools-protocol "0.0.1147663"
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
ws "8.13.0"
Add smoke test script that runs in chrome headless.
2017-12-18 03:32:58 -05:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
queue-microtask@^1.2.2:
version "1.2.3"
resolved "https://registry.yarnpkg.com/queue-microtask/-/queue-microtask-1.2.3.tgz#4929228bbc724dfac43e0efb058caf7b6cfb6243"
integrity sha512-NuaNSa6flKT5JaSYQzJok04JzTL1CA6aGhv5rfLW3PgqA+M2ChpZQnAC8h8i4ZFkBS8X5RqkDBHA7r4hej3K9A==
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
queue-tick@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/queue-tick/-/queue-tick-1.0.1.tgz#f6f07ac82c1fd60f82e098b417a80e52f1f4c142"
integrity sha512-kJt5qhMxoszgU/62PLP1CJytzd2NKetjSRnyuj31fDd3Rlcz3fzlFdFLD1SItunPwyqEOkca6GbV612BWfaBag==
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
quick-temp@^0.1.3, quick-temp@^0.1.5, quick-temp@^0.1.8:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "0.1.8"
resolved "https://registry.yarnpkg.com/quick-temp/-/quick-temp-0.1.8.tgz#bab02a242ab8fb0dd758a3c9776b32f9a5d94408"
integrity sha512-YsmIFfD9j2zaFwJkzI6eMG7y0lQP7YeWzgtFgNl38pGWZBSXJooZbOWwkcRot7Vt0Fg9L23pX0tqWU3VvLDsiA==
dependencies:
mktemp "~0.4.0"
rimraf "^2.5.4"
underscore.string "~3.3.4"
DEV: Bump `@mixer/parallel-prettier` (#19053)
2022-11-16 15:38:57 -05:00
readable-stream@^2.0.1, readable-stream@~2.3.6:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "2.3.8"
resolved "https://registry.yarnpkg.com/readable-stream/-/readable-stream-2.3.8.tgz#91125e8042bba1b9887f49345f6277027ce8be9b"
integrity sha512-8p0AUk4XODgIewSi0l8Epjs+EVnWiK7NoDIEGU0HhE7+ZyY8D1IMY7odu5lRrFXGg71L15KG8QrPmum45RTtdA==
Manage qunit via yarn.
2018-09-11 03:07:28 -04:00
dependencies:
core-util-is "~1.0.0"
inherits "~2.0.3"
isarray "~1.0.0"
process-nextick-args "~2.0.0"
safe-buffer "~5.1.1"
string_decoder "~1.1.1"
util-deprecate "~1.0.1"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
readable-stream@^3.1.1, readable-stream@^3.4.0, readable-stream@^3.6.0:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "3.6.2"
resolved "https://registry.yarnpkg.com/readable-stream/-/readable-stream-3.6.2.tgz#56a9b36ea965c00c5a93ef31eb111a0f11056967"
integrity sha512-9u/sniCrY3D5WdsERHzHE4G2YCXqoG5FTHUiCC4SIbr6XcLZBY05ya9EKjYek9O5xOAwjGq+1JdGBAS7Q9ScoA==
DEV: Merge package.json files (#21172) This means: a single yarn.lock and removing one of the package.json files
2023-04-20 06:46:12 -04:00
dependencies:
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
inherits "^2.0.3"
string_decoder "^1.1.1"
util-deprecate "^1.0.1"
DEV: Merge package.json files (#21172) This means: a single yarn.lock and removing one of the package.json files
2023-04-20 06:46:12 -04:00
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
regenerator-runtime@^0.14.0:
version "0.14.0"
resolved "https://registry.yarnpkg.com/regenerator-runtime/-/regenerator-runtime-0.14.0.tgz#5e19d68eb12d486f797e15a3c6a918f7cec5eb45"
integrity sha512-srw17NI0TUWHuGa5CFGGmhfNIeja30WMBfbslPNhf6JrqQlLN5gcrvig1oqPxiVaXb0oW0XRKtH6Nngs5lKCIA==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
DEV: Consolidate and update jsconfig, and add types packages (#23824) These updates significantly improve IDE tooling for imports across the Discourse core codebase, and also for framework packages. The `@types/ember-*` packages are a temporary solution until we get onto Ember 5, which ships its types in the main package. The previous approach of having jsconfig files in each package directory did work, but once you start adding all the possible interlinks between them, we hit the file count limit of VSCode's tooling (because it counts every file for every jsconfig its referenced in). Having one file at the root means that a single file can apply to all core packages and plugins. Long-term, to get the same functionality for all themes/plugins, we may need to look at building/publishing a Discourse types package which can be added to theme/plugin package.json files for development purposes.
2023-10-18 07:13:20 -04:00
regexp.prototype.flags@^1.5.0, regexp.prototype.flags@^1.5.1:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
version "1.5.1"
resolved "https://registry.yarnpkg.com/regexp.prototype.flags/-/regexp.prototype.flags-1.5.1.tgz#90ce989138db209f81492edd734183ce99f9677e"
integrity sha512-sy6TXMN+hnP/wMy+ISxg3krXx7BAtWVO4UouuCN/ziM9UEne0euamVNafDfvC83bRNr95y0V5iijeDQFUNpvrg==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
dependencies:
call-bind "^1.0.2"
define-properties "^1.2.0"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
set-function-name "^2.0.0"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
remove-trailing-separator@^1.1.0:
Manage qunit via yarn.
2018-09-11 03:07:28 -04:00
version "1.1.0"
resolved "https://registry.yarnpkg.com/remove-trailing-separator/-/remove-trailing-separator-1.1.0.tgz#c24bce2a283adad5bc3f58e0d48249b92379d8ef"
DEV: Bump `@mixer/parallel-prettier` (#19053)
2022-11-16 15:38:57 -05:00
integrity sha512-/hS+Y0u3aOfIETiaiirUFwDBDzmXPvO+jAfKTitUngIPzdKc6Z0LoFjM/CK5PL4C+eKwHohlHAb6H0VFfmmUsw==
Manage qunit via yarn.
2018-09-11 03:07:28 -04:00
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
require-directory@^2.1.1:
version "2.1.1"
resolved "https://registry.yarnpkg.com/require-directory/-/require-directory-2.1.1.tgz#8c64ad5fd30dab1c976e2344ffe7f792a6a6df42"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-fGxEI7+wsG9xrvdjsrlmL22OMTTiHRwAMroiEeMgq8gzoLC/PQr7RsRDSTLUg/bZAZtF+TVIkHc6/4RIKrui+Q==
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
requireindex@^1.2.0:
version "1.2.0"
resolved "https://registry.yarnpkg.com/requireindex/-/requireindex-1.2.0.tgz#3463cdb22ee151902635aa6c9535d4de9c2ef1ef"
integrity sha512-L9jEkOi3ASd9PYit2cwRfyppc9NoABujTP8/5gFcbERmo5jUoAKovIC3fsF17pkTnGsrByysqX+Kxd2OTNI1ww==
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
DEV: introduces documentation for chat (#19772) Note this commit also slightly changes internal API: channel instead of getChannel and updateCurrentUserChannelNotificationsSettings instead of updateCurrentUserChatChannelNotificationsSettings. Also destroyChannel takes a second param which is the name confirmation instead of an optional object containing this confirmation. This is to enforce the fact that it's required. In the future a top level jsdoc config file could be used instead of the hack tempfile, but while it's only an experiment for chat, it's probably good enough.
2023-01-18 06:36:16 -05:00
requizzle@^0.2.3:
version "0.2.4"
resolved "https://registry.yarnpkg.com/requizzle/-/requizzle-0.2.4.tgz#319eb658b28c370f0c20f968fa8ceab98c13d27c"
integrity sha512-JRrFk1D4OQ4SqovXOgdav+K8EAhSB/LJZqCz8tbX0KObcdeM15Ss59ozWMBWmmINMagCwmqn4ZNryUGpBsl6Jw==
dependencies:
lodash "^4.17.21"
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
resolve-from@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/resolve-from/-/resolve-from-4.0.0.tgz#4abcd852ad32dd7baabfe9b40e00a36db5f392e6"
integrity sha512-pb/MYmXstAkysRFx8piNI1tGFNQIFA3vkE3Gq4EuA1dF6gHp/+vgZqsCGJapvy8N3Q+4o7FwvquPJcnZ7RYy4g==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
resolve-from@^5.0.0:
version "5.0.0"
resolved "https://registry.yarnpkg.com/resolve-from/-/resolve-from-5.0.0.tgz#c35225843df8f776df21c57557bc087e9dfdfc69"
integrity sha512-qYg9KP24dD5qka9J47d0aVky0N+b4fTU89LN9iDnjB5waksiC49rvMB0PrUJQGoTmH50XPiqOvAjDfaijGxYZw==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
resolve-package-path@^1.0.11:
version "1.2.7"
resolved "https://registry.yarnpkg.com/resolve-package-path/-/resolve-package-path-1.2.7.tgz#2a7bc37ad96865e239330e3102c31322847e652e"
integrity sha512-fVEKHGeK85bGbVFuwO9o1aU0n3vqQGrezPc51JGu9UTXpFQfWq5qCeKxyaRUSvephs+06c5j5rPq/dzHGEo8+Q==
DEV: Merge package.json files (#21172) This means: a single yarn.lock and removing one of the package.json files
2023-04-20 06:46:12 -04:00
dependencies:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
path-root "^0.1.1"
resolve "^1.10.0"
resolve-package-path@^3.1.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/resolve-package-path/-/resolve-package-path-3.1.0.tgz#35faaa5d54a9c7dd481eb7c4b2a44410c9c763d8"
integrity sha512-2oC2EjWbMJwvSN6Z7DbDfJMnD8MYEouaLn5eIX0j8XwPsYCVIyY9bbnX88YHVkbr8XHqvZrYbxaLPibfTYKZMA==
dependencies:
path-root "^0.1.1"
resolve "^1.17.0"
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
resolve@^1.10.0, resolve@^1.11.1, resolve@^1.17.0, resolve@^1.22.3:
version "1.22.8"
resolved "https://registry.yarnpkg.com/resolve/-/resolve-1.22.8.tgz#b6c87a9f2aa06dfab52e3d70ac8cde321fa5a48d"
integrity sha512-oKWePCxqpd6FlLvGV1VU0x7bkPmmCNolxzjMf4NczoDnQcIWrAF+cPtZn5i6n+RfD2d9i0tzpKnG6Yk168yIyw==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
dependencies:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
is-core-module "^2.13.0"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
path-parse "^1.0.7"
supports-preserve-symlinks-flag "^1.0.0"
DEV: Add uppy.js to build and project (#13645) This PR adds uppy to the project with a custom JS build and the shims needed to import it into our JS code. We need a custom build of Uppy because we do not use webpack for our JS modules/build. The only way to get what you want from Uppy is to use the webpack modules or to include the entire Uppy project including all plugins in a single JS file. This way we can just use the plugins we actually want. Future PRs will actually use Uppy!
2021-07-06 20:39:33 -04:00
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
restore-cursor@^3.1.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/restore-cursor/-/restore-cursor-3.1.0.tgz#39f67c54b3a7a58cea5236d95cf0034239631f7e"
integrity sha512-l+sSefzHpj5qimhFSE5a8nufZYAM3sBSVMAPtYkmC+4EH2anSGaEMXSD0izRQbu9nfyQ9y5JrVmp7E8oZrUjvA==
dependencies:
onetime "^5.1.0"
signal-exit "^3.0.2"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
retry@^0.12.0:
version "0.12.0"
resolved "https://registry.yarnpkg.com/retry/-/retry-0.12.0.tgz#1b42a6266a21f07421d1b0b54b7dc167b01c013b"
integrity sha512-9LkiTwjUh6rT555DtE9rTX+BKByPfrMzEAtnlEtdEwr3Nkffwiihqe2bWADg+OQRjt9gl6ICdmB/ZFDCGAtSow==
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
reusify@^1.0.4:
version "1.0.4"
resolved "https://registry.yarnpkg.com/reusify/-/reusify-1.0.4.tgz#90da382b1e126efc02146e90845a88db12925d76"
integrity sha512-U9nH88a3fc/ekCF1l0/UP1IosiuIjyTh7hBvXVMHYgVcfGvt897Xguj2UOLDeI5BG2m7/uwyaLVT6fbtCwTyzw==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
rimraf@^2.2.8, rimraf@^2.3.4, rimraf@^2.4.3, rimraf@^2.5.3, rimraf@^2.5.4, rimraf@^2.6.1, rimraf@^2.6.2:
version "2.7.1"
resolved "https://registry.yarnpkg.com/rimraf/-/rimraf-2.7.1.tgz#35797f13a7fdadc566142c29d4f07ccad483e3ec"
integrity sha512-uWjbaKIK3T1OSVptzX7Nl6PvQ3qAGtKEtVRjRuazjfL3Bx5eI409VZSqgND+4UNnmzLVdPj9FqFJNPqBZFve4w==
dependencies:
glob "^7.1.3"
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
rimraf@^3.0.0, rimraf@^3.0.2:
version "3.0.2"
resolved "https://registry.yarnpkg.com/rimraf/-/rimraf-3.0.2.tgz#f1a5402ba6220ad52cc1282bac1ae3aa49fd061a"
integrity sha512-JZkJMZkAGFFPP2YqXZXPbMlMBgsxzE8ILs4lMIX/2o0L9UBw9O/Y3o6wFw/i9YLapcUJWwqbi3kdxIPdC62TIA==
dependencies:
glob "^7.1.3"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
rsvp@^3.0.14, rsvp@^3.0.18:
version "3.6.2"
resolved "https://registry.yarnpkg.com/rsvp/-/rsvp-3.6.2.tgz#2e96491599a96cde1b515d5674a8f7a91452926a"
integrity sha512-OfWGQTb9vnwRjwtA2QwpG2ICclHC3pgXZO5xt8H2EfgDquO0qVdSb5T88L4qJVAEugbS56pAuV4XZM58UX8ulw==
rsvp@^4.7.0, rsvp@^4.8.5:
version "4.8.5"
resolved "https://registry.yarnpkg.com/rsvp/-/rsvp-4.8.5.tgz#c8f155311d167f68f21e168df71ec5b083113734"
integrity sha512-nfMOlASu9OnRJo1mbEk2cz0D56a1MBNrJ7orjRZQG10XDyuvwksKbuXNp6qa+kbn839HwjwhBzhFmdsaEAfauA==
rsvp@~3.2.1:
version "3.2.1"
resolved "https://registry.yarnpkg.com/rsvp/-/rsvp-3.2.1.tgz#07cb4a5df25add9e826ebc67dcc9fd89db27d84a"
integrity sha512-Rf4YVNYpKjZ6ASAmibcwTNciQ5Co5Ztq6iZPEykHpkoflnD/K5ryE/rHehFsTm4NJj8nKDhbi3eKBWGogmNnkg==
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
run-parallel@^1.1.9:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "1.2.0"
resolved "https://registry.yarnpkg.com/run-parallel/-/run-parallel-1.2.0.tgz#66d1368da7bdf921eb9d95bd1a9229e7f21a43ee"
integrity sha512-5l4VyZR86LZ/lDxZTR6jqL8AFE2S0IFLMP26AbjsLVADxHdhB/c0GUsH+y39UfCi3dzz8OlQuPmnaJOMoDHQBA==
dependencies:
queue-microtask "^1.2.2"
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
rxjs@^6.6.3:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "6.6.7"
resolved "https://registry.yarnpkg.com/rxjs/-/rxjs-6.6.7.tgz#90ac018acabf491bf65044235d5863c4dab804c9"
integrity sha512-hTdwr+7yYNIT5n4AMYp85KA6yw2Va0FLa3Rguvbpa4W3I5xynaBZo41cM3XM+4Q6fRMj3sBYIR1VAmZMXYJvRQ==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
dependencies:
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
tslib "^1.9.0"
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
rxjs@^7.8.1:
version "7.8.1"
resolved "https://registry.yarnpkg.com/rxjs/-/rxjs-7.8.1.tgz#6f6f3d99ea8044291efd92e7c7fcf562c4057543"
integrity sha512-AA3TVj+0A2iuIoQkWEK/tqFjBq2j+6PO6Y0zJcvzLAFhEFIO3HL0vls9hWLncZbAAbK0mar7oZ4V079I/qPMxg==
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
dependencies:
tslib "^2.1.0"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
safe-array-concat@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/safe-array-concat/-/safe-array-concat-1.0.1.tgz#91686a63ce3adbea14d61b14c99572a8ff84754c"
integrity sha512-6XbUAseYE2KtOuGueyeobCySj9L4+66Tn6KQMOPQJrAJEowYKW/YR/MGJZl7FdydUdaFu4LYyDZjxf4/Nmo23Q==
dependencies:
call-bind "^1.0.2"
get-intrinsic "^1.2.1"
has-symbols "^1.0.3"
isarray "^2.0.5"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
safe-buffer@~5.1.0, safe-buffer@~5.1.1:
Manage qunit via yarn.
2018-09-11 03:07:28 -04:00
version "5.1.2"
resolved "https://registry.yarnpkg.com/safe-buffer/-/safe-buffer-5.1.2.tgz#991ec69d296e0313747d59bdfd2b745c35f8828d"
Update yarn.lock with integrity hashes This should prevent the stable version of yarn from rewriting the lock file all the time.
2018-10-04 05:21:13 -04:00
integrity sha512-Gd2UZBJDkXlY7GbJxfsE8/nvKkUEU1G38c1siN6QP6a9PT9MmHB8GnpscSmMJSoF8LOIrt8ud/wPtojys4G6+g==
Manage qunit via yarn.
2018-09-11 03:07:28 -04:00
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
safe-buffer@~5.2.0:
DEV: Remove unused legacy dependencies
2022-06-18 14:30:12 -04:00
version "5.2.1"
resolved "https://registry.yarnpkg.com/safe-buffer/-/safe-buffer-5.2.1.tgz#1eaf9fa9bdb1fdd4ec75f58f9cdb4e6b7827eec6"
integrity sha512-rp3So07KcdmmKbGvgaNxQSJr7bGVSVk5S9Eq1F+ppbRo70+YeaDxkw5Dd8NPN+GD6bjnYm2VuPuCXmpuYvmCXQ==
Manage qunit via yarn.
2018-09-11 03:07:28 -04:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
safe-regex-test@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/safe-regex-test/-/safe-regex-test-1.0.0.tgz#793b874d524eb3640d1873aad03596db2d4f2295"
integrity sha512-JBUUzyOgEwXQY1NuPtvcj/qcBDbDmEvWufhlnXZIm75DEHp+afM1r1ujJpJsV/gSM4t59tpDyPi1sd6ZaPFfsA==
dependencies:
call-bind "^1.0.2"
get-intrinsic "^1.1.3"
is-regex "^1.1.4"
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
semver@^6.3.0, semver@^6.3.1:
Build(deps): Bump semver from 6.3.0 to 6.3.1 (#22527) Bumps [semver](https://github.com/npm/node-semver) from 6.3.0 to 6.3.1. - [Release notes](https://github.com/npm/node-semver/releases) - [Changelog](https://github.com/npm/node-semver/blob/v6.3.1/CHANGELOG.md) - [Commits](https://github.com/npm/node-semver/compare/v6.3.0...v6.3.1) --- updated-dependencies: - dependency-name: semver dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-07-10 21:39:53 -04:00
version "6.3.1"
resolved "https://registry.yarnpkg.com/semver/-/semver-6.3.1.tgz#556d2ef8689146e46dcea4bfdd095f3434dffcb4"
integrity sha512-BR7VvDCVHO+q2xBEWskxS6DJE1qRnb7DxzUrogb71CWoSficBxYsiAGd+Kl0mmq/MprG9yArRkyrQxTO6XjMzA==
DEV: Don't lint core files when target == plugins (#10259) * DEV: Don't lint core files when target == plugins * Prettier the plugin/*.js files * Update eslintignore/prettierignore * Add eslint-plugin-ember and eslint-plugin-node * Properly lint all js files in all plugins * LINT: run prettier on test/*.js files * DEV: Run prettier checks on test/*.js files * ESLint plugins' assets/javascripts and test/javascripts directories only
2020-08-25 05:40:40 -04:00
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
semver@^7.3.2, semver@^7.3.4, semver@^7.3.5, semver@^7.5.2:
Build(deps): Bump semver from 6.3.0 to 6.3.1 (#22527) Bumps [semver](https://github.com/npm/node-semver) from 6.3.0 to 6.3.1. - [Release notes](https://github.com/npm/node-semver/releases) - [Changelog](https://github.com/npm/node-semver/blob/v6.3.1/CHANGELOG.md) - [Commits](https://github.com/npm/node-semver/compare/v6.3.0...v6.3.1) --- updated-dependencies: - dependency-name: semver dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-07-10 21:39:53 -04:00
version "7.5.4"
resolved "https://registry.yarnpkg.com/semver/-/semver-7.5.4.tgz#483986ec4ed38e1c6c48c34894a9182dbff68a6e"
integrity sha512-1bCSESV6Pv+i21Hvpxp3Dx+pSD8lIPt8uVjRrxAUt/nbswYc+tK6Y2btiULjd4+fnq15PX+nqQDC7Oft7WkwcA==
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
dependencies:
lru-cache "^6.0.0"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
set-function-name@^2.0.0:
version "2.0.1"
resolved "https://registry.yarnpkg.com/set-function-name/-/set-function-name-2.0.1.tgz#12ce38b7954310b9f61faa12701620a0c882793a"
integrity sha512-tMNCiqYVkXIZgc2Hnoy2IvC/f8ezc5koaRFkCjrpWzGpCd3qbZXPzVy9MAZzK1ch/X0jvSkojys3oqJN0qCmdA==
dependencies:
define-data-property "^1.0.1"
functions-have-names "^1.2.3"
has-property-descriptors "^1.0.0"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
shebang-command@^2.0.0:
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
version "2.0.0"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
resolved "https://registry.yarnpkg.com/shebang-command/-/shebang-command-2.0.0.tgz#ccd0af4f8835fbdc265b82461aaf0c36663f34ea"
integrity sha512-kHxr2zZpYtdmrN1qDjrrX/Z1rR1kG8Dx+gkpK1G4eXmvXswmcE1hTWBWYUzlraYw1/yZp6YuDY77YtvbN0dmDA==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
dependencies:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
shebang-regex "^3.0.0"
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
shebang-regex@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/shebang-regex/-/shebang-regex-3.0.0.tgz#ae16f1644d873ecad843b0307b143362d4c42172"
integrity sha512-7++dFhtcx3353uBaq8DDR4NuxBetBzC7ZQOhmTQInHEd6bSrXdiEyzCvG07Z44UYdLShWUyXt5M/yhz8ekcb1A==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
shell-quote@^1.8.1:
version "1.8.1"
resolved "https://registry.yarnpkg.com/shell-quote/-/shell-quote-1.8.1.tgz#6dbf4db75515ad5bac63b4f1894c3a154c766680"
integrity sha512-6j1W9l1iAs/4xYBI1SYOVZyFcCis9b4KCLQ8fgAGG07QvzaRLVVRQvAy85yNmmZSjYjg4MWh4gNvlPujU/5LpA==
side-channel@^1.0.4:
version "1.0.4"
resolved "https://registry.yarnpkg.com/side-channel/-/side-channel-1.0.4.tgz#efce5c8fdc104ee751b25c58d4290011fa5ea2cf"
integrity sha512-q5XPytqFEIKHkGdiMIrY10mvLRvnQh42/+GoBlFW3b2LXLE2xxJpZFdm94we0BaoV3RwJyGqg5wS7epxTv0Zvw==
dependencies:
call-bind "^1.0.0"
get-intrinsic "^1.0.2"
object-inspect "^1.9.0"
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
signal-exit@^3.0.2:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "3.0.7"
resolved "https://registry.yarnpkg.com/signal-exit/-/signal-exit-3.0.7.tgz#a9a1767f8af84155114eaabd73f99273c8f59ad9"
integrity sha512-wnD2ZE+l+SPC/uoS0vXeE9L1+0wuaMqKlfz9AMUo38JsyLSBWSFcHR1Rri62LZc12vLr1gb3jl7iwQhgwpAbGQ==
silent-error@^1.1.1:
version "1.1.1"
resolved "https://registry.yarnpkg.com/silent-error/-/silent-error-1.1.1.tgz#f72af5b0d73682a2ba1778b7e32cd8aa7c2d8662"
integrity sha512-n4iEKyNcg4v6/jpb3c0/iyH2G1nzUNl7Gpqtn/mHIJK9S/q/7MCfoO4rwVOoO59qPFIc0hVHvMbiOJ0NdtxKKw==
dependencies:
debug "^2.2.0"
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
simple-html-tokenizer@^0.5.11:
version "0.5.11"
resolved "https://registry.yarnpkg.com/simple-html-tokenizer/-/simple-html-tokenizer-0.5.11.tgz#4c5186083c164ba22a7b477b7687ac056ad6b1d9"
integrity sha512-C2WEK/Z3HoSFbYq8tI7ni3eOo/NneSPRoPpcM7WdLjFOArFuyXEjAoCdOC3DgMfRyziZQ1hCNR4mrNdWEvD0og==
Support for Ember Template linting
2020-02-05 11:33:15 -05:00
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
slash@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/slash/-/slash-3.0.0.tgz#6539be870c165adbd5240220dbe361f1bc4d4634"
integrity sha512-g9Q1haeby36OSStwb4ntCGGGaKsaVSjQ68fBxoQcutl5fS1vuY18H3wSt3jFyFtrkx+Kz0V1G85A4MyAdDMi2Q==
Support for Ember Template linting
2020-02-05 11:33:15 -05:00
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
slash@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/slash/-/slash-4.0.0.tgz#2422372176c4c6c5addb5e2ada885af984b396a7"
integrity sha512-3dOsAHXXUkQTpOYcoAxLIorMTp4gIQr5IW3iVb7A7lFIp0VHhnynm9izx6TssdrIcVIESAlVjtnO2K8bg+Coew==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
smart-buffer@^4.2.0:
version "4.2.0"
resolved "https://registry.yarnpkg.com/smart-buffer/-/smart-buffer-4.2.0.tgz#6e1d71fa4f18c05f7d0ff216dd16a481d0e8d9ae"
integrity sha512-94hK0Hh8rPqQl2xXc3HsaBoOXKV20MToPkcXvwbISWLEs+64sBq5kFgn2kJDHb1Pry9yrP0dxrCI9RRci7RXKg==
DEV: Introduce decorator-position lint rule (#22937)
2023-08-04 07:26:06 -04:00
snake-case@^3.0.3, snake-case@^3.0.4:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
version "3.0.4"
resolved "https://registry.yarnpkg.com/snake-case/-/snake-case-3.0.4.tgz#4f2bbd568e9935abdfd593f34c691dadb49c452c"
integrity sha512-LAOh4z89bGQvl9pFfNF8V146i7o7/CqFPbqzYgP+yYzDIDeS9HaNFtXABamRW+AQzEVODcvE79ljJ+8a9YSdMg==
DEV: Don't lint core files when target == plugins (#10259) * DEV: Don't lint core files when target == plugins * Prettier the plugin/*.js files * Update eslintignore/prettierignore * Add eslint-plugin-ember and eslint-plugin-node * Properly lint all js files in all plugins * LINT: run prettier on test/*.js files * DEV: Run prettier checks on test/*.js files * ESLint plugins' assets/javascripts and test/javascripts directories only
2020-08-25 05:40:40 -04:00
dependencies:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
dot-case "^3.0.4"
tslib "^2.0.3"
Upgrade puppeteer which was accidentally downgraded.
2018-06-07 02:03:01 -04:00
Revert "DEV: FloatKit (#23541)" (#23549) This reverts commits 0623ac684a65f95ce4f5438ff47944b1dc2119f4 408e71e437ef8abf98f93e3449898bf906766b0e a32fa3b9470dde0543fcee809f2abd1f219f7336 User tips were running into some issues.
2023-09-12 13:55:12 -04:00
socks-proxy-agent@^8.0.1:
version "8.0.1"
resolved "https://registry.yarnpkg.com/socks-proxy-agent/-/socks-proxy-agent-8.0.1.tgz#ffc5859a66dac89b0c4dab90253b96705f3e7120"
integrity sha512-59EjPbbgg8U3x62hhKOFVAmySQUcfRQ4C7Q/D5sEHnZTQRrQlNKINks44DMR1gwXp0p4LaVIeccX2KHTTcHVqQ==
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
dependencies:
Revert "DEV: FloatKit (#23541)" (#23549) This reverts commits 0623ac684a65f95ce4f5438ff47944b1dc2119f4 408e71e437ef8abf98f93e3449898bf906766b0e a32fa3b9470dde0543fcee809f2abd1f219f7336 User tips were running into some issues.
2023-09-12 13:55:12 -04:00
agent-base "^7.0.1"
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
debug "^4.3.4"
socks "^2.7.1"
socks@^2.7.1:
version "2.7.1"
resolved "https://registry.yarnpkg.com/socks/-/socks-2.7.1.tgz#d8e651247178fde79c0663043e07240196857d55"
integrity sha512-7maUZy1N7uo6+WVEX6psASxtNlKaNVMlGQKkG/63nEDdLOWNbiUMoLK7X4uYoLhQstau72mLgfEWcXcwsaHbYQ==
dependencies:
ip "^2.0.0"
smart-buffer "^4.2.0"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
source-map-js@^1.0.1:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
version "1.0.2"
resolved "https://registry.yarnpkg.com/source-map-js/-/source-map-js-1.0.2.tgz#adbc361d9c62df380125e7f161f71c826f1e490c"
integrity sha512-R0XvVJ9WusLiqTCEiGCmICCMplcCkIwwR11mOSD9CR5u+IXYdiseeEuXCVAjS54zqwkLcPNnmU4OeJ6tUrWhDw==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
source-map@~0.6.1:
version "0.6.1"
resolved "https://registry.yarnpkg.com/source-map/-/source-map-0.6.1.tgz#74722af32e9614e9c287a8d0bbde48b5e2f1a263"
integrity sha512-UjgapumWlbMhkBgzT7Ykc5YXUT46F0iKu8SGXq0bcwP5dz/h0Plj6enJqjz1Zbq2l5WaqYnrVbwWOWMyF3F47g==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
sourcemap-codec@^1.4.8:
version "1.4.8"
resolved "https://registry.yarnpkg.com/sourcemap-codec/-/sourcemap-codec-1.4.8.tgz#ea804bd94857402e6992d05a38ef1ae35a9ab4c4"
integrity sha512-9NykojV5Uih4lgo5So5dtw+f0JgJX30KCNI8gwhz2J9A15wD0Ml6tjHKwf6fTSa6fAdVBdZeNOs9eJ71qCk8vA==
spawn-command@0.0.2:
version "0.0.2"
resolved "https://registry.yarnpkg.com/spawn-command/-/spawn-command-0.0.2.tgz#9544e1a43ca045f8531aac1a48cb29bdae62338e"
integrity sha512-zC8zGoGkmc8J9ndvml8Xksr1Amk9qBujgbF0JAIWO7kXr43w0h/0GJNM/Vustixu+YE8N/MTrQ7N31FvHUACxQ==
sprintf-js@^1.1.1:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
version "1.1.3"
resolved "https://registry.yarnpkg.com/sprintf-js/-/sprintf-js-1.1.3.tgz#4914b903a2f8b685d17fdf78a70e917e872e444a"
integrity sha512-Oo+0REFV59/rz3gfJNKQiBlwfHaSESl1pcGyABQsnnIfWOFt6JNj5gCog2U6MLZ//IGYD+nA8nI+mTShREReaA==
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
FEATURE: Optimize images before upload (#13432) Integrates [mozJPEG](https://github.com/mozilla/mozjpeg) and [Resize](https://github.com/PistonDevelopers/resize) using WebAssembly to optimize user uploads in the composer on the client-side. NPM libraries are sourced from our [Squoosh fork](https://github.com/discourse/squoosh/tree/discourse), which was needed because we have an older asset pipeline.
2021-06-23 11:31:12 -04:00
squoosh@discourse/squoosh#dc9649d:
version "2.0.0"
resolved "https://codeload.github.com/discourse/squoosh/tar.gz/dc9649d0a4d396d1251c22291b17d99f1716da44"
dependencies:
DEV: Upgrade "lefthook" and skip hooks during merge/rebase (#18910) The old lefthook package was deprecated a long time ago and skipping hooks during merge/rebase makes those git commands a lot faster.
2022-11-07 11:13:21 -05:00
wasm-feature-detect "^1.2.11"
FEATURE: Optimize images before upload (#13432) Integrates [mozJPEG](https://github.com/mozilla/mozjpeg) and [Resize](https://github.com/PistonDevelopers/resize) using WebAssembly to optimize user uploads in the composer on the client-side. NPM libraries are sourced from our [Squoosh fork](https://github.com/discourse/squoosh/tree/discourse), which was needed because we have an older asset pipeline.
2021-06-23 11:31:12 -04:00
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
stream-shift@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/stream-shift/-/stream-shift-1.0.1.tgz#d7088281559ab2778424279b0877da3c392d5a3d"
integrity sha512-AiisoFqQ0vbGcZgQPY1cdP2I76glaVA/RauYR4G4thNFgkTqr90yXTo4LYX60Jl+sIlPNHHdGSwo01AvbKUSVQ==
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
streamx@^2.15.0:
version "2.15.1"
resolved "https://registry.yarnpkg.com/streamx/-/streamx-2.15.1.tgz#396ad286d8bc3eeef8f5cea3f029e81237c024c6"
integrity sha512-fQMzy2O/Q47rgwErk/eGeLu/roaFWV0jVsogDmrszM9uIw8L5OA+t+V93MgYlufNptfjmYR1tOMWhei/Eh7TQA==
dependencies:
fast-fifo "^1.1.0"
queue-tick "^1.0.1"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
string-width@^4.1.0, string-width@^4.2.0, string-width@^4.2.3:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
version "4.2.3"
resolved "https://registry.yarnpkg.com/string-width/-/string-width-4.2.3.tgz#269c7117d27b05ad2e536830a8ec895ef9c6d010"
integrity sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
dependencies:
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
emoji-regex "^8.0.0"
is-fullwidth-code-point "^3.0.0"
strip-ansi "^6.0.1"
DEV: Merge package.json files (#21172) This means: a single yarn.lock and removing one of the package.json files
2023-04-20 06:46:12 -04:00
DEV: Rename I18n imports to discourse-i18n (#23915) As of #23867 this is now a real package, so updating the imports to use the real package name, rather than relying on the alias. The name change in the package name is because `I18n` is not a valid name as NPM packages must be all lowercase. This commit also introduces an eslint rule to prevent importing from the old I18n path. For themes/plugins, the old 'i18n' name remains functional.
2023-10-18 06:07:09 -04:00
string.prototype.matchall@^4.0.5, string.prototype.matchall@^4.0.6:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
version "4.0.10"
resolved "https://registry.yarnpkg.com/string.prototype.matchall/-/string.prototype.matchall-4.0.10.tgz#a1553eb532221d4180c51581d6072cd65d1ee100"
integrity sha512-rGXbGmOEosIQi6Qva94HUjgPs9vKW+dkG7Y8Q5O2OYkWL6wFaTRZO8zM4mhP94uX55wgyrXzfS2aGtGzUL7EJQ==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
dependencies:
call-bind "^1.0.2"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
define-properties "^1.2.0"
es-abstract "^1.22.1"
get-intrinsic "^1.2.1"
has-symbols "^1.0.3"
internal-slot "^1.0.5"
regexp.prototype.flags "^1.5.0"
set-function-name "^2.0.0"
side-channel "^1.0.4"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
string.prototype.trim@^1.2.8:
version "1.2.8"
resolved "https://registry.yarnpkg.com/string.prototype.trim/-/string.prototype.trim-1.2.8.tgz#f9ac6f8af4bd55ddfa8895e6aea92a96395393bd"
integrity sha512-lfjY4HcixfQXOfaqCvcBuOIapyaroTXhbkfJN3gcB1OtyupngWK4sEET9Knd0cXd28kTUqu/kHoV4HKSJdnjiQ==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
dependencies:
call-bind "^1.0.2"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
define-properties "^1.2.0"
es-abstract "^1.22.1"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
string.prototype.trimend@^1.0.7:
version "1.0.7"
resolved "https://registry.yarnpkg.com/string.prototype.trimend/-/string.prototype.trimend-1.0.7.tgz#1bb3afc5008661d73e2dc015cd4853732d6c471e"
integrity sha512-Ni79DqeB72ZFq1uH/L6zJ+DKZTkOtPIHovb3YZHQViE+HDouuU4mBrLOLDn5Dde3RF8qw5qVETEjhu9locMLvA==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
dependencies:
call-bind "^1.0.2"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
define-properties "^1.2.0"
es-abstract "^1.22.1"
string.prototype.trimstart@^1.0.7:
version "1.0.7"
resolved "https://registry.yarnpkg.com/string.prototype.trimstart/-/string.prototype.trimstart-1.0.7.tgz#d4cdb44b83a4737ffbac2d406e405d43d0184298"
integrity sha512-NGhtDFu3jCEm7B4Fy0DpLewdJQOZcQ0rGbwQ/+stjnrp2i+rlKeCvos9hOIeCmqwratM47OBxY7uFZzjxHXmrg==
dependencies:
call-bind "^1.0.2"
define-properties "^1.2.0"
es-abstract "^1.22.1"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
string_decoder@^1.1.1:
version "1.3.0"
resolved "https://registry.yarnpkg.com/string_decoder/-/string_decoder-1.3.0.tgz#42f114594a46cf1a8e30b0a84f56c78c3edac21e"
integrity sha512-hkRX8U1WjJFd8LsDJ2yQ/wWWxaopEsABU1XfkM8A+j0+85JAGppt16cr1Whg6KIbb4okU6Mql6BOj+uup/wKeA==
dependencies:
safe-buffer "~5.2.0"
Manage qunit via yarn.
2018-09-11 03:07:28 -04:00
string_decoder@~1.1.1:
version "1.1.1"
resolved "https://registry.yarnpkg.com/string_decoder/-/string_decoder-1.1.1.tgz#9cf1611ba62685d7030ae9e4ba34149c3af03fc8"
Update yarn.lock with integrity hashes This should prevent the stable version of yarn from rewriting the lock file all the time.
2018-10-04 05:21:13 -04:00
integrity sha512-n/ShnvDi6FHbbVfviro+WojiFzv+s8MPMHBczVePfUpDJLwoLT0ht1l4YwBCbi8pJAveEEdnkHyPyTP/mzRfwg==
Manage qunit via yarn.
2018-09-11 03:07:28 -04:00
dependencies:
safe-buffer "~5.1.0"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
strip-ansi@^6.0.0, strip-ansi@^6.0.1:
version "6.0.1"
resolved "https://registry.yarnpkg.com/strip-ansi/-/strip-ansi-6.0.1.tgz#9e26c63d30f53443e9489495b2105d37b67a85d9"
integrity sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
dependencies:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
ansi-regex "^5.0.1"
Support for Ember Template linting
2020-02-05 11:33:15 -05:00
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
strip-json-comments@^3.1.0, strip-json-comments@^3.1.1:
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
version "3.1.1"
resolved "https://registry.yarnpkg.com/strip-json-comments/-/strip-json-comments-3.1.1.tgz#31f1281b3832630434831c310c01cccda8cbe006"
integrity sha512-6fPc+R4ihwqP6N/aIv2f1gMH8lOVtWQHoqC4yK6oSDVVocumAsfCqjkXnqiYMhmMwS/mEHLp7Vehlt3ql6lEig==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
DEV: Upgrade sinon and fix time based bookmark tests (#9647) Update sinon.js to 9.0.2 to access async fake timers https://sinonjs.org/releases/v9.0.2/fake-timers/ which can then be used with acceptance tests (previously useFakeTimers didn't work with await, e.g. for visit). Fix the bookmark acceptance test that was time based to use these new fake timers. Add a fakeTime function that uses moment and the provided date string + timezone to freeze time using useFakeTimers and return a clock. Add a timeStep function that accepts a clock from fakeTime and a function to run. Once the function is run we call clock.tickAsync(1000) to progress the fake clock forward 1s to progress promises/callbacks.
2020-05-06 19:10:32 -04:00
supports-color@^5.3.0:
use yarn to manage test vendor dependencies, upgrade sinon to v6.3.5
2018-10-04 11:06:14 -04:00
version "5.5.0"
resolved "https://registry.yarnpkg.com/supports-color/-/supports-color-5.5.0.tgz#e2e69a44ac8772f78a1ec0b35b689df6530efc8f"
integrity sha512-QjVjwdXIt408MIiAqCX4oUKsgU2EqAGzs2Ppkm4aQYbjm+ZEWEcW4SfFNTr4uMNZma0ey4f5lgLrkB0aX0QMow==
dependencies:
has-flag "^3.0.0"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
supports-color@^7.1.0:
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
version "7.2.0"
resolved "https://registry.yarnpkg.com/supports-color/-/supports-color-7.2.0.tgz#1b7dcdcb32b8138801b3e478ba6a51caa89648da"
integrity sha512-qpCAvRl9stuOHveKsn7HncJRvv501qIacKzQlO/+Lwxc9+0q2wLyv4Dfvt80/DPn2pqOBsJdDiogXGR9+OvwRw==
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
dependencies:
has-flag "^4.0.0"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
supports-color@^8.1.1:
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
version "8.1.1"
resolved "https://registry.yarnpkg.com/supports-color/-/supports-color-8.1.1.tgz#cd6fc17e28500cff56c1b86c0a7fd4a54a73005c"
integrity sha512-MpUEN2OodtUzxvKQl72cUF7RQ5EiHsGvSsVG0ia9c5RbWGL2CI4C7EpPS8UTBIplnlzZiNuV56w+FuNxy3ty2Q==
dependencies:
has-flag "^4.0.0"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
supports-preserve-symlinks-flag@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/supports-preserve-symlinks-flag/-/supports-preserve-symlinks-flag-1.0.0.tgz#6eda4bd344a3c94aea376d4cc31bc77311039e09"
integrity sha512-ot0WnXS9fgdkgIcePe6RHNk1WA8+muPa6cSjeR3V8K27q9BB1rTE3R1p7Hv0z1ZyAc8s6Vvv8DIyWf681MAt0w==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
symlink-or-copy@^1.0.0, symlink-or-copy@^1.0.1, symlink-or-copy@^1.1.8, symlink-or-copy@^1.2.0, symlink-or-copy@^1.3.1:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "1.3.1"
resolved "https://registry.yarnpkg.com/symlink-or-copy/-/symlink-or-copy-1.3.1.tgz#9506dd64d8e98fa21dcbf4018d1eab23e77f71fe"
integrity sha512-0K91MEXFpBUaywiwSSkmKjnGcasG/rVBXFLJz5DrgGabpYD6N+3yZrfD6uUIfpuTu65DZLHi7N8CizHc07BPZA==
sync-disk-cache@^1.3.3:
version "1.3.4"
resolved "https://registry.yarnpkg.com/sync-disk-cache/-/sync-disk-cache-1.3.4.tgz#53a2c5a09d8f4bb53160bce182a456ad71574024"
integrity sha512-GlkGeM81GPPEKz/lH7QUTbvqLq7K/IUTuaKDSMulP9XQ42glqNJIN/RKgSOw4y8vxL1gOVvj+W7ruEO4s36eCw==
dependencies:
debug "^2.1.3"
heimdalljs "^0.2.3"
mkdirp "^0.5.0"
rimraf "^2.2.8"
username-sync "^1.0.2"
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
sync-disk-cache@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/sync-disk-cache/-/sync-disk-cache-2.1.0.tgz#01e879edc41c34a01fcdda5b39d47dd496e154a6"
integrity sha512-vngT2JmkSapgq0z7uIoYtB9kWOOzMihAAYq/D3Pjm/ODOGMgS4r++B+OZ09U4hWR6EaOdy9eqQ7/8ygbH3wehA==
dependencies:
debug "^4.1.1"
heimdalljs "^0.2.6"
mkdirp "^0.5.0"
rimraf "^3.0.0"
username-sync "^1.0.2"
DEV: Chat service object initial implementation (#19814) This is a combined work of Martin Brennan, Loïc Guitaut, and Joffrey Jaffeux. --- This commit implements a base service object when working in chat. The documentation is available at https://discourse.github.io/discourse/chat/backend/Chat/Service.html Generating documentation has been made as part of this commit with a bigger goal in mind of generally making it easier to dive into the chat project. Working with services generally involves 3 parts: - The service object itself, which is a series of steps where few of them are specialized (model, transaction, policy) ```ruby class UpdateAge include Chat::Service::Base model :user, :fetch_user policy :can_see_user contract step :update_age class Contract attribute :age, :integer end def fetch_user(user_id:, **) User.find_by(id: user_id) end def can_see_user(guardian:, **) guardian.can_see_user(user) end def update_age(age:, **) user.update!(age: age) end end ``` - The `with_service` controller helper, handling success and failure of the service within a service and making easy to return proper response to it from the controller ```ruby def update with_service(UpdateAge) do on_success { render_serialized(result.user, BasicUserSerializer, root: "user") } end end ``` - Rspec matchers and steps inspector, improving the dev experience while creating specs for a service ```ruby RSpec.describe(UpdateAge) do subject(:result) do described_class.call(guardian: guardian, user_id: user.id, age: age) end fab!(:user) { Fabricate(:user) } fab!(:current_user) { Fabricate(:admin) } let(:guardian) { Guardian.new(current_user) } let(:age) { 1 } it { expect(user.reload.age).to eq(age) } end ``` Note in case of unexpected failure in your spec, the output will give all the relevant information: ``` 1) UpdateAge when no channel_id is given is expected to fail to find a model named 'user' Failure/Error: it { is_expected.to fail_to_find_a_model(:user) } Expected model 'foo' (key: 'result.model.user') was not found in the result object. [1/4] [model] 'user' ❌ [2/4] [policy] 'can_see_user' [3/4] [contract] 'default' [4/4] [step] 'update_age' /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/update_age.rb:32:in `fetch_user': missing keyword: :user_id (ArgumentError) from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:202:in `instance_exec' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:202:in `call' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:219:in `call' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:417:in `block in run!' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:417:in `each' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:417:in `run!' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:411:in `run' from <internal:kernel>:90:in `tap' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:302:in `call' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/spec/services/update_age_spec.rb:15:in `block (3 levels) in <main>' ```
2023-02-13 07:09:57 -05:00
taffydb@2.6.2:
version "2.6.2"
resolved "https://registry.yarnpkg.com/taffydb/-/taffydb-2.6.2.tgz#7cbcb64b5a141b6a2efc2c5d2c67b4e150b2a268"
integrity sha512-y3JaeRSplks6NYQuCOj3ZFMO3j60rTwbuKCvZxsAraGYH2epusatvZ0baZYA01WsGqJBq/Dl6vOrMUJqyMj8kA==
taffydb@^2.7.3:
version "2.7.3"
resolved "https://registry.yarnpkg.com/taffydb/-/taffydb-2.7.3.tgz#2ad37169629498fca5bc84243096d3cde0ec3a34"
integrity sha512-GQ3gtYFSOAxSMN/apGtDKKkbJf+8izz5YfbGqIsUc7AMiQOapARZ76dhilRY2h39cynYxBFdafQo5HUL5vgkrg==
DEV: introduces documentation for chat (#19772) Note this commit also slightly changes internal API: channel instead of getChannel and updateCurrentUserChannelNotificationsSettings instead of updateCurrentUserChatChannelNotificationsSettings. Also destroyChannel takes a second param which is the name confirmation instead of an optional object containing this confirmation. This is to enforce the fact that it's required. In the future a top level jsdoc config file could be used instead of the hack tempfile, but while it's only an experiment for chat, it's probably good enough.
2023-01-18 06:36:16 -05:00
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
tar-fs@3.0.4:
version "3.0.4"
resolved "https://registry.yarnpkg.com/tar-fs/-/tar-fs-3.0.4.tgz#a21dc60a2d5d9f55e0089ccd78124f1d3771dbbf"
integrity sha512-5AFQU8b9qLfZCX9zp2duONhPmZv0hGYiBPJsyUdqMjzq/mqVpy/rEUSeHk1+YitmxugaptgBh5oDGU3VsAJq4w==
DEV: Switch from puppeteer to puppeteer-core for smoke test (#15262) `puppeteer` includes a full chromium binary, which adds more than 300mb to our node_modules directory in development/test mode (and therefore the `discourse_dev` and `discourse_test` docker images). We already reach out to the system copy of Chrome for our qunit tests, and already have chrome installed in our `discourse_dev`/`discourse_test` docker images, so it's much more efficient to switch to `puppeteer-core` which doesn't include the chromium binary.
2021-12-13 04:31:49 -05:00
dependencies:
mkdirp-classic "^0.5.2"
pump "^3.0.0"
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
tar-stream "^3.1.5"
DEV: Switch from puppeteer to puppeteer-core for smoke test (#15262) `puppeteer` includes a full chromium binary, which adds more than 300mb to our node_modules directory in development/test mode (and therefore the `discourse_dev` and `discourse_test` docker images). We already reach out to the system copy of Chrome for our qunit tests, and already have chrome installed in our `discourse_dev`/`discourse_test` docker images, so it's much more efficient to switch to `puppeteer-core` which doesn't include the chromium binary.
2021-12-13 04:31:49 -05:00
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
tar-stream@^3.1.5:
version "3.1.6"
resolved "https://registry.yarnpkg.com/tar-stream/-/tar-stream-3.1.6.tgz#6520607b55a06f4a2e2e04db360ba7d338cc5bab"
integrity sha512-B/UyjYwPpMBv+PaFSWAmtYjwdrlEaZQEhMIBFNC5oEG8lpiW8XjcSdmEaClj28ArfKScKHs2nshz3k2le6crsg==
DEV: Switch from puppeteer to puppeteer-core for smoke test (#15262) `puppeteer` includes a full chromium binary, which adds more than 300mb to our node_modules directory in development/test mode (and therefore the `discourse_dev` and `discourse_test` docker images). We already reach out to the system copy of Chrome for our qunit tests, and already have chrome installed in our `discourse_dev`/`discourse_test` docker images, so it's much more efficient to switch to `puppeteer-core` which doesn't include the chromium binary.
2021-12-13 04:31:49 -05:00
dependencies:
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
b4a "^1.6.4"
fast-fifo "^1.2.0"
streamx "^2.15.0"
DEV: Switch from puppeteer to puppeteer-core for smoke test (#15262) `puppeteer` includes a full chromium binary, which adds more than 300mb to our node_modules directory in development/test mode (and therefore the `discourse_dev` and `discourse_test` docker images). We already reach out to the system copy of Chrome for our qunit tests, and already have chrome installed in our `discourse_dev`/`discourse_test` docker images, so it's much more efficient to switch to `puppeteer-core` which doesn't include the chromium binary.
2021-12-13 04:31:49 -05:00
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
text-table@^0.2.0:
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
version "0.2.0"
resolved "https://registry.yarnpkg.com/text-table/-/text-table-0.2.0.tgz#7f5ee823ae805207c00af2df4a84ec3fcfa570b4"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-N+8UisAXDGk8PFXP4HAzVR9nbfmVJ3zYLAWiTIoqC5v5isinhr+r5uaO8+7r3BMfuNIufIsA7RdpVgacC2cSpw==
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
"textextensions@1 || 2", textextensions@^2.5.0:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "2.6.0"
resolved "https://registry.yarnpkg.com/textextensions/-/textextensions-2.6.0.tgz#d7e4ab13fe54e32e08873be40d51b74229b00fc4"
integrity sha512-49WtAWS+tcsy93dRt6P0P3AMD2m5PvXRhuEA0kaXos5ZLlujtYmpmFsB+QvWUSxE1ZsstmYXfQ7L40+EcQgpAQ==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
through2-filter@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/through2-filter/-/through2-filter-3.0.0.tgz#700e786df2367c2c88cd8aa5be4cf9c1e7831254"
integrity sha512-jaRjI2WxN3W1V8/FMZ9HKIBXixtiqs3SQSX4/YGIiP3gL6djW48VoZq9tDqeCWs3MT8YY5wb/zli8VW8snY1CA==
dependencies:
through2 "~2.0.0"
xtend "~4.0.0"
DEV: Remove unused legacy dependencies
2022-06-18 14:30:12 -04:00
through2@~2.0.0:
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
version "2.0.5"
resolved "https://registry.yarnpkg.com/through2/-/through2-2.0.5.tgz#01c1e39eb31d07cb7d03a96a70823260b23132cd"
integrity sha512-/mrRod8xqpA+IHSLyGCQ2s8SPHiCDEeQJSep1jqLYeEUClOFG2Qsh+4FU6G9VeqpZnGW/Su8LQGc4YKni5rYSQ==
dependencies:
readable-stream "~2.3.6"
xtend "~4.0.1"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
through@^2.3.8:
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
version "2.3.8"
resolved "https://registry.yarnpkg.com/through/-/through-2.3.8.tgz#0dd4c9ffaabc357960b1b724115d7e0e86a2e1f5"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-w89qg7PI8wAdvX60bMDP+bFoD5Dvhm9oLheFp5O4a2QF0cSBGsBX4qZmadPMvVqlLJBBci+WqGGOAPvcDeNSVg==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
DEV: Chat service object initial implementation (#19814) This is a combined work of Martin Brennan, Loïc Guitaut, and Joffrey Jaffeux. --- This commit implements a base service object when working in chat. The documentation is available at https://discourse.github.io/discourse/chat/backend/Chat/Service.html Generating documentation has been made as part of this commit with a bigger goal in mind of generally making it easier to dive into the chat project. Working with services generally involves 3 parts: - The service object itself, which is a series of steps where few of them are specialized (model, transaction, policy) ```ruby class UpdateAge include Chat::Service::Base model :user, :fetch_user policy :can_see_user contract step :update_age class Contract attribute :age, :integer end def fetch_user(user_id:, **) User.find_by(id: user_id) end def can_see_user(guardian:, **) guardian.can_see_user(user) end def update_age(age:, **) user.update!(age: age) end end ``` - The `with_service` controller helper, handling success and failure of the service within a service and making easy to return proper response to it from the controller ```ruby def update with_service(UpdateAge) do on_success { render_serialized(result.user, BasicUserSerializer, root: "user") } end end ``` - Rspec matchers and steps inspector, improving the dev experience while creating specs for a service ```ruby RSpec.describe(UpdateAge) do subject(:result) do described_class.call(guardian: guardian, user_id: user.id, age: age) end fab!(:user) { Fabricate(:user) } fab!(:current_user) { Fabricate(:admin) } let(:guardian) { Guardian.new(current_user) } let(:age) { 1 } it { expect(user.reload.age).to eq(age) } end ``` Note in case of unexpected failure in your spec, the output will give all the relevant information: ``` 1) UpdateAge when no channel_id is given is expected to fail to find a model named 'user' Failure/Error: it { is_expected.to fail_to_find_a_model(:user) } Expected model 'foo' (key: 'result.model.user') was not found in the result object. [1/4] [model] 'user' ❌ [2/4] [policy] 'can_see_user' [3/4] [contract] 'default' [4/4] [step] 'update_age' /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/update_age.rb:32:in `fetch_user': missing keyword: :user_id (ArgumentError) from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:202:in `instance_exec' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:202:in `call' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:219:in `call' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:417:in `block in run!' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:417:in `each' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:417:in `run!' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:411:in `run' from <internal:kernel>:90:in `tap' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:302:in `call' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/spec/services/update_age_spec.rb:15:in `block (3 levels) in <main>' ```
2023-02-13 07:09:57 -05:00
tidy-jsdoc@^1.4.1:
version "1.4.1"
resolved "https://registry.yarnpkg.com/tidy-jsdoc/-/tidy-jsdoc-1.4.1.tgz#609289afb4094c4b4cb4367cbce746f940232edd"
integrity sha512-FpH1oL6fEMMO0qPPAjoV8peAriwTjdys92TMsfMufrDERDGfmg2w90ieqOQ4RGDH7yuvDTqxR7a0W1Mfun8fzA==
dependencies:
jsdoc "^3.6.3"
taffydb "^2.7.3"
util "^0.10.3"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
tmp@0.0.28:
version "0.0.28"
resolved "https://registry.yarnpkg.com/tmp/-/tmp-0.0.28.tgz#172735b7f614ea7af39664fa84cf0de4e515d120"
integrity sha512-c2mmfiBmND6SOVxzogm1oda0OJ1HZVIk/5n26N59dDTh80MUeavpiCls4PGAdkX1PFkKokLpcf7prSjCeXLsJg==
dependencies:
os-tmpdir "~1.0.1"
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
tmp@^0.2.1:
version "0.2.1"
resolved "https://registry.yarnpkg.com/tmp/-/tmp-0.2.1.tgz#8457fc3037dcf4719c251367a1af6500ee1ccf14"
integrity sha512-76SUhtfqR2Ijn+xllcI5P1oyannHNHByD80W1q447gU3mp9G9PSpGdWmjUOHRDPiHYacIk66W7ubDTuPF3BEtQ==
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
dependencies:
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
rimraf "^3.0.0"
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
DEV: Bump `@mixer/parallel-prettier` (#19053)
2022-11-16 15:38:57 -05:00
to-absolute-glob@^2.0.2:
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
version "2.0.2"
resolved "https://registry.yarnpkg.com/to-absolute-glob/-/to-absolute-glob-2.0.2.tgz#1865f43d9e74b0822db9f145b78cff7d0f7c849b"
DEV: Bump `@mixer/parallel-prettier` (#19053)
2022-11-16 15:38:57 -05:00
integrity sha512-rtwLUQEwT8ZeKQbyFJyomBRYXyE16U5VKuy0ftxLMK/PZb2fkOsg5r9kHdauuVDbsNdIBoC/HCthpidamQFXYA==
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
dependencies:
is-absolute "^1.0.0"
is-negated-glob "^1.0.0"
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
to-fast-properties@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/to-fast-properties/-/to-fast-properties-2.0.0.tgz#dc5e698cbd079265bc73e0377681a4e4e83f616e"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-/OaKK0xYrs3DmxRYqL/yDc+FxFUVYhDlXMhRmv3z915w2HF1tnN1omB354j8VUGO/hbRzyD6Y3sA7v7GS/ceog==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
to-regex-range@^5.0.1:
version "5.0.1"
resolved "https://registry.yarnpkg.com/to-regex-range/-/to-regex-range-5.0.1.tgz#1648c44aae7c8d988a326018ed72f5b4dd0392e4"
integrity sha512-65P7iz6X5yEr1cwcgvQxbbIw7Uk3gOy5dIdtZ4rDveLqhrdJP+Li/Hx6tyK0NEb+2GCyneCMJiGqrADCSNk8sQ==
dependencies:
is-number "^7.0.0"
DEV: Switch from puppeteer to puppeteer-core for smoke test (#15262) `puppeteer` includes a full chromium binary, which adds more than 300mb to our node_modules directory in development/test mode (and therefore the `discourse_dev` and `discourse_test` docker images). We already reach out to the system copy of Chrome for our qunit tests, and already have chrome installed in our `discourse_dev`/`discourse_test` docker images, so it's much more efficient to switch to `puppeteer-core` which doesn't include the chromium binary.
2021-12-13 04:31:49 -05:00
tr46@~0.0.3:
version "0.0.3"
resolved "https://registry.yarnpkg.com/tr46/-/tr46-0.0.3.tgz#8184fd347dac9cdc185992f3a6622e14b9d9ab6a"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-N3WMsuqV66lT30CrXNbEjx4GEwlow3v6rr4mCcv6prnfwhS01rkgyFdjPNBYd9br7LpXV1+Emh01fHnq2Gdgrw==
DEV: Switch from puppeteer to puppeteer-core for smoke test (#15262) `puppeteer` includes a full chromium binary, which adds more than 300mb to our node_modules directory in development/test mode (and therefore the `discourse_dev` and `discourse_test` docker images). We already reach out to the system copy of Chrome for our qunit tests, and already have chrome installed in our `discourse_dev`/`discourse_test` docker images, so it's much more efficient to switch to `puppeteer-core` which doesn't include the chromium binary.
2021-12-13 04:31:49 -05:00
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
tree-kill@^1.2.2:
version "1.2.2"
resolved "https://registry.yarnpkg.com/tree-kill/-/tree-kill-1.2.2.tgz#4ca09a9092c88b73a7cdc5e8a01b507b0790a0cc"
integrity sha512-L0Orpi8qGpRG//Nd+H90vFB+3iHnue1zSSGmNOOCh1GLJ7rUKVwV2HvijphGQS2UmhUZewS9VgvxYIdgr+fG1A==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
tree-sync@^1.2.2:
version "1.4.0"
resolved "https://registry.yarnpkg.com/tree-sync/-/tree-sync-1.4.0.tgz#314598d13abaf752547d9335b8f95d9a137100d6"
integrity sha512-YvYllqh3qrR5TAYZZTXdspnIhlKAYezPYw11ntmweoceu4VK+keN356phHRIIo1d+RDmLpHZrUlmxga2gc9kSQ==
dependencies:
debug "^2.2.0"
fs-tree-diff "^0.5.6"
mkdirp "^0.5.1"
quick-temp "^0.1.5"
walk-sync "^0.3.3"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
ts-replace-all@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/ts-replace-all/-/ts-replace-all-1.0.0.tgz#ef28283ccdb4da7d69fb03cf543e09e51711659b"
integrity sha512-6uBtdkw3jHXkPtx/e9xB/5vcngMm17CyJYsS2YZeQ+9FdRnt6Ev5g931Sg2p+dxbtMGoCm13m3ax/obicTZIkQ==
dependencies:
core-js "^3.4.1"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
tslib@^1.9.0:
version "1.14.1"
resolved "https://registry.yarnpkg.com/tslib/-/tslib-1.14.1.tgz#cf2d38bdc34a134bcaf1091c41f6619e2f672d00"
integrity sha512-Xni35NKzjgMrwevysHTCArtLDpPvye8zV/0E4EyYn43P7/7qvQwPh9BGkHewbMulVntbigmcT7rdX3BNo9wRJg==
Add eslint and babel-eslint to yarn dev dependencies.
2017-12-22 00:24:17 -05:00
DEV: Update linting setup (#23434) * Update eslint-config-discourse * Update eslint-plugin-ember * Update ember-template-lint * Update concurrently * Update glint * Dedup + yarn * Whitespace fix
2023-09-06 08:23:06 -04:00
tslib@^2.0.1, tslib@^2.0.3, tslib@^2.1.0, tslib@^2.4.1:
version "2.6.2"
resolved "https://registry.yarnpkg.com/tslib/-/tslib-2.6.2.tgz#703ac29425e7b37cd6fd456e92404d46d1f3e4ae"
integrity sha512-AEYxH93jGFPn/a2iVAwW87VuUIkR1FVUKB77NwMF7nBTDkDrrT/Hpt/IrCJ0QXhW27jTBDcf5ZY7w6RiqTMw2Q==
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
type-check@^0.4.0, type-check@~0.4.0:
version "0.4.0"
resolved "https://registry.yarnpkg.com/type-check/-/type-check-0.4.0.tgz#07b8203bfa7056c0657050e3ccd2c37730bab8f1"
integrity sha512-XleUoc9uwGXqjWwXaUTZAmzMcFZ5858QA2vvx1Ur5xIcixXIP+8LnFDgRplU30us6teqdlskFfu+ae4K79Ooew==
dependencies:
prelude-ls "^1.2.1"
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
type-detect@^4.0.0, type-detect@^4.0.5:
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
version "4.0.8"
resolved "https://registry.yarnpkg.com/type-detect/-/type-detect-4.0.8.tgz#7646fb5f18871cfbb7749e69bd39a6388eb7450c"
integrity sha512-0fr/mIH1dlO+x7TlcMy+bIDqKPsw/70tVyeHW787goQjhmqaZe10uwLujubK9q9Lg6Fiho1KUKDYz0Z7k7g5/g==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
type-fest@^0.20.2:
version "0.20.2"
resolved "https://registry.yarnpkg.com/type-fest/-/type-fest-0.20.2.tgz#1bf207f4b28f91583666cb5fbd327887301cd5f4"
integrity sha512-Ne+eE4r0/iWnpAxD852z3A+N0Bt5RN//NjJwRd2VFHEmrywxf5vsZlh4R6lixl6B+wz/8d+maTSAkN1FIkI3LQ==
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
typed-array-buffer@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/typed-array-buffer/-/typed-array-buffer-1.0.0.tgz#18de3e7ed7974b0a729d3feecb94338d1472cd60"
integrity sha512-Y8KTSIglk9OZEr8zywiIHG/kmQ7KWyjseXs1CbSo8vC42w7hg2HgYTxSWwP0+is7bWDc1H+Fo026CpHFwm8tkw==
dependencies:
call-bind "^1.0.2"
get-intrinsic "^1.2.1"
is-typed-array "^1.1.10"
typed-array-byte-length@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/typed-array-byte-length/-/typed-array-byte-length-1.0.0.tgz#d787a24a995711611fb2b87a4052799517b230d0"
integrity sha512-Or/+kvLxNpeQ9DtSydonMxCx+9ZXOswtwJn17SNLvhptaXYDJvkFFP5zbfU/uLmvnBJlI4yrnXRxpdWH/M5tNA==
dependencies:
call-bind "^1.0.2"
for-each "^0.3.3"
has-proto "^1.0.1"
is-typed-array "^1.1.10"
typed-array-byte-offset@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/typed-array-byte-offset/-/typed-array-byte-offset-1.0.0.tgz#cbbe89b51fdef9cd6aaf07ad4707340abbc4ea0b"
integrity sha512-RD97prjEt9EL8YgAgpOkf3O4IF9lhJFr9g0htQkm0rchFp/Vx7LW5Q8fSXXub7BXAODyUQohRMyOc3faCPd0hg==
dependencies:
available-typed-arrays "^1.0.5"
call-bind "^1.0.2"
for-each "^0.3.3"
has-proto "^1.0.1"
is-typed-array "^1.1.10"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
typed-array-length@^1.0.4:
version "1.0.4"
resolved "https://registry.yarnpkg.com/typed-array-length/-/typed-array-length-1.0.4.tgz#89d83785e5c4098bec72e08b319651f0eac9c1bb"
integrity sha512-KjZypGq+I/H7HI5HlOoGHkWUUGq+Q0TPhQurLbyrVrvnKTBgzLhIJ7j6J/XTQOi0d1RjyZ0wdas8bKs2p0x3Ng==
dependencies:
call-bind "^1.0.2"
for-each "^0.3.3"
is-typed-array "^1.1.9"
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
typescript@^5.1.3:
Revert "DEV: FloatKit (#23541)" (#23549) This reverts commits 0623ac684a65f95ce4f5438ff47944b1dc2119f4 408e71e437ef8abf98f93e3449898bf906766b0e a32fa3b9470dde0543fcee809f2abd1f219f7336 User tips were running into some issues.
2023-09-12 13:55:12 -04:00
version "5.1.6"
resolved "https://registry.yarnpkg.com/typescript/-/typescript-5.1.6.tgz#02f8ac202b6dad2c0dd5e0913745b47a37998274"
integrity sha512-zaWCozRZ6DLEWAWFrVDz1H6FVXzUSfTy5FUMWsQlU8Ym5JP9eO4xkTIROFCQvhQf61z6O/G6ugw3SgAnvvm+HA==
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
DEV: introduces documentation for chat (#19772) Note this commit also slightly changes internal API: channel instead of getChannel and updateCurrentUserChannelNotificationsSettings instead of updateCurrentUserChatChannelNotificationsSettings. Also destroyChannel takes a second param which is the name confirmation instead of an optional object containing this confirmation. This is to enforce the fact that it's required. In the future a top level jsdoc config file could be used instead of the hack tempfile, but while it's only an experiment for chat, it's probably good enough.
2023-01-18 06:36:16 -05:00
uc.micro@^1.0.1, uc.micro@^1.0.5:
version "1.0.6"
resolved "https://registry.yarnpkg.com/uc.micro/-/uc.micro-1.0.6.tgz#9c411a802a409a91fc6cf74081baba34b24499ac"
integrity sha512-8Y75pvTYkLJW2hWQHXxoqRgV7qb9B+9vFEtidML+7koHUFapnVJAZ6cKs+Qjz5Aw3aZWHMC6u0wJE3At+nSGwA==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
unbox-primitive@^1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/unbox-primitive/-/unbox-primitive-1.0.2.tgz#29032021057d5e6cdbd08c5129c226dff8ed6f9e"
integrity sha512-61pPlCD9h51VoreyJ0BReideM3MDKMKnh6+V9L08331ipq6Q8OFXZYiqP6n/tbHx4s5I9uRhcye6BrbkizkBDw==
dependencies:
call-bind "^1.0.2"
has-bigints "^1.0.2"
has-symbols "^1.0.3"
which-boxed-primitive "^1.0.2"
DEV: Switch from puppeteer to puppeteer-core for smoke test (#15262) `puppeteer` includes a full chromium binary, which adds more than 300mb to our node_modules directory in development/test mode (and therefore the `discourse_dev` and `discourse_test` docker images). We already reach out to the system copy of Chrome for our qunit tests, and already have chrome installed in our `discourse_dev`/`discourse_test` docker images, so it's much more efficient to switch to `puppeteer-core` which doesn't include the chromium binary.
2021-12-13 04:31:49 -05:00
unbzip2-stream@1.4.3:
version "1.4.3"
resolved "https://registry.yarnpkg.com/unbzip2-stream/-/unbzip2-stream-1.4.3.tgz#b0da04c4371311df771cdc215e87f2130991ace7"
integrity sha512-mlExGW4w71ebDJviH16lQLtZS32VKqsSfk80GCfUlwT/4/hNRFsoscrF/c++9xinkMzECL1uL9DDwXqFWkruPg==
dependencies:
buffer "^5.2.1"
through "^2.3.8"
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
unc-path-regex@^0.1.2:
version "0.1.2"
resolved "https://registry.yarnpkg.com/unc-path-regex/-/unc-path-regex-0.1.2.tgz#e73dd3d7b0d7c5ed86fbac6b0ae7d8c6a69d50fa"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-eXL4nmJT7oCpkZsHZUOJo8hcX3GbsiDOa0Qu9F646fi8dT3XuSVopVqAcEiVzSKKH7UoDti23wNX3qGFxcW5Qg==
underscore.string@~3.3.4:
version "3.3.6"
resolved "https://registry.yarnpkg.com/underscore.string/-/underscore.string-3.3.6.tgz#ad8cf23d7423cb3b53b898476117588f4e2f9159"
integrity sha512-VoC83HWXmCrF6rgkyxS9GHv8W9Q5nhMKho+OadDJGzL2oDYbYEppBaCMH6pFlwLeqj2QS+hhkw2kpXkSdD1JxQ==
dependencies:
sprintf-js "^1.1.1"
util-deprecate "^1.0.2"
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
underscore@~1.13.2:
DEV: introduces documentation for chat (#19772) Note this commit also slightly changes internal API: channel instead of getChannel and updateCurrentUserChannelNotificationsSettings instead of updateCurrentUserChatChannelNotificationsSettings. Also destroyChannel takes a second param which is the name confirmation instead of an optional object containing this confirmation. This is to enforce the fact that it's required. In the future a top level jsdoc config file could be used instead of the hack tempfile, but while it's only an experiment for chat, it's probably good enough.
2023-01-18 06:36:16 -05:00
version "1.13.6"
resolved "https://registry.yarnpkg.com/underscore/-/underscore-1.13.6.tgz#04786a1f589dc6c09f761fc5f45b89e935136441"
integrity sha512-+A5Sja4HP1M08MaXya7p5LvjuM7K6q/2EaC0+iovj/wOcMsTzMvDFbasi/oSapiwOlt252IqsKqPjCl7huKS0A==
DEV: Bump `@mixer/parallel-prettier` (#19053)
2022-11-16 15:38:57 -05:00
unique-stream@^2.3.1:
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
version "2.3.1"
resolved "https://registry.yarnpkg.com/unique-stream/-/unique-stream-2.3.1.tgz#c65d110e9a4adf9a6c5948b28053d9a8d04cbeac"
integrity sha512-2nY4TnBE70yoxHkDli7DMazpWiP7xMdCYqU2nBRO0UB+ZpEkGsSija7MvmvnZFUeC+mrgiUfcHSr3LmRFIg4+A==
dependencies:
json-stable-stringify-without-jsonify "^1.0.1"
through2-filter "^3.0.0"
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
universalify@^0.1.0:
version "0.1.2"
resolved "https://registry.yarnpkg.com/universalify/-/universalify-0.1.2.tgz#b646f69be3942dabcecc9d6639c80dc105efaa66"
integrity sha512-rBJeI5CXAlmy1pV+617WB9J63U6XcazHHF2f2dbJix4XzpUF0RS3Zbj0FGIOCAva5P/d/GBOYaACQ1w+0azUkg==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
universalify@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/universalify/-/universalify-2.0.0.tgz#75a4984efedc4b08975c5aeb73f530d02df25717"
integrity sha512-hAZsKq7Yy11Zu1DE0OzWjw7nnLZmJZYTDZZyEFHZdUhV8FkH5MCfoU1XMaxXovpyW5nq5scPqq0ZDP9Zyl04oQ==
upath@^2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/upath/-/upath-2.0.1.tgz#50c73dea68d6f6b990f51d279ce6081665d61a8b"
integrity sha512-1uEe95xksV1O0CYKXo8vQvN1JEbtJp7lb7C5U9HMsIp6IVwntkH/oNUzyVNQSd4S1sYk2FpSSW44FqMc8qee5w==
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
update-browserslist-db@^1.0.13:
version "1.0.13"
resolved "https://registry.yarnpkg.com/update-browserslist-db/-/update-browserslist-db-1.0.13.tgz#3c5e4f5c083661bd38ef64b6328c26ed6c8248c4"
integrity sha512-xebP81SNcPuNpPP3uzeW1NYXxI3rxyJzF3pD6sH4jE7o/IX+WtSpwnVU+qIsDPyk0d3hmFQ7mjqc6AtV604hbg==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
dependencies:
escalade "^3.1.1"
picocolors "^1.0.0"
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
uri-js@^4.2.2:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "4.4.1"
resolved "https://registry.yarnpkg.com/uri-js/-/uri-js-4.4.1.tgz#9b1a52595225859e55f669d928f88c6c57f2a77e"
integrity sha512-7rKUyy33Q1yc98pQ1DAmLtwX109F7TIfWlW1Ydo8Wl1ii1SeHieeh0HHfPeL2fMXK6z0s8ecKs9frCuLJvndBg==
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
dependencies:
punycode "^2.1.0"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
username-sync@^1.0.2:
version "1.0.3"
resolved "https://registry.yarnpkg.com/username-sync/-/username-sync-1.0.3.tgz#ae41c5c8a4c8c2ecc1443a7d0742742bd7e36732"
integrity sha512-m/7/FSqjJNAzF2La448c/aEom0gJy7HY7Y509h6l0ePvEkFictAGptwWaj1msWJ38JbfEDOUoE8kqFee9EHKdA==
util-deprecate@^1.0.1, util-deprecate@^1.0.2, util-deprecate@~1.0.1:
Add smoke test script that runs in chrome headless.
2017-12-18 03:32:58 -05:00
version "1.0.2"
resolved "https://registry.yarnpkg.com/util-deprecate/-/util-deprecate-1.0.2.tgz#450d4dc9fa70de732762fbd2d4a28981419a0ccf"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-EPD5q1uXyFxJpCrLnCc1nHnq3gOa6DZBocAIiI2TaSCA7VCJ1UJDMagCzIkXNsUYfD1daK//LTEQ8xiIbrHtcw==
Add smoke test script that runs in chrome headless.
2017-12-18 03:32:58 -05:00
DEV: Chat service object initial implementation (#19814) This is a combined work of Martin Brennan, Loïc Guitaut, and Joffrey Jaffeux. --- This commit implements a base service object when working in chat. The documentation is available at https://discourse.github.io/discourse/chat/backend/Chat/Service.html Generating documentation has been made as part of this commit with a bigger goal in mind of generally making it easier to dive into the chat project. Working with services generally involves 3 parts: - The service object itself, which is a series of steps where few of them are specialized (model, transaction, policy) ```ruby class UpdateAge include Chat::Service::Base model :user, :fetch_user policy :can_see_user contract step :update_age class Contract attribute :age, :integer end def fetch_user(user_id:, **) User.find_by(id: user_id) end def can_see_user(guardian:, **) guardian.can_see_user(user) end def update_age(age:, **) user.update!(age: age) end end ``` - The `with_service` controller helper, handling success and failure of the service within a service and making easy to return proper response to it from the controller ```ruby def update with_service(UpdateAge) do on_success { render_serialized(result.user, BasicUserSerializer, root: "user") } end end ``` - Rspec matchers and steps inspector, improving the dev experience while creating specs for a service ```ruby RSpec.describe(UpdateAge) do subject(:result) do described_class.call(guardian: guardian, user_id: user.id, age: age) end fab!(:user) { Fabricate(:user) } fab!(:current_user) { Fabricate(:admin) } let(:guardian) { Guardian.new(current_user) } let(:age) { 1 } it { expect(user.reload.age).to eq(age) } end ``` Note in case of unexpected failure in your spec, the output will give all the relevant information: ``` 1) UpdateAge when no channel_id is given is expected to fail to find a model named 'user' Failure/Error: it { is_expected.to fail_to_find_a_model(:user) } Expected model 'foo' (key: 'result.model.user') was not found in the result object. [1/4] [model] 'user' ❌ [2/4] [policy] 'can_see_user' [3/4] [contract] 'default' [4/4] [step] 'update_age' /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/update_age.rb:32:in `fetch_user': missing keyword: :user_id (ArgumentError) from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:202:in `instance_exec' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:202:in `call' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:219:in `call' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:417:in `block in run!' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:417:in `each' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:417:in `run!' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:411:in `run' from <internal:kernel>:90:in `tap' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/app/services/base.rb:302:in `call' from /Users/joffreyjaffeux/Code/pr-discourse/plugins/chat/spec/services/update_age_spec.rb:15:in `block (3 levels) in <main>' ```
2023-02-13 07:09:57 -05:00
util@^0.10.3:
version "0.10.4"
resolved "https://registry.yarnpkg.com/util/-/util-0.10.4.tgz#3aa0125bfe668a4672de58857d3ace27ecb76901"
integrity sha512-0Pm9hTQ3se5ll1XihRic3FDIku70C+iHUdT/W926rSgHV5QgXsYbKZN8MSC3tJtSkhuROzvsQjAaFENRXr+19A==
dependencies:
inherits "2.0.3"
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
uuid@^8.3.2:
version "8.3.2"
resolved "https://registry.yarnpkg.com/uuid/-/uuid-8.3.2.tgz#80d5b5ced271bb9af6c445f21a1a04c606cefbe2"
integrity sha512-+NYs2QeMWy+GWFOEm9xnn6HCDp0l7QBD7ml8zLUmJ+93Q5NF0NocErnwkTkXVFNiX3/fpC6afS8Dhb/gz7R7eg==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
v8-compile-cache@^2.3.0:
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
version "2.4.0"
resolved "https://registry.yarnpkg.com/v8-compile-cache/-/v8-compile-cache-2.4.0.tgz#cdada8bec61e15865f05d097c5f4fd30e94dc128"
integrity sha512-ocyWc3bAHBB/guyqJQVI5o4BZkPhznPYUG2ea80Gond/BgNWpap8TOmLSeeQG7bnh2KMISxskdADG59j7zruhw==
DEV: upgrades dev config (#10588)
2020-09-04 07:33:03 -04:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
validate-peer-dependencies@^1.1.0:
version "1.2.0"
resolved "https://registry.yarnpkg.com/validate-peer-dependencies/-/validate-peer-dependencies-1.2.0.tgz#22aab93c514f4fda457d36c80685e8b1160d2036"
integrity sha512-nd2HUpKc6RWblPZQ2GDuI65sxJ2n/UqZwSBVtj64xlWjMx0m7ZB2m9b2JS3v1f+n9VWH/dd1CMhkHfP6pIdckA==
dependencies:
resolve-package-path "^3.1.0"
semver "^7.3.2"
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
vscode-jsonrpc@8.1.0:
version "8.1.0"
resolved "https://registry.yarnpkg.com/vscode-jsonrpc/-/vscode-jsonrpc-8.1.0.tgz#cb9989c65e219e18533cc38e767611272d274c94"
integrity sha512-6TDy/abTQk+zDGYazgbIPc+4JoXdwC8NHU9Pbn4UJP1fehUyZmM4RHp5IthX7A6L5KS30PRui+j+tbbMMMafdw==
vscode-languageserver-protocol@3.17.3:
version "3.17.3"
resolved "https://registry.yarnpkg.com/vscode-languageserver-protocol/-/vscode-languageserver-protocol-3.17.3.tgz#6d0d54da093f0c0ee3060b81612cce0f11060d57"
integrity sha512-924/h0AqsMtA5yK22GgMtCYiMdCOtWTSGgUOkgEDX+wk2b0x4sAfLiO4NxBxqbiVtz7K7/1/RgVrVI0NClZwqA==
dependencies:
vscode-jsonrpc "8.1.0"
vscode-languageserver-types "3.17.3"
vscode-languageserver-textdocument@^1.0.5:
version "1.0.8"
resolved "https://registry.yarnpkg.com/vscode-languageserver-textdocument/-/vscode-languageserver-textdocument-1.0.8.tgz#9eae94509cbd945ea44bca8dcfe4bb0c15bb3ac0"
integrity sha512-1bonkGqQs5/fxGT5UchTgjGVnfysL0O8v1AYMBjqTbWQTFn721zaPGDYFkOKtfDgFiSgXM3KwaG3FMGfW4Ed9Q==
vscode-languageserver-types@3.17.3:
version "3.17.3"
resolved "https://registry.yarnpkg.com/vscode-languageserver-types/-/vscode-languageserver-types-3.17.3.tgz#72d05e47b73be93acb84d6e311b5786390f13f64"
integrity sha512-SYU4z1dL0PyIMd4Vj8YOqFvHu7Hz/enbWtpfnVbJHU4Nd1YNYx8u0ennumc6h48GQNeOLxmwySmnADouT/AuZA==
vscode-languageserver@^8.0.1:
version "8.1.0"
resolved "https://registry.yarnpkg.com/vscode-languageserver/-/vscode-languageserver-8.1.0.tgz#5024253718915d84576ce6662dd46a791498d827"
integrity sha512-eUt8f1z2N2IEUDBsKaNapkz7jl5QpskN2Y0G01T/ItMxBxw1fJwvtySGB9QMecatne8jFIWJGWI61dWjyTLQsw==
dependencies:
vscode-languageserver-protocol "3.17.3"
vscode-uri@^3.0.2:
version "3.0.7"
resolved "https://registry.yarnpkg.com/vscode-uri/-/vscode-uri-3.0.7.tgz#6d19fef387ee6b46c479e5fb00870e15e58c1eb8"
integrity sha512-eOpPHogvorZRobNqJGhapa0JdwaxpjVvyBp0QIUMRMSf8ZAlqOdEquKuRmw9Qwu0qXtJIWqFtMkmvJjUZmMjVA==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
walk-sync@^0.3.1, walk-sync@^0.3.3:
version "0.3.4"
resolved "https://registry.yarnpkg.com/walk-sync/-/walk-sync-0.3.4.tgz#cf78486cc567d3a96b5b2237c6108017a5ffb9a4"
integrity sha512-ttGcuHA/OBnN2pcM6johpYlEms7XpO5/fyKIr48541xXedan4roO8cS1Q2S/zbbjGH/BarYDAMeS2Mi9HE5Tig==
dependencies:
ensure-posix-path "^1.0.0"
matcher-collection "^1.0.0"
walk-sync@^1.0.0, walk-sync@^1.1.3:
version "1.1.4"
resolved "https://registry.yarnpkg.com/walk-sync/-/walk-sync-1.1.4.tgz#81049f3d8095479b49574cfa5f558d7a252b127d"
integrity sha512-nowc9thB/Jg0KW4TgxoRjLLYRPvl3DB/98S89r4ZcJqq2B0alNcKDh6pzLkBSkPMzRSMsJghJHQi79qw0YWEkA==
dependencies:
"@types/minimatch" "^3.0.3"
ensure-posix-path "^1.1.0"
matcher-collection "^1.1.1"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
walk-sync@^2.2.0:
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
version "2.2.0"
resolved "https://registry.yarnpkg.com/walk-sync/-/walk-sync-2.2.0.tgz#80786b0657fcc8c0e1c0b1a042a09eae2966387a"
integrity sha512-IC8sL7aB4/ZgFcGI2T1LczZeFWZ06b3zoHH7jBPyHxOtIIz1jppWHjjEXkOFvFojBVAK9pV7g47xOZ4LW3QLfg==
dependencies:
"@types/minimatch" "^3.0.3"
ensure-posix-path "^1.1.0"
matcher-collection "^2.0.0"
minimatch "^3.0.4"
walk-sync@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/walk-sync/-/walk-sync-3.0.0.tgz#67f882925021e20569a1edd560b8da31da8d171c"
integrity sha512-41TvKmDGVpm2iuH7o+DAOt06yyu/cSHpX3uzAwetzASvlNtVddgIjXIb2DfB/Wa20B1Jo86+1Dv1CraSU7hWdw==
dependencies:
"@types/minimatch" "^3.0.4"
ensure-posix-path "^1.1.0"
matcher-collection "^2.0.1"
minimatch "^3.0.4"
DEV: Upgrade "lefthook" and skip hooks during merge/rebase (#18910) The old lefthook package was deprecated a long time ago and skipping hooks during merge/rebase makes those git commands a lot faster.
2022-11-07 11:13:21 -05:00
wasm-feature-detect@^1.2.11:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "1.5.1"
resolved "https://registry.yarnpkg.com/wasm-feature-detect/-/wasm-feature-detect-1.5.1.tgz#0db57a7d7f8c26b743dde85386215ae2b135e78a"
integrity sha512-GHr23qmuehNXHY4902/hJ6EV5sUANIJC3R/yMfQ7hWDg3nfhlcJfnIL96R2ohpIwa62araN6aN4bLzzzq5GXkg==
FEATURE: Optimize images before upload (#13432) Integrates [mozJPEG](https://github.com/mozilla/mozjpeg) and [Resize](https://github.com/PistonDevelopers/resize) using WebAssembly to optimize user uploads in the composer on the client-side. NPM libraries are sourced from our [Squoosh fork](https://github.com/discourse/squoosh/tree/discourse), which was needed because we have an older asset pipeline.
2021-06-23 11:31:12 -04:00
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
wcwidth@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/wcwidth/-/wcwidth-1.0.1.tgz#f0b0dcf915bc5ff1528afadb2c0e17b532da2fe8"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-XHPEwS0q6TaxcvG85+8EYkbiCux2XtWG2mkc47Ng2A77BQu9+DqIOJldST4HgPkuea7dvKSj5VgX3P1d4rW8Tg==
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
dependencies:
defaults "^1.0.3"
DEV: Switch from puppeteer to puppeteer-core for smoke test (#15262) `puppeteer` includes a full chromium binary, which adds more than 300mb to our node_modules directory in development/test mode (and therefore the `discourse_dev` and `discourse_test` docker images). We already reach out to the system copy of Chrome for our qunit tests, and already have chrome installed in our `discourse_dev`/`discourse_test` docker images, so it's much more efficient to switch to `puppeteer-core` which doesn't include the chromium binary.
2021-12-13 04:31:49 -05:00
webidl-conversions@^3.0.0:
version "3.0.1"
resolved "https://registry.yarnpkg.com/webidl-conversions/-/webidl-conversions-3.0.1.tgz#24534275e2a7bc6be7bc86611cc16ae0a5654871"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-2JAn3z8AR6rjK8Sm8orRC0h/bcl/DqL7tRPdGZ4I1CjdF+EaMLmYxBHyXuKL849eucPFhvBoxMsflfOb8kxaeQ==
DEV: Switch from puppeteer to puppeteer-core for smoke test (#15262) `puppeteer` includes a full chromium binary, which adds more than 300mb to our node_modules directory in development/test mode (and therefore the `discourse_dev` and `discourse_test` docker images). We already reach out to the system copy of Chrome for our qunit tests, and already have chrome installed in our `discourse_dev`/`discourse_test` docker images, so it's much more efficient to switch to `puppeteer-core` which doesn't include the chromium binary.
2021-12-13 04:31:49 -05:00
whatwg-url@^5.0.0:
version "5.0.0"
resolved "https://registry.yarnpkg.com/whatwg-url/-/whatwg-url-5.0.0.tgz#966454e8765462e37644d3626f6742ce8b70965d"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-saE57nupxk6v3HY35+jzBwYa0rKSy0XR8JSxZPwgLr7ys0IBzhGviA1/TUGJLmSVqs8pb9AnvICXEuOHLprYTw==
DEV: Switch from puppeteer to puppeteer-core for smoke test (#15262) `puppeteer` includes a full chromium binary, which adds more than 300mb to our node_modules directory in development/test mode (and therefore the `discourse_dev` and `discourse_test` docker images). We already reach out to the system copy of Chrome for our qunit tests, and already have chrome installed in our `discourse_dev`/`discourse_test` docker images, so it's much more efficient to switch to `puppeteer-core` which doesn't include the chromium binary.
2021-12-13 04:31:49 -05:00
dependencies:
tr46 "~0.0.3"
webidl-conversions "^3.0.0"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
which-boxed-primitive@^1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/which-boxed-primitive/-/which-boxed-primitive-1.0.2.tgz#13757bc89b209b049fe5d86430e21cf40a89a8e6"
integrity sha512-bwZdv0AKLpplFY2KZRX6TvyuN7ojjr7lwkg6ml0roIy9YeuSr7JS372qlNW18UQYzgYK9ziGcerWqZOmEn9VNg==
dependencies:
is-bigint "^1.0.1"
is-boolean-object "^1.1.0"
is-number-object "^1.0.4"
is-string "^1.0.5"
is-symbol "^1.0.3"
DEV: Update eslint-config-discourse
2023-10-10 13:50:47 -04:00
which-typed-array@^1.1.11:
version "1.1.11"
resolved "https://registry.yarnpkg.com/which-typed-array/-/which-typed-array-1.1.11.tgz#99d691f23c72aab6768680805a271b69761ed61a"
integrity sha512-qe9UWWpkeG5yzZ0tNYxDmd7vo58HDBc39mZ0xWWpolAGADdFOzkfamWLDxkOWcvHQKVmdTyQdLD4NOfjLWTKew==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
dependencies:
available-typed-arrays "^1.0.5"
call-bind "^1.0.2"
for-each "^0.3.3"
gopd "^1.0.1"
has-tostringtag "^1.0.0"
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
which@^2.0.1:
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
version "2.0.2"
resolved "https://registry.yarnpkg.com/which/-/which-2.0.2.tgz#7c6a8dd0a636a0327e10b59c9286eee93f3f51b1"
integrity sha512-BLI3Tl1TW3Pvl70l3yq3Y64i+awpwXqsGBYWkkqMtnbXgrMD+yj7rhW0kuEDxzJaYXGjEW5ogapKNMEKNMjibA==
Manage qunit via yarn.
2018-09-11 03:07:28 -04:00
dependencies:
isexe "^2.0.0"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
workerpool@^6.4.0:
DEV: Use `@discourse/lint-configs` (#24038)
2023-10-23 06:08:35 -04:00
version "6.5.1"
resolved "https://registry.yarnpkg.com/workerpool/-/workerpool-6.5.1.tgz#060f73b39d0caf97c6db64da004cd01b4c099544"
integrity sha512-Fs4dNYcsdpYSAfVxhnl1L5zTksjvOJxtC5hzMNl+1t9B8hTJTdKDyZ5ju7ztgPy+ft9tBFXoOlDNiOT9WUXZlA==
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
wrap-ansi@^7.0.0:
version "7.0.0"
resolved "https://registry.yarnpkg.com/wrap-ansi/-/wrap-ansi-7.0.0.tgz#67e145cff510a6a6984bdf1152911d69d2eb9e43"
integrity sha512-YVGIj2kamLSTxw6NsZjoBxfSwsn0ycdesmc4p+Q21c5zPuZ1pl+NfxVdxPtdHvmNVOQ6XSYG4AUtyt/Fi7D16Q==
DEV: upgrades ember-template-lint 2.5.2 (#9411)
2020-04-13 18:43:55 -04:00
dependencies:
ansi-styles "^4.0.0"
string-width "^4.1.0"
strip-ansi "^6.0.0"
Run JS test in chrome headless on Travis.
2017-12-14 21:15:04 -05:00
wrappy@1:
version "1.0.2"
resolved "https://registry.yarnpkg.com/wrappy/-/wrappy-1.0.2.tgz#b5243d8f3ec1aa35f1364605bc0d1036e30ab69f"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-l4Sp/DRseor9wL6EvV2+TuQn63dMkPjZ/sp9XkghTEbV9KlPS1xUsZ3u7/IQO4wxtcFB4bgpQPRcR3QCvezPcQ==
Run JS test in chrome headless on Travis.
2017-12-14 21:15:04 -05:00
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
ws@8.13.0:
version "8.13.0"
resolved "https://registry.yarnpkg.com/ws/-/ws-8.13.0.tgz#9a9fb92f93cf41512a0735c8f4dd09b8a1211cd0"
integrity sha512-x9vcZYTrFPC7aSIbj7sRCYo7L/Xb8Iy+pW0ng0wt2vCJv7M9HOMy0UoN3rr+IFC7hb7vXoqS+P9ktyLLLhO+LA==
DEV: Fix the smoke test
2019-05-21 13:01:29 -04:00
DEV: Bump chrome-launcher/chrome-remote-interface (#16160)
2022-03-12 13:52:07 -05:00
ws@^7.2.0:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "7.5.9"
resolved "https://registry.yarnpkg.com/ws/-/ws-7.5.9.tgz#54fa7db29f4c7cec68b1ddd3a89de099942bb591"
integrity sha512-F+P9Jil7UiSKSkppIiD94dN07AwvFixvLIj1Og1Rl9GGMuNipJnV9JzjD6XuqmAeiswGvUmNLjr5cFuXwNS77Q==
DEV: Bump chrome-launcher/chrome-remote-interface (#16160)
2022-03-12 13:52:07 -05:00
DEV: introduces documentation for chat (#19772) Note this commit also slightly changes internal API: channel instead of getChannel and updateCurrentUserChannelNotificationsSettings instead of updateCurrentUserChatChannelNotificationsSettings. Also destroyChannel takes a second param which is the name confirmation instead of an optional object containing this confirmation. This is to enforce the fact that it's required. In the future a top level jsdoc config file could be used instead of the hack tempfile, but while it's only an experiment for chat, it's probably good enough.
2023-01-18 06:36:16 -05:00
xmlcreate@^2.0.4:
version "2.0.4"
resolved "https://registry.yarnpkg.com/xmlcreate/-/xmlcreate-2.0.4.tgz#0c5ab0f99cdd02a81065fa9cd8f8ae87624889be"
integrity sha512-nquOebG4sngPmGPICTS5EnxqhKbCmz5Ox5hsszI2T6U5qdrJizBc+0ilYSEjTSzU0yZcmvppztXe/5Al5fUwdg==
Revert "DEV: Merge package.json files (#21172)" (#21182) This reverts commit 49a1e1cd0eac1af823963b9095ac65329d330daf. Is causing issues in prod-adjacent environments (Jenkins)
2023-04-20 08:57:40 -04:00
xtend@~4.0.0, xtend@~4.0.1:
DEV: experiments parallel prettier (#11854) For now only attempts to use it in pre-commit hook
2021-01-27 11:25:48 -05:00
version "4.0.2"
resolved "https://registry.yarnpkg.com/xtend/-/xtend-4.0.2.tgz#bb72779f5fa465186b1f438f674fa347fdb5db54"
integrity sha512-LKYU1iAXJXUgAXn9URjiu+MWhyUXHsvfp7mcuYm9dSUKK0/CjtrUwFAxD82/mCWbtLsGjFIad0wIsod4zrTAEQ==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
y18n@^5.0.5:
version "5.0.8"
resolved "https://registry.yarnpkg.com/y18n/-/y18n-5.0.8.tgz#7f4934d0f7ca8c56f95314939ddcd2dd91ce1d55"
integrity sha512-0pfFzegeDWJHJIAmTLRP2DwHjdF5s7jo9tuztdQxAhINCdvS+3nGINqPd00AphqJR/0LhANUS6/+7SCb98YOfA==
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
yallist@^3.0.2:
version "3.1.1"
resolved "https://registry.yarnpkg.com/yallist/-/yallist-3.1.1.tgz#dbb7daf9bfd8bac9ab45ebf602b8cbad0d5d08fd"
integrity sha512-a4UGQaWPH59mOXUYnAG2ewncQS4i4F43Tv3JoAM+s2VDAmS9NsK8GpDMLrCHPksFT7h3K6TOoUNn2pb7RoXx4g==
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04:00
yallist@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/yallist/-/yallist-4.0.0.tgz#9bb92790d9c0effec63be73519e11a35019a3a72"
integrity sha512-3wdGidZyq5PB084XLES5TpOSRA3wjXAlIWMhum2kRcv/41Sn2emQ0dycQW4uZXLejwKvg6EsvbdlVL+FYEct7A==
yargs-parser@^21.1.1:
version "21.1.1"
resolved "https://registry.yarnpkg.com/yargs-parser/-/yargs-parser-21.1.1.tgz#9096bceebf990d21bb31fa9516e0ede294a77d35"
integrity sha512-tVpsJW7DdjecAiFpbIB1e3qxIQsE6NoPc5/eTdrbbIC4h0LVsWhnoa3g+m2HclBIujHzsxZ4VJVA+GUuc2/LBw==
FIX: use the latest version of `puppeteer-core` package to fix `page.click` issue (#22989) Previously, the `page.click` method randomly failed in some situations.
2023-08-16 01:06:45 -04:00
yargs@17.7.1:
version "17.7.1"
resolved "https://registry.yarnpkg.com/yargs/-/yargs-17.7.1.tgz#34a77645201d1a8fc5213ace787c220eabbd0967"
integrity sha512-cwiTb08Xuv5fqF4AovYacTFNxk62th7LKJ6BL9IGUpTJrWoU7/7WdQGTP2SjKf1dUNBGzDd28p/Yfs/GI6JrLw==
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"
DEV: introduce Ember `<template>` tag support (.gjs) (#22719) The gjs/gts formats are a new pattern for authoring Ember components. This commit introduces support for these patterns to our build pipeline for core/plugins, and converts a handful of components to use the new format. It also introduces relevant updates to our linting config, and to our sample vscode configuration. Co-authored-by: Godfrey Chan <godfreykfc@gmail.com> Co-authored-by: Krystan HuffMenne <kmenne+github@gmail.com>
2023-07-20 16:01:12 -04:00
yargs@^17.5.1, yargs@^17.7.2:
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
version "17.7.2"
resolved "https://registry.yarnpkg.com/yargs/-/yargs-17.7.2.tgz#991df39aca675a192b816e1e0363f9d75d2aa269"
integrity sha512-7dSzzRQ++CKnNI/krKnYRV7JKKPUXMEh61soaHKg9mrWEhzFWhFnxPxGl+69cD1Ou63C13NUPCnmIcrvqCuM6w==
DEV: Setup lint to the future (#20990) ## How does this work? Any time a lint rule is added or changed, you can run `yarn lint:fix` to handle all the auto-fixable situations. But not all lints are auto-fixable -- for those, lint-to-the-future has tooling to automatically ignore present violations. An alias has been added for lint-to-the-future to ignore new violations, `yarn lttf:ignore`. The command will add lint-ignore declarations throughout all the files with present violations, which should then be committed. An excerpt from lint-to-the-future's [README](https://github.com/mansona/lint-to-the-future#lint-to-the-future-dashboard): > The point of Lint to the Future is to allow you to progressively update your codebase using new lint rules without overwhelming you with the task. You can easily ignore lint rules using project-based ignores in your config files but that doesn't prevent you from making the same errors in new files. > We chose to do the ignores on a file basis as it is a perfect balance and it means that the tracking/graphing aspects of Lint to the Future provide you with achievable goals, especially in large codebases. ## How do I view progress? lint-to-the-future provides graphs of violations-over-time per lint rule in a dashboard format, so we can track how well we're doing at cleaning up the violations. To view the dashboard locally, run `yarn lint-progress` and visit `http://localhost:8084` (or whatever the port it chose, as it will choose a new port if 8084 is preoccupied) Also there is a `list` command which shows a JSON object of: ```ts { [date: string]: { // yyyy-mm-dd [pluginName: string]: { [fileName: string]: string[]; // list of files with violations } } } ``` ```bash yarn lint-to-the-future list --stdout ``` ## What about lint-todo? Lint todo is another system available for both eslint and ember-template-lint that _forces_ folks to "leave things better than they found them" by being transparent / line-specific ignoring of violations. It was decided that for _this_ project, it made more sense, and would be less disruptive to new contributors to have the ignore declarations explicitly defined in each file (whereas in lint-todo, they are hidden). To effectively use lint-todo, a whole team needs to agree to the workflow, and in open source, we want "just anyway" to be able to contribute, and throwing surprises at them can deter contributions.
2023-04-06 12:25:01 -04: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"
Update javascripts (#9907)
2020-05-28 12:15:13 -04:00
yauzl@^2.10.0:
version "2.10.0"
resolved "https://registry.yarnpkg.com/yauzl/-/yauzl-2.10.0.tgz#c7eb17c93e112cb1086fa6d8e51fb0667b79a5f9"
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
integrity sha512-p4a9I6X6nu6IhoGmBqAcbJy1mlC4j27vEPZX9F4L4/vZT3Lyq1VkFHw/V/PUcB9Buo+DG3iHkT0x3Qya58zc3g==
Add smoke test script that runs in chrome headless.
2017-12-18 03:32:58 -05:00
dependencies:
Update javascripts (#9907)
2020-05-28 12:15:13 -04:00
buffer-crc32 "~0.2.3"
fd-slicer "~1.1.0"
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
DEV: Update eslint/prettier (#22226)
2023-06-21 14:59:03 -04:00
yocto-queue@^0.1.0:
version "0.1.0"
resolved "https://registry.yarnpkg.com/yocto-queue/-/yocto-queue-0.1.0.tgz#0294eb3dee05028d31ee1a5fa2c556a6aaf10a1b"
integrity sha512-rVksvsnNCdJ/ohGc6xgPwyN8eheCxsiLM8mxuE/t/mOVqJewPuO1miLpTHQiRgTKCLexL4MeAFVagts7HmNZ2Q==
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-07-06 04:37:54 -04:00
yocto-queue@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/yocto-queue/-/yocto-queue-1.0.0.tgz#7f816433fb2cbc511ec8bf7d263c3b58a1a3c251"
integrity sha512-9bnSc/HEW2uRy67wc+T8UwauLuPJVn28jb+GtJY16iiKWyvmYJRXVT4UamsAEGQfPohgr2q4Tq0sQbQlxTfi1g==