V3 proposal

[Mister-Hope]

Here are some ideas for artalk client v3. Not sure about your attitude for raising major or introduce potential breaking changes in v2. These changes include:

• use rollup to bundle a single declaration file for artalk

• Add "type": "module" and "exports" field for all packages, as all LTS node.js support ESM. It will make artalk works in strict esm env while it won't break commonjs "require".

• Bump to marked V11 and remove deprecated options https://marked.js.org/using_advanced#options

• Remove markedReplacers in context and options, add new option markedExtenstions, since marked support .use() api (https://marked.js.org/using_pro#use)

• Some code refactors

  • Update export field

  remove the following compact code in v3

   "./dist/*": "./dist/*",
   "./dist/Artalk": "./dist/Artalk.js",
   "./dist/Artalk.es": "./dist/Artalk.es.js",
   "./dist/Artalk.iife": "./dist/Artalk.iife.js",
   "./dist/ArtalkLite": "./dist/ArtalkLite.js",
   "./dist/ArtalkLite.es": "./dist/ArtalkLite.es.js",
   "./dist/ArtalkLite.iife": "./dist/ArtalkLite.iife.js",
   "./dist/i18n/jp": "./dist/i18n/jp.js",
   "./dist/i18n/zh-TW": "./dist/i18n/zh-TW.js",

  • Use lowercase filename in dist file

    Weblinks could be case sensitive and could be not, lowercase is better.

  • remove cjs files

    Since all node.js support esm, there is no need to provide cjs output