github-mirror/discourse
2
0
Fork 0
mirror of https://github.com/discourse/discourse.git synced 2024-11-29 06:53:39 +08:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity
0cd8659b06
discourse/app/assets/javascripts/package.json

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

34 lines
916 B
JSON
Raw Normal View History

DEV: Migrate to Ember CLI (#11932) This encompasses a lot of work done over the last year, much of which has already been merged into master. This is the final set of changes required to get Ember CLI running locally for development. From here on it will be bug fixes / enhancements. Co-authored-by: Jarek Radosz <jradosz@gmail.com> Co-authored-by: romanrizzi <rizziromanalejandro@gmail.com> Co-authored-by: Jarek Radosz <jradosz@gmail.com> Co-authored-by: romanrizzi <rizziromanalejandro@gmail.com>
2021-02-04 03:22:20 +08:00
{
"private": true,
DEV: Use patch-package to apply ember-jquery workaround Co-authored-by: David Taylor <david@taylorhq.com>
2023-04-11 17:12:30 +08:00
"scripts": {
"postinstall": "patch-package"
},
DEV: Migrate to Ember CLI (#11932) This encompasses a lot of work done over the last year, much of which has already been merged into master. This is the final set of changes required to get Ember CLI running locally for development. From here on it will be bug fixes / enhancements. Co-authored-by: Jarek Radosz <jradosz@gmail.com> Co-authored-by: romanrizzi <rizziromanalejandro@gmail.com> Co-authored-by: Jarek Radosz <jradosz@gmail.com> Co-authored-by: romanrizzi <rizziromanalejandro@gmail.com>
2021-02-04 03:22:20 +08:00
"workspaces": [
"admin",
DEV: Make bootstrap-json a monorepo package (#19048)
2022-11-16 18:58:10 +08:00
"bootstrap-json",
DEV: Make dialog-holder a monorepo package (#19051)
2022-11-16 23:43:45 +08:00
"dialog-holder",
DEV: Make bootstrap-json a monorepo package (#19048)
2022-11-16 18:58:10 +08:00
"discourse",
DEV: Migrate to Ember CLI (#11932) This encompasses a lot of work done over the last year, much of which has already been merged into master. This is the final set of changes required to get Ember CLI running locally for development. From here on it will be bug fixes / enhancements. Co-authored-by: Jarek Radosz <jradosz@gmail.com> Co-authored-by: romanrizzi <rizziromanalejandro@gmail.com> Co-authored-by: Jarek Radosz <jradosz@gmail.com> Co-authored-by: romanrizzi <rizziromanalejandro@gmail.com>
2021-02-04 03:22:20 +08:00
"discourse-common",
"discourse-hbr",
DEV: Make bootstrap-json a monorepo package (#19048)
2022-11-16 18:58:10 +08:00
"discourse-plugins",
DEV: Migrate to Ember CLI (#11932) This encompasses a lot of work done over the last year, much of which has already been merged into master. This is the final set of changes required to get Ember CLI running locally for development. From here on it will be bug fixes / enhancements. Co-authored-by: Jarek Radosz <jradosz@gmail.com> Co-authored-by: romanrizzi <rizziromanalejandro@gmail.com> Co-authored-by: Jarek Radosz <jradosz@gmail.com> Co-authored-by: romanrizzi <rizziromanalejandro@gmail.com>
2021-02-04 03:22:20 +08:00
"discourse-widget-hbs",
DEV: Add progress output in CI during ember-cli build (#17977) By default, in CI environments, Ember CLI does not output anything between "building..." and "cleaning up". Depending on configuration and hardware, Discourse asset builds can take upwards of 60s, and so this lack of output can make the build feel 'stuck'. This commit introduces an addon which checks for CI mode, and then outputs status information periodically. The logic is very similar to Ember CLI's non-CI progress output implementation (https://github.com/ember-cli/ember-cli/blob/04a38fda2c/lib/models/builder.js#L183-L185).
2022-08-18 05:39:52 +08:00
"ember-cli-progress-ci",
DEV: Include ember deprecation messages in production builds (#20587) By default, Ember uses a babel transformation to strip out calls to `deprecate()` in production builds. Given that Discourse is a development platform for third-party themes/plugins, having deprecation messages visible in production is essential - many themes/plugins do not have comprehensive test-suites, and rely on production feedback to prompt changes. This commit patches Ember to print its deprecation messages to the console in production. In future we intend to improve the visibility of these to hosting providers and/or site admins. There are two main parts to this commit: 1. Use yarn's 'resolutions' feature to point `babel-plugin-debug-macros` to a discourse-owned fork. This fork prevents `deprecate()` calls from being stripped. Relevant change can be found at https://github.com/discourse/babel-plugin-debug-macros/commit/d179d613bf 2. Introduce a production shim for Ember's deprecation library, including the `registerDeprecationHandler` API. The default implementation is stripped out of production builds via an `if(DEBUG)` wrapper. Long term we hope that this kind of functionality can be made available in Ember itself via a flag.
2023-03-10 18:37:28 +08:00
"ember-production-deprecations",
DEV: Migrate to Ember CLI (#11932) This encompasses a lot of work done over the last year, much of which has already been merged into master. This is the final set of changes required to get Ember CLI running locally for development. From here on it will be bug fixes / enhancements. Co-authored-by: Jarek Radosz <jradosz@gmail.com> Co-authored-by: romanrizzi <rizziromanalejandro@gmail.com> Co-authored-by: Jarek Radosz <jradosz@gmail.com> Co-authored-by: romanrizzi <rizziromanalejandro@gmail.com>
2021-02-04 03:22:20 +08:00
"pretty-text",
FIX: Make truth-helpers work in Ember CLI (#13044) The addon wasn't included at all 😃
2021-05-12 23:52:36 +08:00
"select-kit",
DEV: Make wizard an ember addon (#17027) Co-authored-by: David Taylor <david@taylorhq.com>
2022-06-17 20:50:21 +08:00
"truth-helpers",
"wizard"
DEV: Include ember deprecation messages in production builds (#20587) By default, Ember uses a babel transformation to strip out calls to `deprecate()` in production builds. Given that Discourse is a development platform for third-party themes/plugins, having deprecation messages visible in production is essential - many themes/plugins do not have comprehensive test-suites, and rely on production feedback to prompt changes. This commit patches Ember to print its deprecation messages to the console in production. In future we intend to improve the visibility of these to hosting providers and/or site admins. There are two main parts to this commit: 1. Use yarn's 'resolutions' feature to point `babel-plugin-debug-macros` to a discourse-owned fork. This fork prevents `deprecate()` calls from being stripped. Relevant change can be found at https://github.com/discourse/babel-plugin-debug-macros/commit/d179d613bf 2. Introduce a production shim for Ember's deprecation library, including the `registerDeprecationHandler` API. The default implementation is stripped out of production builds via an `if(DEBUG)` wrapper. Long term we hope that this kind of functionality can be made available in Ember itself via a flag.
2023-03-10 18:37:28 +08:00
],
DEV: Update browserslist (#20846) Silences some verbose logging while booting the UI
2023-03-28 01:15:04 +08:00
"resolutions": {
DEV: Include ember deprecation messages in production builds (#20587) By default, Ember uses a babel transformation to strip out calls to `deprecate()` in production builds. Given that Discourse is a development platform for third-party themes/plugins, having deprecation messages visible in production is essential - many themes/plugins do not have comprehensive test-suites, and rely on production feedback to prompt changes. This commit patches Ember to print its deprecation messages to the console in production. In future we intend to improve the visibility of these to hosting providers and/or site admins. There are two main parts to this commit: 1. Use yarn's 'resolutions' feature to point `babel-plugin-debug-macros` to a discourse-owned fork. This fork prevents `deprecate()` calls from being stripped. Relevant change can be found at https://github.com/discourse/babel-plugin-debug-macros/commit/d179d613bf 2. Introduce a production shim for Ember's deprecation library, including the `registerDeprecationHandler` API. The default implementation is stripped out of production builds via an `if(DEBUG)` wrapper. Long term we hope that this kind of functionality can be made available in Ember itself via a flag.
2023-03-10 18:37:28 +08:00
"**/babel-plugin-debug-macros": "npm:@discourse/babel-plugin-debug-macros@0.4.0-pre1"
DEV: Update browserslist (#20846) Silences some verbose logging while booting the UI
2023-03-28 01:15:04 +08:00
},
DEV: Enable patch-package in production and in `javascripts/discourse` (#21078) When running `yarn install` in a yarn workspace, the lifecycle hooks in the root package.json are not triggered. https://github.com/yarnpkg/yarn/issues/5790 As a workaround, we can additionally run `patch-package` from the `javascripts/discourse/package.json` `postinstall` hook. `patch-package` is idempotent, so it doesn't matter if it is triggered multiple times. Longer term we intend to move to pnpm, which has built-in patch support.
2023-04-12 20:15:53 +08:00
"dependencies": {
DEV: Use patch-package to apply ember-jquery workaround Co-authored-by: David Taylor <david@taylorhq.com>
2023-04-11 17:12:30 +08:00
"patch-package": "^6.5.1",
"postinstall-postinstall": "^2.1.0"
DEV: Replace virtual-dom fork with patch-package (#21007) Using patch-package is much easier to reason with than maintaining a full fork of virtual-dom. Original reasoning for the fork can be found in e216a98f Patch is based on the diff at https://github.com/discourse/virtual-dom/commit/c64007150abc0b7872e44f5cf5be23fefec03b73#diff-f648eb0588a88af826e29622f64aca611e191c66eb9e79396d559edaef622313
2023-04-19 02:42:25 +08:00
},
"devDependencies": {},
"notes": {
"deps vs devDeps": "this project doesn't use dev dependencies when building the app, so all dependencies affecting the build of the UI (ember-cli, webpack, etc), need to be in 'dependencies', not 'devDependencies' (yarn install --production is used)"
DEV: Enable patch-package in production and in `javascripts/discourse` (#21078) When running `yarn install` in a yarn workspace, the lifecycle hooks in the root package.json are not triggered. https://github.com/yarnpkg/yarn/issues/5790 As a workaround, we can additionally run `patch-package` from the `javascripts/discourse/package.json` `postinstall` hook. `patch-package` is idempotent, so it doesn't matter if it is triggered multiple times. Longer term we intend to move to pnpm, which has built-in patch support.
2023-04-12 20:15:53 +08:00
}
DEV: Migrate to Ember CLI (#11932) This encompasses a lot of work done over the last year, much of which has already been merged into master. This is the final set of changes required to get Ember CLI running locally for development. From here on it will be bug fixes / enhancements. Co-authored-by: Jarek Radosz <jradosz@gmail.com> Co-authored-by: romanrizzi <rizziromanalejandro@gmail.com> Co-authored-by: Jarek Radosz <jradosz@gmail.com> Co-authored-by: romanrizzi <rizziromanalejandro@gmail.com>
2021-02-04 03:22:20 +08:00
}
Reference in New Issue Copy Permalink