discourse/app/assets/javascripts/pretty-text/index.js

"use strict";

module.exports = {
  name: require("./package").name,

  isDevelopingAddon() {
    return true;
  },
};
DEV: Move pretty-text into an ember-addon format (#9689) 2020-05-07 11:37:47 -05:00			`"use strict";`

			`module.exports = {`
DEV: apply new coding standards (#10592) 2020-09-04 06:42:47 -05:00			`name: require("./package").name,`
DEV: invert pretty-text build logic (#22524) Generally follows the same pattern as #22520 There are some changes here, notably it uses the addon's babel settings rather than the app's, and it goes through the same treatment as the rest of the addon code (which may include more than just babel). However, this probably brings us closer to the normal expectations you have around developing addon code, and in any case, does not seem to have any effect on the final output: ``` $ diff dist/assets/markdown-it-bundle.js /tmp/dist-before/assets/markdown-it-bundle.js ``` 2023-07-10 17:11:49 -05:00
REFACTOR: Support bundling our `admin` section as an ember addon 2020-09-22 13:18:47 -05:00			`isDevelopingAddon() {`
			`return true;`
			`},`
DEV: Move pretty-text into an ember-addon format (#9689) 2020-05-07 11:37:47 -05:00			`};`