Cloning Exporters

All exporter packages are backed by GitHub repositories. This allows Exporter Store to take advantage of all GitHub features like forking, distributing versions, or even provide a familiar place to report issues or feature requests directly to the author.

Forking the GitHub exporter repository

To get your clone of the Exporter Package you like, start by navigating to Exporter detail in Exporter Store by clicking on the store tile, and then click on GitHub Repo. This will take you directly to the backing repository.

Next, fork the exporter on GitHub to make a copy that tracks updates from upstream! This is highly recommended, especially if you are making copies of Supernova-developed exporters — we are constantly improving upon them and you will get the updates for free.

Forking a GitHub repository using the user-friendly interface

When you have forked the repository, you are now almost ready to push

Changing Unique Identifier

Before you can use the cloned package with your workspace, you should change its unique package identifier - this will save you some time later when you want to make it available to other users, as all packages must be uniquely identified. If you don't plan to make your modification public, feel free to skip this step.To change the exporter ID, locate exporter.json in the root directory and change it to something else - then, commit the change. It is recommended you use reverse domain name notation to describe your package:

Properly identified Flutter Exporter package provided by Supernova Team

Publishing a new package

Now that you have your own repository with forked content and optionally changed UID, you can link the Exporter package with your workspace. This will install a private exporter that will be only visible to you, both on the Cloud and in the VSCode extension. Go to Exporter Store, click + NEW and provide the URL of the forked repository.

You can validate that the new forked exporter is available right in the installed exporters. If you also renamed the exporter in exporter.json file, you will see the new name there as well.

Forked exporter showing up right with the original one in the workspace installed exporters