Do you often type Markdown code manually for a link or image, or even all tabs in a window, and feel tired? Copy as Markdown can help you!

• Google Chrome: Chrome Web Store - Copy as Markdown
• Firefox: Copy as Markdown :: Add-ons for Firefox
• Microsoft Edge: Copy as Markdown - Microsoft Edge Addons

Copy as Markdown is a browser extension helps you copy the following things as Markdown to your system clipboard:

☑️ Current Tab as Link
☑️ A Link in the Page
☑️ An Image in the Page
☑️ An Image that is wrapped with a Link
☑️ All Tabs as a List of Links
☑️ Highlighted Tabs as a List of Links

You can add keyboard shortuts for copying tab(s) as Markdown. By default, Copy as Markdown does not assign any keyboard shortcuts.

Please refer to this Firefox Help: https://support.mozilla.org/en-US/kb/manage-extension-shortcuts-firefox

The Keyboard Shortcuts of extensions can be found at chrome://extensions/shortcuts URL. (Paste and open the link in the Location Bar).

• [Chrome] When copying an image, the image code does not include the alternative text of that image. This is due to API restriction.

Here is the forder structure. Platform-specific folder is used to resolve browser inconsistencies.

src/               # Shared Source Code
  background.js
  ...
chrome/            # Chrome / Chromium files
  dist/            # ../src will be copied here
  mainfest.json
  ...
firefox-mv2/       # Firefox Manifest V2 files
  dist/            # ../src will be copied here
  mainfest.json
  background.html  # Loads ESModule
  ...
firefox/           # Firefox Manifest V3 files
  dist/            # ../src will be copied here
  mainfest.json
  background.html  # Loads ESModule
  ...
compile.sh         # Copies src/**/* to <platform>/dist/

npm install -g web-ext
npm install

Since the source code are copied to platform-specific folders by compile.sh, it is recommended to use the auto-reload test script.

npm debug-chrome
npm debug-firefox
npm debug-firefox-mv3   // Requires Firefox Developer Edition

For manual debugging without auto-reload:

• Chrome: [Window] Menu -> Extensions -> Load unpacked extension
• Firefox: [Tools] Menu -> Add-ons -> [Gear] Icon -> Debug Add-ons -> Load Temporary Add-on

To debug some behaviors such as Firefox restarts (for example, are context menus installed properly), it is necessary to build an XPI package and install it on Firefox. Temporary Add-Ons won't be enough because they get uninstalled after Firefox quits.

Firefox checks signature when installing XPI. To do so,

1. Grab API keys from Firefox Add-On
2. Bump version in manifest.json. Note that AMO only accepts version number in X.Y.Z format where all 3 segments are numbers without zero prefix.
3. Run:

   web-ext sign --channel=unlisted --api-key=... --api-secret=...

It'll create an XPI that is signed with your Firefox Add-Ons account. The file will also be uploaded to Add-On Developer Hub as unlisted.

Note that Firefox Add-On keeps track of all the versions that has ever been uploaded, including 'self-distributed' (channel=unlisted).

See https://extensionworkshop.com/documentation/develop/getting-started-with-web-ext/

Unit tests are written in mocha, ./test/**/*.test.js.

To run, use npm test.

There is a qa.html that includes various edge test cases. Open it in the browser, then try Copy as Markdown with the content in it.

See MIT-LICENSE.txt