babel-plugin-transform-es2015-object-super
Compile ES2015 object super to ES5
This package has a good security score with no known vulnerabilities.
Community Reviews
Legacy Babel plugin - deprecated and superseded by @babel/preset-env
The transformation itself is straightforward and has zero runtime overhead - it's purely compile-time. No configuration options, no memory leaks, no runtime dependencies. It just works when it runs. However, this is a deprecated package that's been completely replaced by @babel/preset-env and the modular Babel 7+ plugin system.
From an operations perspective, there's nothing to monitor or tune here - it's a build-time transform with no runtime footprint. The real issue is that using legacy Babel 6 plugins creates dependency management headaches and prevents you from getting security updates and modern tooling improvements. If you're still on Babel 6, migration should be your priority.
Best for: Maintaining legacy Babel 6 projects that cannot yet migrate to Babel 7+.
Avoid if: You're starting a new project or can migrate to Babel 7+ and @babel/preset-env.
Legacy Babel plugin - superseded but functional for specific ES2015 needs
The biggest operational concern is that this package has been unmaintained since 2017 and is explicitly superseded by @babel/plugin-transform-object-super and preset-env. You won't find it causing runtime issues because it only touches your build pipeline, but you're stuck on Babel 6 architecture if you use it. No logging, no configuration options to speak of - it just does one thing during compilation.
For teams still on Babel 6 maintaining legacy codebases, it works fine and won't cause production incidents. However, the lack of updates means no bug fixes, and you're blocking yourself from modern Babel 7+ tooling. Migration path exists but requires broader Babel ecosystem upgrades.
Best for: Legacy Babel 6 projects that cannot migrate and specifically need object super transformation.
Avoid if: You're starting a new project or can migrate to Babel 7+ and @babel/preset-env.
Deprecated standalone plugin - use @babel/preset-env instead
The plugin has zero runtime footprint - it's purely a compile-time transformation with no runtime dependencies or performance impact. Configuration is minimal (just add it to your Babel plugins array), and it doesn't expose any options or hooks because there's nothing to configure. Error handling is transparent; if the transform fails, you get standard Babel error output.
The real issue is maintenance and ecosystem fit. This is a deprecated package that's been superseded by @babel/preset-env, which includes this transformation automatically when needed based on your target browsers. Using standalone ES2015 transform plugins creates unnecessary complexity in your build configuration and prevents you from benefiting from Babel's modern target-based compilation approach.
Best for: Maintaining legacy Babel 6 projects that haven't migrated to Babel 7+
Avoid if: You're starting a new project or can migrate to @babel/preset-env for automatic polyfill management
Sign in to write a review
Sign In