Update content on image update (#31)

* Initial work to log owning documents

* Move nitro plugin to subfolder

* Refactor module and plugin to use single cache manager

* Update types

* Refactor services to sources

* Refactor assets code to assets folder

* Improve sockets code

* Improve ignores functionality

* Reorganise files

* Housekeeping

* Finalise image resizing and watch

* Update version and docs

CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## v1.2.0
+
+- Fix image size change and live-reload [#30](../../issues/30)
+
 ## v1.1.2
 
 - Fix non-default watch port [#28](../../issues/28)

README.md

@@ -283,6 +283,8 @@ If they do, then the attribute or property is rewritten with the absolute path.
 
 Finally, Nitro serves the site, and any requests made to the transformed asset paths should be picked up and the *copied* asset served by the browser.
 
+In development, file watching propagates asset changes to the public folder, updates related cached content, and notifies the browser via web sockets to refresh any loaded images. 
+
 ## Development
 
 Should you wish to develop the project, the scripts are:

demo/nuxt.config.ts

@@ -1,4 +1,4 @@
-import { MountOptions } from '@nuxt/content'
+import type { MountOptions } from '@nuxt/content'
 
 // @ts-ignore
 const isStackblitz = process.env.GIT_PROXY?.includes('stackblitz')
@@ -52,4 +52,3 @@ export default defineNuxtConfig({
     debug: true,
   },
 })
-