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
Tests and app code get through a pipeline in Karma:
They are determined (wildcard resolution).
They are loaded into memory (and cache).
Watching is set up (if enabled).
They undergo preprocessing.
They are inserted in the respective context.html template expansion.
They are served.
Preprocessing takes in a file and modifies it (i.e. input: 1 file; output: 1 file). However, this pipeline misses a step that offers a lot of potential: bundling. After preprocessing (between 3 and 4), bundling would get as input the preprocessed files and output other files (not necessarily in a 1:1 relationship).
Bundling could be used for:
Splitting large script files. This has been a need in our tests on Karma, as frequently big scripts mess up with the event loop and memory.
The input config supplies 'patterns' which FileList expands into Files.
These files are preprocessed and then 'file-list-modified' is fired.
The event offers a pair of file lists, {included, served}.
The bundle layer maps this pair to a new pair where fewer files are included.
By default the bundler copies the inputs to outputs.
Fixeskarma-runner#3633
Tests and app code get through a pipeline in Karma:
context.html
template expansion.Preprocessing takes in a file and modifies it (i.e. input: 1 file; output: 1 file). However, this pipeline misses a step that offers a lot of potential: bundling. After preprocessing (between 3 and 4), bundling would get as input the preprocessed files and output other files (not necessarily in a 1:1 relationship).
Bundling could be used for:
The text was updated successfully, but these errors were encountered: