Publish your Extension
After you've finished building your Extension, it's time to publish it to the store for all to use. There are a few steps you will need to complete before you release it. Extensions are expected to be a bundle that can be statically served.
Design an Icon
Extensions need to have a clean, visible, and memorable icon before being added to the store. We have a tutorial on figma on how to create your own.
If you use a framework like React, you will need to build a static output folder which renders the extension's contents statically. The default template already has the build steps configured, just confirm that it works by running the build command in the shell.
If you are using HTML/CSS/JS, set the build command to a single space
" " and set the output directory to your Repl's base URL
npx vite build will create a static folder
vite build in your
package.json file and set the extension's build command to
npm run build. Next, set the output folder to
Next.js supports building a static HTML export, but some features such as server-side rendering and API routes are not supported.
next.config.js, set the
output property to
The required steps to build the static output folder consist of:
- Deleting the
- Building in development mode
All three steps can be collapsed into a single bash command, which can be set as the
"export" command in
"dev": "next dev",
"build": "next build",
"start": "next start",
"export": "rm -rf .next && export NODE_ENV=development && yarn build && next export"
next export will create a static folder
out. In the Extension Devtools, set the build command to
npm run export and the output folder to
After your extension has been published, you must wait for a Replit staff member to review it before it can be put on the store.