4 ms·

Just to share, there is an issue about uglifyjs https://github.com/mishoo/UglifyJS2/issues/936 https://github.com/mishoo/UglifyJS2/issues/936

• nailer 11y ago
  The uglify authors should use 'uglify' per the naming conventions and can easily reserve uglify-js and uglifyjs as empty / legacy packages.
  • u223344 11y ago
    According to the parent link they've been waiting for npm support to respond for a over a month.
    • nailer 11y ago
      They filed an official dispute 11 hours ago.
      • dps7t 11y ago
        Feb 4th. https://github.com/mishoo/UglifyJS2/issues/936#issuecomment-179937812 https://github.com/mishoo/UglifyJS2/issues/936#issuecomment-...
• u223344 11y ago
  Ironically the same person who first reported this npm vulnerability used the wrong package name uglifyjs instead of uglify-js in an unrelated github project. https://github.com/mishoo/UglifyJS2/issues/936#issuecomment-179910332 https://github.com/mishoo/UglifyJS2/issues/936#issuecomment-... https://github.com/samccone/The-cost-of-transpiling-es2015-in-2016/issues/27 https://github.com/samccone/The-cost-of-transpiling-es2015-i... Or perhaps was it a security experiment to see how long it took someone to notice.