Gathering detailed insights and metrics for simple-ngtemplate-loader
Gathering detailed insights and metrics for simple-ngtemplate-loader
Gathering detailed insights and metrics for simple-ngtemplate-loader
Gathering detailed insights and metrics for simple-ngtemplate-loader
Include AngularJS templates in the Webpack bundle without preload the template cache.
npm install simple-ngtemplate-loader
Typescript
Module System
Node Version
NPM Version
67.8
Supply Chain
95.1
Quality
74.8
Maintenance
100
Vulnerability
100
License
JavaScript (92.77%)
HTML (7.23%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
53 Commits
1 Watchers
1 Branches
1 Contributors
Updated on Feb 24, 2021
Latest Version
2.0.1
Package Id
simple-ngtemplate-loader@2.0.1
Unpacked Size
19.08 kB
Size
6.52 kB
File Count
18
NPM Version
6.14.11
Node Version
14.16.0
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
2
4
Based on ngtemplate-loader
Includes your AngularJS templates into your webpack Javascript Bundle.
SimpleNgTemplate loader does not minify or process your HTML at all, and instead uses the standard loaders such as html-loader or raw-loader. This gives you the flexibility to pick and choose your HTML loaders.
npm install simple-ngtemplate-loader --save-dev
SimpleNgTemplate loader will export the path of the HTML file, so you can use require directly AngularJS with templateUrl parameters e.g.
1var templateUrl = require('simple-ngtemplate-loader!html!./test.html'); 2 3app.directive('testDirective', function() { 4 return { 5 restrict: 'E', 6 templateUrl: templateUrl 7 } 8});
To remove the extra require
, check out the Baggage Example below.
The following code is wrong, Because it'll operate only after angular bootstraps:
app.directive('testDirective', function() {
return {
restrict: 'E',
templateUrl: require('simple-ngtemplate-loader!html!./test.html') // <- WRONG !
}
});
relativeTo
and prefix
You can set the base path of your templates using relativeTo
and prefix
parameters. relativeTo
is used
to strip a matching prefix from the absolute path of the input html file. prefix
is then appended to path.
The prefix of the path up to and including the first relativeTo
match is stripped, e.g.
1require('!simple-ngtemplate-loader?relativeTo=/src/!html!/test/src/test.html'); 2// c.put('test.html', ...)
To match the from the start of the absolute path prefix a '//', e.g.
1require('!simple-ngtemplate-loader?relativeTo=//Users/WearyMonkey/project/test/!html!/test/src/test.html'); 2// c.put('src/test.html', ...)
You can combine relativeTo
and prefix
to replace the prefix in the absolute path, e.g.
1require('!simple-ngtemplate-loader?relativeTo=src/&prefix=build/!html!/test/src/test.html'); 2// c.put('build/test.html', ...)
relativeTo
and prefix
parameters are interpolated using
Webpack's standard interpolation rules.
Interpolation regular expressions can be passed using the extra parameters relativeToRegExp
and prefixRegExp
which apply to single parameters, or regExp
which will apply to all three parameters.
By default, SimpleNgTemplate loader will assume you are using unix style path separators '/' for html paths in your project.
e.g. templateUrl: '/views/app.html'
. If however you want to use Window's style path separators ''
e.g. templateUrl: '\\views\\app.html'
you can override the separator by providing the pathSep parameter.
1require('simple-ngtemplate-loader?pathSep=\\!html!.\\test.html')
Make sure you use the same path separator for the prefix
and relativeTo
parameters, all templateUrls and in your webpack.config.js file.
It's recommended to adjust your webpack.config
so simple-ngtemplate-loader!html!
is applied automatically on all files ending with .html
. For Webpack 1 this would be something like:
1module.exports = { 2 module: { 3 loaders: [ 4 { 5 test: /\.html$/, 6 loader: 'simple-ngtemplate-loader?relativeTo=' + (path.resolve(__dirname, './app')) + '/!html' 7 } 8 ] 9 } 10};
For Webpack 2 this would be something like:
1module.exports = { 2 module: { 3 rules: [ 4 { 5 test: /\.html$/, 6 use: [ 7 { loader:'simple-ngtemplate-loader?relativeTo=' + (path.resolve(__dirname, './app')) }, 8 { loader: 'html-loader' } 9 ] 10 } 11 ] 12 } 13};
Make sure you already have html-loader
installed. Then you only need to write: require('file.html')
.
SimpleNgTemplate loader works well with the Baggage Loader to remove all those extra HTML and CSS requires. See an example of a directive and webpack.config.js below. Or take a look at more complete example in the examples/baggage folder.
With a folder structure:
app/
├── app.js
├── index.html
├── webpack.config.js
└── my-directive/
├── my-directive.js
├── my-directive.css
└── my-directive.html
and a webpack.config.js for webpack 1 like:
1module.exports = { 2 module: { 3 preLoaders: [ 4 { 5 test: /\.js$/, 6 loader: 'baggage?[file].html&[file].css' 7 } 8 ], 9 loaders: [ 10 { 11 test: /\.html$/, 12 loader: 'simple-ngtemplate-loader?relativeTo=' + __dirname + '/!html' 13 } 14 ] 15 } 16};
For webpack 2 like:
1module.exports = { 2 module: { 3 rules: [ 4 { 5 test: /\.js$/, 6 enforce: 'pre', 7 use: [{ loader:'baggage?[file].html&[file].css' }] 8 }, 9 { 10 test: /\.html$/, 11 use: [ 12 { loader: 'simple-ngtemplate-loader?relativeTo=' + __dirname + '/' }, 13 { loader: 'html-loader' }] 14 ] 15 } 16 ] 17 } 18};
You can now skip the initial require of html and css like so:
1app.directive('myDirective', function() { 2 return { 3 restrict: 'E', 4 templateUrl: require('./my-directive.html') 5 } 6});
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
Reason
no SAST tool detected
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 0/30 approved changesets -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More