@babel/plugin-transform-export-namespace-from
Advanced tools
Compile export namespace to ES2015
See our website @babel/plugin-transform-export-namespace-from for more information.
Using npm:
npm install --save-dev @babel/plugin-transform-export-namespace-from
or using yarn:
yarn add @babel/plugin-transform-export-namespace-from --dev
This package is a proposal plugin for Babel that adds support for the export * as syntax before it was officially included in the ECMAScript specification. It serves a similar purpose to @babel/plugin-transform-export-namespace-from but is intended for use during the proposal stage.
This Babel plugin adds support for the export-from extension syntax, which includes export * as syntax as well as other export extensions. It's a broader plugin that encompasses the functionality of @babel/plugin-transform-export-namespace-from along with additional export-related transformations.
FAQs
Compile export namespace to ES2015
The npm package @babel/plugin-transform-export-namespace-from receives a total of 33,052,194 weekly downloads. As such, @babel/plugin-transform-export-namespace-from popularity was classified as popular.
We found that @babel/plugin-transform-export-namespace-from demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 4 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
The White House’s Gold Eagle Initiative aims to coordinate AI-discovered vulnerabilities, validate findings, and accelerate patching across critical software.
Security News
A Shai-Hulud infection exposed Suno's source code, which shows the AI music startup stream-ripped tracks to train its models.
Security News
Vercel is formalizing a monthly release program for Next.js. The change follows React2Shell and a sharp rise in AI-assisted vulnerability discovery.