Describe the bug
main.js in the 4.13.0 release is 5.02 MB, which is over Obsidian Sync's 5 MB per-file limit on the Standard plan (Plus is 200 MB). Sync refuses to sync files over the limit, so on a Standard plan the plugin can no longer be synced between devices: a phone or a second machine that gets its plugins only through Obsidian Sync stays on the previous version (or never receives the plugin at all), while devices updated through the plugin browser are on 4.13.0.
Release asset sizes for main.js:
| Release |
main.js |
| 4.12.5 |
4.99 MB |
| 4.13.0 |
5.02 MB |
| 5.0.0-beta.2 |
4.76 MB |
So 4.12.x was already within a few KB of the limit and 4.13.0 crossed it.
To Reproduce
- Obsidian Sync on the Standard plan, with "Installed community plugins" enabled in the Sync settings.
- Update TaskNotes to 4.13.0 on one device.
- On another device, Sync reports
.obsidian/plugins/tasknotes/main.js as over the file size limit and skips it.
Expected behavior
The plugin's main.js stays under 5 MB so it can be synced on the Standard plan (e.g. a minified production build, or splitting the bundle).
Environment
- TaskNotes 4.13.0
- Obsidian Sync, Standard plan
Describe the bug
main.jsin the 4.13.0 release is 5.02 MB, which is over Obsidian Sync's 5 MB per-file limit on the Standard plan (Plus is 200 MB). Sync refuses to sync files over the limit, so on a Standard plan the plugin can no longer be synced between devices: a phone or a second machine that gets its plugins only through Obsidian Sync stays on the previous version (or never receives the plugin at all), while devices updated through the plugin browser are on 4.13.0.Release asset sizes for
main.js:main.jsSo 4.12.x was already within a few KB of the limit and 4.13.0 crossed it.
To Reproduce
.obsidian/plugins/tasknotes/main.jsas over the file size limit and skips it.Expected behavior
The plugin's
main.jsstays under 5 MB so it can be synced on the Standard plan (e.g. a minified production build, or splitting the bundle).Environment