Kodai Nakamura 8748a6c4d2 fix(plugin): resolve obsidian compatibility warnings ... Why: - Obsidian's plugin checks were reporting compatibility and packaging warnings that could break popout-window behavior or leave async failures unhandled. - The build also depended on a deprecated module listing package and carried inline tests that leaked warning noise into the production bundle. What: - add @codemirror/view as a runtime dependency and replace builtin-modules with node:module builtinModules in the esbuild config - route plugin async startup and save-file hooks through compatibility helpers so delayed work uses window.setTimeout and fire-and-forget promises are explicitly handled - switch the AI progress notice to activeDocument, await clipboard writes, align extended Obsidian types, rename the settings heading, and remove unused catch bindings - move trie inline tests into dedicated Vitest files and add coverage for the new compatibility helpers to keep the build warning-free		2026-05-26 21:49:50 +09:00
..
__tests__	chore: add stylistic eslint plugin and format code	2025-12-20 20:43:05 +09:00
github.ts	fix(plugin): resolve obsidian compatibility warnings	2026-05-26 21:49:50 +09:00
jira.ts	fix(plugin): resolve obsidian compatibility warnings	2026-05-26 21:49:50 +09:00
linear.ts	fix(plugin): resolve obsidian compatibility warnings	2026-05-26 21:49:50 +09:00
replace-urls.ts	chore: add stylistic eslint plugin and format code	2025-12-20 20:43:05 +09:00