Version 1.0.0 breaks DB data saving back to file because it uses only in memory DB.
This is good feature and it's worth to implement it.
Major questions:
- Since plugin allows to merge many files into one DB, how to deal with this case? It's generally impossible to propagate DB changes back to appropriate file.
- Server reloading works via gulp's watch, so modifying source file when reloading DB will cause server reloading again causing infinite cycle then.
The solution for both issues is to save bundled DB changes to one file, speficied in options for plugin.
Version 1.0.0 breaks DB data saving back to file because it uses only in memory DB.
This is good feature and it's worth to implement it.
Major questions:
The solution for both issues is to save bundled DB changes to one file, speficied in options for plugin.