New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More →
Socket
Sign inDemoInstall
Socket
Sign inDemoInstall

esperanto

Package Overview
Dependencies
Maintainers
1
Versions
75
Alerts
File Explorer

Advanced tools

License
Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

esperanto - npm Package Versions

1
…
…
8

0.5.10

Diff
rich_harris
 published 0.5.10 •

Changelog

Source

0.5.10

  • One-to-one conversions get the same compact UMD form as bundles
  • Default imports are not hedged unnecessarily (#40)

0.5.9

Diff
rich_harris
 published 0.5.9 •

Changelog

Source

0.5.9

  • More concise UMD output (#36)

0.5.8

Diff
rich_harris
 published 0.5.8 •

Changelog

Source

0.5.8

  • Functions are always exported early (#37)
  • Modules can be transformed before bundling with esperanto.bundle({ transform: someFunction }), where someFunction returns either a string, or a promise that resolves to a string

0.5.7

Diff
rich_harris
 published 0.5.7 •

Changelog

Source

0.5.7

  • Classes are exported after declaration, not before (#33)

0.5.6

Diff
rich_harris
 published 0.5.6 •

Changelog

Source

0.5.6

  • Support for named AMD modules, via amdName option (works for both standalone and bundle conversions)

0.5.5

Diff
rich_harris
 published 0.5.5 •

Changelog

Source

0.5.5

  • No actual changes - just shuffling things about so we can separate demo page into separate repo

0.5.3

Diff
rich_harris
 published 0.5.3 •

Changelog

Source

0.5.3

  • You can specify a banner and/or footer option when converting or bundling
  • An error will be thrown if a module attempts to import itself

0.5.2

Diff
rich_harris
 published 0.5.2 •

Changelog

Source

0.5.2

  • Imported objects (other than namespace imports) can be assigned properties (#29)
  • Default imports can be exported as named exports from the entry module in a bundle

0.5.1

Diff
rich_harris
 published 0.5.1 •

Changelog

Source

0.5.1

  • Identifiers that match object prototype properties are not mistakenly exported (and garbled)

0.5.0

Diff
rich_harris
 published 0.5.0 •

Changelog

Source

0.5.0

  • Chained imports/exports are renamed correctly within a bundle (#17)
  • Bundle exports are written at assignment time, rather than at the end of the bundle with an Object.defineProperty hack
  • Attempting to import a non-exported identifier within the same bundle throws an error
  • External modules are imported correctly (#28)
  • Identifiers are only rewritten as necessary (#25)
  • Redundant assignments in a bundle (mod__default = mod__foo) are avoided (#14)
  • Shadowed imports are handled (#18)
  • Modules are indented consistently within a bundle
1
…
…
8
SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

About

Packages

npm

Go

Maven

PyPI

Rubygems

Stay in touch

Get open source security insights delivered straight into your inbox.

  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc