1.0.2

1.0.2 — an export that fails now says so

Fixed

• An unexpected error during an export used to be swallowed: the menu item did
  nothing at all and there was no way to tell why. Every export path now reports
  its failure in a notice.
• The native save dialog reaches a part of Electron that Electron itself removed
  in version 14 and that Obsidian puts back for compatibility. If that ever stops,
  the export falls back to the configured export folder and says so, instead of
  failing on a click.
• With "Ask where to save" turned off, an existing file of the same name is no
  longer overwritten. The export folder sits outside the vault, where a name
  collision means somebody else's file. With the dialog on, the path is one you
  confirmed yourself, so overwriting stays your decision.

Also

• First test suite: the naming and path rules, including that the timestamp is
  local time rather than UTC — the reason an evening export is not stamped with
  yesterday's date.
• README: install from the community catalogue.
• Internals: Node imports use the node: prefix, and linting is part of the
  build, so a green build means a clean one.

1.0.1

Right-click a note in the file explorer — or a text selection in the editor — and save a copy outside the vault as .md or .txt.

• Export items on the file and editor context menus; selection items appear only when something is selected.
• A native save dialog on every export, or write straight to a configured folder.
• Notes open with unsaved edits export their live editor content, not the older copy on disk.
• The same four operations are available from the command palette and can be bound to hotkeys.

Desktop only — the plugin uses Node's filesystem APIs.

Manual install: copy main.js and manifest.json into <vault>/.obsidian/plugins/quick-export/.