add template dependencies to loader dependencies #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In its current state, only the loader's input EJS file is defined as a dependency.
It means that everytime we update the file, webpack will trigger a new processing.
Problem is when we add included file to the template with one of those directives :
We can check that EJS transitive dependencies are not exposed by looking into
template.dependencies
content.As this loader is a LoaderContext instance, we have access to
this.dependency
which allow adding dependencies to this entry file processing :To declare EJS dependencies, we need to bind it from EJS to the loader :