getify/moduloze

Issues

• Bug: some `default` ESM imports need to be un-special-cased

  #21 opened a year ago by getify
  0

• Bug: if code is empty, throws an error for some reason

  #20 opened 2 years ago by getify
  0

• optimization (bug): multiple named exports are in separate ESM `export` statements

  #19 opened 2 years ago by getify
  0

• Missing dependency map in ESM build

  #17 opened 3 years ago by nfantone
  7

• bug: chained module.exports assignment fails

  #16 opened 3 years ago by getify
  1

• Improper handling of "module.exports" in ESM conversion

  #18 opened 3 years ago by getify
  0

• User feedback suggestions

  #7 opened 4 years ago by horacioh
  16

• add CLI option for prepending contents to each file

  #15 opened 4 years ago by getify
  0

• add CLI option for minification

  #14 opened 4 years ago by getify
  0

• bug: ESM named export identifier conflict

  #13 opened 4 years ago by getify
  4

• Bug: dependency path handling is broken at the library level

  #12 opened 4 years ago by getify
  0

• Add option for ES bundling, as alternative/mode for ES index output

  #11 opened 4 years ago by getify
  2

• check for namespace import used as function call

  #10 opened 4 years ago by getify
  0

• Explore: should moduloze also support converting "globals-only" (instead of just CJS)

  #8 opened 4 years ago by getify
  11

• How is dependency-map used in the ESM and UMD builds?

  #9 opened 4 years ago by getify
  3

• moduloze should operate without any .mzrc present

  #5 opened 4 years ago by getify
  0

• consider option to force creation of target output directory

  #6 opened 4 years ago by getify
  0

• Breaks when other files than JS files are found

  #4 opened 4 years ago by mgrsskls
  4

• TODOs

  #1 opened 4 years ago by getify
  0

• Incorrect import conversion

  #3 opened 4 years ago by getify
  0

• Unknown dependencies path is modified

  #2 opened 4 years ago by getify
  0