angular-templatecache-loader-2
Advanced tools
+1
-1
| { | ||
| "name": "angular-templatecache-loader-2", | ||
| "version": "0.3.0", | ||
| "version": "0.3.1", | ||
| "description": "Webpack angular templateCache loader", | ||
@@ -5,0 +5,0 @@ "main": "index.js", |
+16
-1
| # Angular templatecache webpack loader | ||
| > This repo adds the | ||
| Puts HTML files to Angular $templateCache. | ||
@@ -49,5 +51,18 @@ | ||
| 3. You can also use context in webpack to pass correct template url. See [Context example](https://github.com/EJIqpEP/angular-templatecache-loader/tree/master/examples/context) | ||
| 3. relativeTo - remove a string from the path | ||
| relativeTo is used to strip a matching prefix from the path of the input html file. | ||
| ```javascript | ||
| { | ||
| test: /\.html$/, | ||
| loader: "angular-templatecache-loader?relativeTo=/public/" | ||
| } | ||
| ``` | ||
| The above will remove the "/public/" from the generated templateUrl path | ||
| 4. You can also use context in webpack to pass correct template url. See [Context example](https://github.com/EJIqpEP/angular-templatecache-loader/tree/master/examples/context) | ||
| ```javascript | ||
| var app = path.join(__dirname, 'app'); | ||
@@ -54,0 +69,0 @@ |
Network access
Supply chain riskThis module accesses the network.
Found 1 instance in 1 package
Uses eval
Supply chain riskPackage uses dynamic code execution (e.g., eval()), which is a dangerous practice. This can prevent the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.
Found 2 instances in 1 package
Dynamic require
Supply chain riskDynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.
Found 1 instance in 1 package
Long strings
Supply chain riskContains long string literals, which may be a sign of obfuscated or packed code.
Found 1 instance in 1 package
Network access
Supply chain riskThis module accesses the network.
Found 1 instance in 1 package
Uses eval
Supply chain riskPackage uses dynamic code execution (e.g., eval()), which is a dangerous practice. This can prevent the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.
Found 2 instances in 1 package
Dynamic require
Supply chain riskDynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.
Found 1 instance in 1 package
Long strings
Supply chain riskContains long string literals, which may be a sign of obfuscated or packed code.
Found 1 instance in 1 package
1061115
0.03%72
26.32%