You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 23, 2019. It is now read-only.
During development, sometimes you git pull changes and need to install a new package. I am not proposing Mendel should install the packages, but I think we should track the dependencies.
IIRC, when filesystem watcher scans folders, we don't wildcard watch for node_modules for performance reasons. But we do watch every file we require. I am thinking to fix this, we just need to watch for new node_modules/ we know are missing.
For instance, this is the proposed workflow:
Git pull something, a new file or existing file within variational or base folder requires a new dependency foo.
Dependency foo is not found
2.1. Currently I think we do not watch for the dependency foo.
2.2. Suggesting we add foo to a list of dependencies we are looking for and watch node_modules/
User installs foo manually (or maybe they have a grunt task for it).
3.1. Currently user needs to stop daemon and start again
3.2. Suggesting we get events on node_modules folder, if it matches array of missing dependencies (in example array is ['foo']) we then require the entry and start watching for changes.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
During development, sometimes you git pull changes and need to install a new package. I am not proposing Mendel should install the packages, but I think we should track the dependencies.
IIRC, when filesystem watcher scans folders, we don't wildcard watch for node_modules for performance reasons. But we do watch every file we require. I am thinking to fix this, we just need to watch for new node_modules/ we know are missing.
For instance, this is the proposed workflow:
Git pull something, a new file or existing file within variational or base folder requires a new dependency
foo
.Dependency
foo
is not found2.1. Currently I think we do not watch for the dependency
foo
.2.2. Suggesting we add
foo
to a list of dependencies we are looking for and watchnode_modules/
User installs
foo
manually (or maybe they have a grunt task for it).3.1. Currently user needs to stop daemon and start again
3.2. Suggesting we get events on
node_modules
folder, if it matches array of missing dependencies (in example array is['foo']
) we then require the entry and start watching for changes.The text was updated successfully, but these errors were encountered: