
Security News
Meet Socket at Black Hat Europe and BSides London 2025
Socket is heading to London! Stop by our booth or schedule a meeting to see what we've been working on.
@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
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>`;
Tip: A component named
icon/eyewill be exported as variable namediconEye.
You can easily add this outputter to your .figmaexportrc.js:
import asES6 from '@figma-export/output-components-as-es6'
export default {
commands: [
['components', {
fileId: 'fzYhvQpqwhZDUImRz431Qo',
onlyFromPages: ['icons', 'unit-test'],
outputters: [
asES6({
output: './output'
})
]
}],
]
}
output is mandatory.
getVariableName, useBase64 and useDataUrl are optional.
import asES6 from '@figma-export/output-components-as-es6'
import { camelCase } from '@figma-export/utils'
...
asES6({
output: './output',
getVariableName: (options) => camelCase(options.componentName.trim()),
useBase64: false,
useDataUrl: false,
})
defaults may change, please refer to
./src/index.ts
Using npm:
npm install --save-dev @figma-export/output-components-as-es6
or using yarn:
yarn add @figma-export/output-components-as-es6 --dev
This task can be configured providing some options:
output is the path to the output folder.variablePrefix and variableSuffix enable you to prepend or append a text to the variable name. This is necessary when your component name is a reserved word (e.g. const, package, ...).useBase64 (boolean) will export each components using Base 64 encoding.// icons.js
export const figmaExport = `PHN2ZyB3aWR0aD0iNjAiIGhlaWdodD0iNjAiIHZpZXdCb3g9IjAgMCA2MCA2MCIgZmlsbD0ibm9uZSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIj4gLi4uIDwvc3ZnPg==`;
useDataUrl (boolean) will export each components using Data URL format.// icons.js
export const figmaExport = `data:image/svg+xml,%3csvg width='60' height='60' viewBox='0 0 60 60' fill='none' xmlns='http://www.w3.org/2000/svg'%3e ... %3c/svg%3e`;
FAQs
Outputter for @figma-export that exports components in javascript file
The npm package @figma-export/output-components-as-es6 receives a total of 634 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
Socket is heading to London! Stop by our booth or schedule a meeting to see what we've been working on.

Security News
OWASP’s 2025 Top 10 introduces Software Supply Chain Failures as a new category, reflecting rising concern over dependency and build system risks.

Research
/Security News
Socket researchers discovered nine malicious NuGet packages that use time-delayed payloads to crash applications and corrupt industrial control systems.