@figma-export/output-components-as-es6
Advanced tools
Outputter for @figma-export that exports components in javascript file
Outputter for @figma-export that exports components in javascript file.
With this outputter you can export all components as variables inside a .js file called with the page name.
This is a sample of the output:
$ tree output/
# output/
# ├── icons.js
# └── monochrome.js
For each file you will have a list of export.
// icons.js
export const figmaExport = `<svg width="60" height="60" viewBox="0 0 60 60" fill="none" xmlns="http://www.w3.org/2000/svg"> ... </svg>`;
export const figmaLogo = `<svg width="40" height="60" viewBox="0 0 40 60" fill="none" xmlns="http://www.w3.org/2000/svg"> ... </svg>`;
Using npm:
npm install --save-dev @figma-export/output-components-as-es6
or using yarn:
yarn add @figma-export/output-components-as-es6 --dev
FAQs
Outputter for @figma-export that exports components in javascript file
The npm package @figma-export/output-components-as-es6 receives a total of 286 weekly downloads. As such, @figma-export/output-components-as-es6 popularity was classified as not popular.
We found that @figma-export/output-components-as-es6 demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer 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
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.