zotero-plugin-template/.env.example
Northword 0d76086064
feat: publish development scripts as independent npm packages (#109)
* feat!: use zotero-plugin-scaffold

* fix: tsc error

* docs: update readme and comment

* fix: clean code, remove useless file

* fix: update zotero-plugin-scaffold

* fix: set esbuild target to ff115

* chore: clean and update deps

* fix: Simplify config files and update dep

* fix: update deps

* chore: update renovate config

* fix: default use proxy mode to install plugin

* chore: bump scaffold to 0.0.19

resolve: #113

* fix: bump scaffold to 0.0.20

* fix: use new devtools hack
2024-05-15 15:33:42 +08:00

29 lines
1.2 KiB
Plaintext

# Usage:
# Copy this file as `.env` and fill in the variables below as instructed.
# If you are developing more than one plugin, you can store the bin path and
# profile path in the system environment variables, which can be omitted here.
# The path of the Zotero binary file.
# The path delimiter should be escaped as `\\` for win32.
# The path is `*/Zotero.app/Contents/MacOS/zotero` for MacOS.
ZOTERO_PLUGIN_ZOTERO_BIN_PATH = /path/to/zotero.exe
# The path of the profile used for development.
# Start the profile manager by `/path/to/zotero.exe -p` to create a profile for development.
# @see https://www.zotero.org/support/kb/profile_directory
ZOTERO_PLUGIN_PROFILE_PATH = /path/to/profile
# The directory where the database is located.
# If this field is kept empty, Zotero will start with the default data.
# @see https://www.zotero.org/support/zotero_data
ZOTERO_PLUGIN_DATA_DIR =
# Custom commands to kill Zotero processes.
# Commands for different platforms are already built into zotero-plugin,
# if the built-in commands are not suitable for your needs, please modify this variable.
# ZOTERO_PLUGIN_KILL_COMMAND =
# GitHub Token
# For release-it auto create release and upload assets
# GITHUB_TOKEN =