discourse/app/assets/javascripts/discourse-markdown-it/package.json

{
  "name": "discourse-markdown-it",
  "version": "1.0.0",
  "private": true,
  "description": "Discourse's markdown-it features",
  "author": "Discourse <team@discourse.org>",
  "license": "GPL-2.0-only",
  "keywords": [
    "ember-addon"
  ],
  "exports": {
    ".": "./src/index.js",
    "./*": "./src/*.js",
    "./addon-main.js": "./addon-main.cjs"
  },
  "files": [
    "addon-main.cjs",
    "src"
  ],
  "dependencies": {
    "@embroider/addon-shim": "^1.8.7",
    "discourse-common": "1.0.0",
    "ember-auto-import": "^2.7.2",
    "markdown-it": "^14.0.0"
  },
  "peerDependencies": {
    "discourse-i18n": "1.0.0",
    "pretty-text": "1.0.0",
    "xss": "*"
  },
  "engines": {
    "node": "16.* || >= 18",
    "npm": "please-use-yarn",
    "yarn": ">= 1.21.1"
  },
  "ember": {
    "edition": "octane"
  },
  "ember-addon": {
    "version": 2,
    "type": "addon",
    "main": "addon-main.cjs",
    "app-js": {}
  }
}
DEV: remove markdown-it-bundle and custom build code (#23859) With Embroider, we can rely on async `import()` to do the splitting for us. This commit extracts from `pretty-text` all the parts that are meant to be loaded async into a new `discourse-markdown-it` package that is also a V2 addon (meaning that all files are presumed unused until they are imported, aka "static"). Mostly I tried to keep the very discourse specific stuff (accessing site settings and loading plugin features) inside discourse proper, while the new package aims to have some resembalance of a general purpose library, a MarkdownIt++ if you will. It is far from perfect because of how all the "options" stuff work but I think it's a good start for more refactorings (clearing up the interfaces) to happen later. With this, pretty-text and app/lib/text are mostly a kitchen sink of loosely related text processing utilities. After the refactor, a lot more code related to setting up the engine are now loaded lazily, which should be a pretty nice win. I also noticed that we are currently pulling in the `xss` library at initial load to power the "sanitize" stuff, but I suspect with a similar refactoring effort those usages can be removed too. (See also #23790). This PR does not attempt to fix the sanitize issue, but I think it sets things up on the right trajectory for that to happen later. Co-authored-by: David Taylor <david@taylorhq.com> 2023-11-06 08:59:49 -08:00			`{`
			`"name": "discourse-markdown-it",`
			`"version": "1.0.0",`
			`"private": true,`
			`"description": "Discourse's markdown-it features",`
			`"author": "Discourse <team@discourse.org>",`
			`"license": "GPL-2.0-only",`
			`"keywords": [`
			`"ember-addon"`
			`],`
			`"exports": {`
			`".": "./src/index.js",`
			`"./": "./src/.js",`
			`"./addon-main.js": "./addon-main.cjs"`
			`},`
			`"files": [`
			`"addon-main.cjs",`
			`"src"`
			`],`
			`"dependencies": {`
Build(deps): Bump the embroider group (#24391) Bumps the embroider group in /app/assets/javascripts with 5 updates: \| Package \| From \| To \| \| --- \| --- \| --- \| \| [@embroider/test-setup](https://github.com/embroider-build/embroider/tree/HEAD/packages/test-setup) \| `3.0.2` \| `3.0.3` \| \| [@embroider/compat](https://github.com/embroider-build/embroider/tree/HEAD/packages/compat) \| `3.2.3` \| `3.3.1` \| \| [@embroider/core](https://github.com/embroider-build/embroider/tree/HEAD/packages/core) \| `3.3.0` \| `3.4.1` \| \| [@embroider/webpack](https://github.com/embroider-build/embroider/tree/HEAD/packages/webpack) \| `3.2.0` \| `3.2.1` \| \| [@embroider/addon-shim](https://github.com/embroider-build/embroider/tree/HEAD/packages/addon-shim) \| `1.8.6` \| `1.8.7` \| Updates `@embroider/test-setup` from 3.0.2 to 3.0.3 - [Release notes](https://github.com/embroider-build/embroider/releases) - [Changelog](https://github.com/embroider-build/embroider/blob/main/CHANGELOG.md) - [Commits](https://github.com/embroider-build/embroider/commits/HEAD/packages/test-setup) Updates `@embroider/compat` from 3.2.3 to 3.3.1 - [Release notes](https://github.com/embroider-build/embroider/releases) - [Changelog](https://github.com/embroider-build/embroider/blob/main/CHANGELOG.md) - [Commits](https://github.com/embroider-build/embroider/commits/HEAD/packages/compat) Updates `@embroider/core` from 3.3.0 to 3.4.1 - [Release notes](https://github.com/embroider-build/embroider/releases) - [Changelog](https://github.com/embroider-build/embroider/blob/main/CHANGELOG.md) - [Commits](https://github.com/embroider-build/embroider/commits/HEAD/packages/core) Updates `@embroider/webpack` from 3.2.0 to 3.2.1 - [Release notes](https://github.com/embroider-build/embroider/releases) - [Changelog](https://github.com/embroider-build/embroider/blob/main/CHANGELOG.md) - [Commits](https://github.com/embroider-build/embroider/commits/HEAD/packages/webpack) Updates `@embroider/addon-shim` from 1.8.6 to 1.8.7 - [Release notes](https://github.com/embroider-build/embroider/releases) - [Changelog](https://github.com/embroider-build/embroider/blob/main/CHANGELOG.md) - [Commits](https://github.com/embroider-build/embroider/commits/HEAD/packages/addon-shim) --- updated-dependencies: - dependency-name: "@embroider/test-setup" dependency-type: direct:development update-type: version-update:semver-patch dependency-group: embroider - dependency-name: "@embroider/compat" dependency-type: direct:development update-type: version-update:semver-minor dependency-group: embroider - dependency-name: "@embroider/core" dependency-type: direct:development update-type: version-update:semver-minor dependency-group: embroider - dependency-name: "@embroider/webpack" dependency-type: direct:development update-type: version-update:semver-patch dependency-group: embroider - dependency-name: "@embroider/addon-shim" dependency-type: direct:production update-type: version-update:semver-patch dependency-group: embroider ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> 2023-11-16 12:31:25 +01:00			`"@embroider/addon-shim": "^1.8.7",`
DEV: remove markdown-it-bundle and custom build code (#23859) With Embroider, we can rely on async `import()` to do the splitting for us. This commit extracts from `pretty-text` all the parts that are meant to be loaded async into a new `discourse-markdown-it` package that is also a V2 addon (meaning that all files are presumed unused until they are imported, aka "static"). Mostly I tried to keep the very discourse specific stuff (accessing site settings and loading plugin features) inside discourse proper, while the new package aims to have some resembalance of a general purpose library, a MarkdownIt++ if you will. It is far from perfect because of how all the "options" stuff work but I think it's a good start for more refactorings (clearing up the interfaces) to happen later. With this, pretty-text and app/lib/text are mostly a kitchen sink of loosely related text processing utilities. After the refactor, a lot more code related to setting up the engine are now loaded lazily, which should be a pretty nice win. I also noticed that we are currently pulling in the `xss` library at initial load to power the "sanitize" stuff, but I suspect with a similar refactoring effort those usages can be removed too. (See also #23790). This PR does not attempt to fix the sanitize issue, but I think it sets things up on the right trajectory for that to happen later. Co-authored-by: David Taylor <david@taylorhq.com> 2023-11-06 08:59:49 -08:00			`"discourse-common": "1.0.0",`
Build(deps): Bump ember-auto-import from 2.7.1 to 2.7.2 in /app/assets/javascripts (#25025) * Build(deps): Bump ember-auto-import in /app/assets/javascripts Bumps [ember-auto-import](https://github.com/ef4/ember-auto-import/tree/HEAD/packages/ember-auto-import) from 2.7.1 to 2.7.2. - [Release notes](https://github.com/ef4/ember-auto-import/releases) - [Changelog](https://github.com/embroider-build/ember-auto-import/blob/main/packages/ember-auto-import/CHANGELOG.md) - [Commits](https://github.com/ef4/ember-auto-import/commits/HEAD/packages/ember-auto-import) --- updated-dependencies: - dependency-name: ember-auto-import dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> * Update lockfiles for ember version flag --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: discoursebuild <build@discourse.org> 2023-12-27 08:25:43 +08:00			`"ember-auto-import": "^2.7.2",`
Build(deps): Bump markdown-it from 13.0.2 to 14.0.0 in /app/assets/javascripts (#24809) * Build(deps): Bump markdown-it in /app/assets/javascripts Bumps [markdown-it](https://github.com/markdown-it/markdown-it) from 13.0.2 to 14.0.0. - [Changelog](https://github.com/markdown-it/markdown-it/blob/master/CHANGELOG.md) - [Commits](https://github.com/markdown-it/markdown-it/compare/13.0.2...14.0.0) --- updated-dependencies: - dependency-name: markdown-it dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> * Update lockfiles for ember version flag --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: discoursebuild <build@discourse.org> 2023-12-10 22:38:03 +01:00			`"markdown-it": "^14.0.0"`
DEV: remove markdown-it-bundle and custom build code (#23859) With Embroider, we can rely on async `import()` to do the splitting for us. This commit extracts from `pretty-text` all the parts that are meant to be loaded async into a new `discourse-markdown-it` package that is also a V2 addon (meaning that all files are presumed unused until they are imported, aka "static"). Mostly I tried to keep the very discourse specific stuff (accessing site settings and loading plugin features) inside discourse proper, while the new package aims to have some resembalance of a general purpose library, a MarkdownIt++ if you will. It is far from perfect because of how all the "options" stuff work but I think it's a good start for more refactorings (clearing up the interfaces) to happen later. With this, pretty-text and app/lib/text are mostly a kitchen sink of loosely related text processing utilities. After the refactor, a lot more code related to setting up the engine are now loaded lazily, which should be a pretty nice win. I also noticed that we are currently pulling in the `xss` library at initial load to power the "sanitize" stuff, but I suspect with a similar refactoring effort those usages can be removed too. (See also #23790). This PR does not attempt to fix the sanitize issue, but I think it sets things up on the right trajectory for that to happen later. Co-authored-by: David Taylor <david@taylorhq.com> 2023-11-06 08:59:49 -08:00			`},`
			`"peerDependencies": {`
			`"discourse-i18n": "1.0.0",`
			`"pretty-text": "1.0.0",`
			`"xss": "*"`
			`},`
			`"engines": {`
			`"node": "16.* \|\| >= 18",`
			`"npm": "please-use-yarn",`
			`"yarn": ">= 1.21.1"`
			`},`
			`"ember": {`
			`"edition": "octane"`
			`},`
			`"ember-addon": {`
			`"version": 2,`
			`"type": "addon",`
			`"main": "addon-main.cjs",`
			`"app-js": {}`
			`}`
			`}`