2017-12-14 21:15:04 -05:00
|
|
|
{
|
|
|
|
|
"name": "discourse",
|
2024-02-26 08:45:58 -05:00
|
|
|
"private": true,
|
2023-06-30 07:01:45 -04:00
|
|
|
"repository": "https://github.com/discourse/discourse",
|
2017-12-14 21:15:04 -05:00
|
|
|
"author": "Discourse",
|
2020-04-29 12:18:21 -04:00
|
|
|
"license": "GPL-2.0-only",
|
2023-06-30 07:01:45 -04:00
|
|
|
"devDependencies": {
|
2024-10-22 18:28:54 -04:00
|
|
|
"@babel/plugin-proposal-decorators": "^7.25.9",
|
2024-11-20 17:19:06 -05:00
|
|
|
"@discourse/lint-configs": "^2.2.1",
|
2023-08-24 10:36:22 -04:00
|
|
|
"@discourse/moment-timezone-names-translations": "^1.0.0",
|
2024-09-09 09:40:56 -04:00
|
|
|
"@fortawesome/fontawesome-free": "6.6.0",
|
2025-01-08 17:58:23 -05:00
|
|
|
"@glint/core": "^1.5.1",
|
2025-01-09 17:36:40 -05:00
|
|
|
"@glint/environment-ember-loose": "^1.5.1",
|
2024-11-05 10:12:54 -05:00
|
|
|
"@glint/environment-ember-template-imports": "^1.5.0",
|
2025-01-08 19:16:05 -05:00
|
|
|
"@glint/template": "^1.5.1",
|
2023-06-30 07:01:45 -04:00
|
|
|
"@mixer/parallel-prettier": "^2.0.3",
|
2025-01-07 18:13:52 -05:00
|
|
|
"@swc/core": "^1.10.6",
|
2021-08-23 07:49:49 -04:00
|
|
|
"chart.js": "3.5.1",
|
2023-06-29 11:08:33 -04:00
|
|
|
"chartjs-plugin-datalabels": "2.2.0",
|
2024-06-13 01:34:34 -04:00
|
|
|
"chrome-launcher": "^1.1.2",
|
2024-07-04 21:07:14 -04:00
|
|
|
"chrome-remote-interface": "^0.33.2",
|
2025-01-02 06:29:47 -05:00
|
|
|
"concurrently": "^9.1.2",
|
2024-09-03 05:51:07 -04:00
|
|
|
"ember-template-lint": "^6.0.0",
|
2024-12-22 17:04:14 -05:00
|
|
|
"esbuild": "^0.24.2",
|
2024-11-12 07:33:17 -05:00
|
|
|
"eslint": "^9.14.0",
|
2024-10-21 08:05:01 -04:00
|
|
|
"jsdoc": "^4.0.4",
|
2025-01-02 07:18:39 -05:00
|
|
|
"lefthook": "^1.10.1",
|
2024-12-01 18:34:19 -05:00
|
|
|
"licensee": "^11.1.1",
|
2025-01-08 17:58:30 -05:00
|
|
|
"lint-to-the-future": "^2.6.2",
|
2024-12-08 16:49:32 -05:00
|
|
|
"lint-to-the-future-ember-template": "^3.0.0",
|
2024-11-03 17:18:23 -05:00
|
|
|
"lint-to-the-future-eslint": "^2.2.0",
|
2023-06-30 07:01:45 -04:00
|
|
|
"magnific-popup": "1.1.0",
|
2024-03-10 22:04:51 -04:00
|
|
|
"moment": "2.30.1",
|
2024-03-10 20:46:09 -04:00
|
|
|
"moment-timezone": "0.5.45",
|
2023-08-24 08:25:44 -04:00
|
|
|
"pikaday": "1.8.2",
|
2023-10-23 06:08:35 -04:00
|
|
|
"prettier": "^2.8.8",
|
2024-12-19 17:47:47 -05:00
|
|
|
"puppeteer-core": "^23.11.1",
|
2024-09-03 08:52:37 -04:00
|
|
|
"squoosh": "https://codeload.github.com/discourse/squoosh/tar.gz/dc9649d",
|
2024-12-05 17:18:45 -05:00
|
|
|
"terser": "^5.37.0",
|
2025-01-09 12:31:10 -05:00
|
|
|
"typescript": "^5.7.3"
|
2018-11-05 15:10:27 -05:00
|
|
|
},
|
|
|
|
|
"scripts": {
|
2024-03-05 19:25:46 -05:00
|
|
|
"dev": "concurrently \"bin/ember-cli server --environment=development\" \"RAILS_ENV=development bin/rails server\"",
|
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": "concurrently \"npm:lint:*(!fix)\" --names \"lint:\"",
|
|
|
|
|
"lint:fix": "concurrently \"npm:lint:*:fix\" --names \"fix:\"",
|
2024-11-19 13:56:14 -05:00
|
|
|
"lint:js": "eslint ./app/assets/javascripts $(script/list_bundled_plugins) --cache --no-error-on-unmatched-pattern",
|
|
|
|
|
"lint:js:fix": "eslint --fix ./app/assets/javascripts $(script/list_bundled_plugins) --no-error-on-unmatched-pattern",
|
2024-12-02 13:13:40 -05:00
|
|
|
"lint:hbs": "ember-template-lint 'app/assets/javascripts/**/*.{gjs,hbs}' 'plugins/*/assets/javascripts/**/*.{gjs,hbs}' 'plugins/*/admin/assets/javascripts/**/*.{gjs,hbs}'",
|
|
|
|
|
"lint:hbs:fix": "ember-template-lint 'app/assets/javascripts/**/*.{gjs,hbs}' 'plugins/*/assets/javascripts/**/*.{gjs,hbs}' 'plugins/*/admin/assets/javascripts/**/*.{gjs,hbs}' --fix",
|
DEV: Introduce 'dev tools' toolbar and plugin-outlet debugger (#30624)
This commit introduces a new 'dev tools' feature for core, theme and plugin developers. This is enabled by default in development environments, and can be enabled in production by running `enableDevTools()` in the browser console.
When enabled, it will load a separate dev-tools JS/CSS bundle, and show a new toolbar on the left of the page. Dev Tools will remain enabled until the 'x' button is clicked, or `disableDevTools()` is run in the console.
The toolbar currently has three buttons:
- "Toggle safe mode" provides an easy way to toggle all themes/plugins on/off
- "Toggle verbose localization" is a toggle for our existing locale debugging feature
- "Debug plugin outlets" is inspired by the popular 'plugin outlet locations' theme component. It hooks into core's plugin outlet system, and renders a button into every single outlet. Those buttons have a tooltip which shows more information about the outlet, including all of the outletArg values. To inspect the value further, buttons allow the values to be saved to globals and logged to the console.
All of this is implemented under `/static`, and is only async-import()-d when the dev tools are enabled. Therefore, we can continue to add more tools, with zero performance cost to ordinary users of Discourse.
2025-01-08 10:26:18 -05:00
|
|
|
"lint:prettier": "pnpm pprettier --list-different 'app/assets/stylesheets/**/*.scss' 'app/assets/javascripts/**/*.{js,gjs,hbs,css}' $(script/list_bundled_plugins '/assets/stylesheets/**/*.scss') $(script/list_bundled_plugins '/{assets,admin/assets,test}/javascripts/**/*.{js,gjs,hbs}')",
|
|
|
|
|
"lint:prettier:fix": "pnpm prettier -w 'app/assets/stylesheets/**/*.scss' 'app/assets/javascripts/**/*.{js,gjs,hbs,css}' $(script/list_bundled_plugins '/assets/stylesheets/**/*.scss') $(script/list_bundled_plugins '/{assets,admin/assets,test}/javascripts/**/*.{js,gjs,hbs}')",
|
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
|
|
|
"lttf:ignore": "lint-to-the-future ignore",
|
|
|
|
|
"lttf:output": "lint-to-the-future output -o ./lint-progress/",
|
2024-09-03 05:51:07 -04:00
|
|
|
"lint-progress": "pnpm lttf:output && npx html-pages ./lint-progress --no-cache",
|
|
|
|
|
"ember": "pnpm --dir=app/assets/javascripts/discourse ember"
|
2021-08-04 16:04:58 -04:00
|
|
|
},
|
|
|
|
|
"engines": {
|
2024-02-27 04:48:30 -05:00
|
|
|
"node": ">= 18",
|
2024-09-03 05:51:07 -04:00
|
|
|
"npm": "please-use-pnpm",
|
|
|
|
|
"yarn": "please-use-pnpm",
|
|
|
|
|
"pnpm": ">= 9"
|
|
|
|
|
},
|
|
|
|
|
"pnpm": {
|
|
|
|
|
"patchedDependencies": {
|
|
|
|
|
"ember-this-fallback@0.4.0": "patches/ember-this-fallback@0.4.0.patch",
|
|
|
|
|
"babel-plugin-debug-macros@0.3.4": "patches/babel-plugin-debug-macros@0.3.4.patch",
|
|
|
|
|
"virtual-dom@2.1.1": "patches/virtual-dom@2.1.1.patch",
|
2024-12-01 18:34:19 -05:00
|
|
|
"licensee@11.1.1": "patches/licensee@11.1.1.patch",
|
2024-12-18 06:59:27 -05:00
|
|
|
"content-tag@3.1.0": "patches/content-tag@3.1.0.patch",
|
2024-12-11 09:09:25 -05:00
|
|
|
"@ember-compat/tracked-built-ins@0.9.1": "patches/@ember-compat__tracked-built-ins@0.9.1.patch",
|
|
|
|
|
"ember-source@5.12.0": "patches/ember-source@5.12.0.patch"
|
2024-09-03 05:51:07 -04:00
|
|
|
},
|
|
|
|
|
"peerDependencyRules": {
|
|
|
|
|
"allowedVersions": {
|
|
|
|
|
"lint-to-the-future-eslint>eslint": "*",
|
|
|
|
|
"@mixer/parallel-prettier>prettier": "*",
|
|
|
|
|
"lint-to-the-future-ember-template>ember-template-lint": "*",
|
|
|
|
|
"ember-this-fallback>ember-source": "*"
|
|
|
|
|
},
|
|
|
|
|
"ignoreMissing": [
|
|
|
|
|
"webpack"
|
|
|
|
|
]
|
|
|
|
|
}
|
2017-12-14 21:15:04 -05:00
|
|
|
}
|
2024-06-17 12:21:04 -04:00
|
|
|
}
|
