Gathering detailed insights and metrics for @rednil/rollup-plugin-version-injector
Gathering detailed insights and metrics for @rednil/rollup-plugin-version-injector
rollup.js plugin to auto inject the current version into the source code
Installations
npm install @rednil/rollup-plugin-version-injectorDeveloper Guide
BETA
Typescript
Yes
Module System
CommonJS
Node Version
14.15.1
NPM Version
6.14.9
Releases
Unable to fetch releases
Languages
2
TypeScript
JavaScript
TypeScript (98.2%)
JavaScript (1.8%)
Developer
rednil
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
14 Commits
6 Branches
1 Contributors
Updated on Dec 04, 2020
Maintainers
1
Package Meta Information
Latest Version
1.0.0
Package Id
@rednil/rollup-plugin-version-injector@1.0.0
Unpacked Size
65.54 kB
Size
12.58 kB
File Count
25
NPM Version
6.14.9
Node Version
14.15.1
Total Downloads
Cumulative downloads
Total Downloads
NaN
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
Weekly Downloads
Monthly Downloads
Yearly Downloads
rollup-plugin-version-injector
A simple rollup.js plugin to inject your application's version number and/or today's date into your built js, html, and css files!
Getting started
Install from npm
1npm i --save-dev rollup-plugin-version-injector
Add it to your rollup.config.js build configuration.
1import versionInjector from 'rollup-plugin-version-injector'; 2// or 3const versionInjector = require('rollup-plugin-version-injector'); 4 5export default { 6 // other configuration 7 plugins: [ 8 versionInjector() 9 // any other plugins 10 ] 11};
Then you can add tags to your source code and it will inject the version where you specified. Example:
src/app.js (example file)
1export class MyApp { 2 getVersion() { 3 return '[VI]{version} - {date}[/VI]'; 4 } 5 // other code 6}
version-injector (VI) will replace that code in your built source to return the following:
build/built-app.js (example build file)
1export class MyApp { 2 getVersion() { 3 return '1.2.1 - June 9, 2007 17:46:12'; 4 } 5 // other code 6}
VI will also inject the version into your files as a comment. Example:
build/index.html (example file)
1<!-- Version: 1.2.1 - June 9, 2007 17:46:12 --> 2<!DOCTYPE html> 3<html lang="en"> 4 ... 5</html>
Basic Usage
VI has two uses -- it will Inject the version number and/or today's date into your generated files in:
VI will replace '{version}' with the version found in your package.json and '{date}' with today's date in the format specified in the configuration.
VI supports injecting the version into all
js,html, andcssfiles output by rollup.
Injected in the source code
VI will only look between the configured tagIds. For example, the default tagId is VI so VI is looking for:
1// string in your javascript file 2const VERSION = '[VI]Version: {version} - built on {date}[/VI]';
VI will only replace the '{version}' and '{date}' found within those tagIds.
1// output after VI has run 2const VERSION = 'Version: 1.2.1 - built on June 9, 2007 17:46:12';
You can change the date format, tagId, and which files to look in using the configuration object passed into the versionInjector() function.
As a comment
It will replace the '{version}' and '{date}' found in the configured tag. For example, the default configured tag is:
1tag: 'Version: {version} - {date}'
You can change the date format, tag, and which files to inject the comment into using the configuration object passed into the versionInjector() function.
Configuration
Anything not specified/overwritten in your versionInjector() configuration will use the default configuration.
default config
1{ 2 injectInComments: { 3 fileRegexp: /\.(js|html|css)$/, 4 tag: 'Version: {version} - {date}', 5 dateFormat: 'mmmm d, yyyy HH:MM:ss' 6 }, 7 injectInTags: { 8 fileRegexp: /\.(js|html|css)$/, 9 tagId: 'VI', 10 dateFormat: 'mmmm d, yyyy HH:MM:ss' 11 }, 12 packageJson: './package.json', 13 logLevel: 'info', 14 logger: console, 15 exclude: [] 16};
All available date formats can be found at dateformat.
injectInTags
The following properties are available:
1versionInjector({ 2 injectInTags: false /* or */ { 3 // Regexp for files to match against 4 fileRegexp: Regex 5 // string of the tagId to look for 6 // Ex: 'ACK' => VI will look for '[ACK]...[/ACK]' 7 tagId: string 8 // string of valid dateformat 9 dateFormat: string 10 } 11})
Note: The
tagIdwill be wrapped in opening and closing brackets. Example:[tagId][/tagId]
All available date formats can be found at dateformat.
injectInComments
The following properties are available:
1versionInjector({ 2 injectInComments: false /* or */ { 3 // Regexp for files to match against 4 fileRegexp: Regex 5 // string of tag to be injected 6 tagId: string 7 // string of valid dateformat 8 dateFormat: string 9 } 10})
packageJson
This is the relative path to your package.json file from your rollup config file. Default is './package.json'.
logLevel
This is the log levels for verion-injector. Default value is 'info'. Available values are:
'debug', 'info', 'warn', 'error'
logger
Default is the console, but can be any logger you prefer that matches the ILogger interface.
excludes
This is an array of specific files you want to exclude from any processing. This must be the full file name without the path.
Credits
This is essentially a less fancy port of the webpack-auto-inject-version.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no SAST tool detected
Details
- Warn: no pull requests merged into dev branch
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 0/14 approved changesets -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
license file not detected
Details
- Warn: project does not have a license file
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'master'
Reason
58 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-968p-4wvh-cqc8
- Warn: Project is vulnerable to: GHSA-67hx-6x53-jw92
- Warn: Project is vulnerable to: GHSA-h5c3-5r3r-rr8q
- Warn: Project is vulnerable to: GHSA-rmvr-2pp2-xj38
- Warn: Project is vulnerable to: GHSA-xx4v-prfh-6cgc
- Warn: Project is vulnerable to: GHSA-93q8-gq69-wqmw
- Warn: Project is vulnerable to: GHSA-v6h2-p8h4-qcjw
- Warn: Project is vulnerable to: GHSA-grv7-fg5c-xmjg
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-w573-4hg7-7wgq
- Warn: Project is vulnerable to: GHSA-ww39-953v-wcq6
- Warn: Project is vulnerable to: GHSA-pfrx-2q88-qq97
- Warn: Project is vulnerable to: GHSA-765h-qjxv-5f44
- Warn: Project is vulnerable to: GHSA-f2jv-r9rf-7988
- Warn: Project is vulnerable to: GHSA-43f8-2h32-f4cj
- Warn: Project is vulnerable to: GHSA-rc47-6667-2j5j
- Warn: Project is vulnerable to: GHSA-qqgx-2p2h-9c37
- Warn: Project is vulnerable to: GHSA-78xj-cgh5-2h22
- Warn: Project is vulnerable to: GHSA-2p57-rm9w-gvfp
- Warn: Project is vulnerable to: GHSA-896r-f27r-55mw
- Warn: Project is vulnerable to: GHSA-9c47-m6qq-7p4h
- Warn: Project is vulnerable to: GHSA-29mw-wpgm-hmr9
- Warn: Project is vulnerable to: GHSA-35jh-r3h4-6jhm
- Warn: Project is vulnerable to: GHSA-4r62-v4vq-hr96
- Warn: Project is vulnerable to: GHSA-5v2h-r2cx-5xgj
- Warn: Project is vulnerable to: GHSA-rrrm-qjm4-v8hf
- Warn: Project is vulnerable to: GHSA-7wpw-2hjm-89gp
- Warn: Project is vulnerable to: GHSA-952p-6rrq-rcjv
- Warn: Project is vulnerable to: GHSA-f8q6-p94x-37v3
- Warn: Project is vulnerable to: GHSA-xvch-5gv4-984h
- Warn: Project is vulnerable to: GHSA-r683-j2x4-v87g
- Warn: Project is vulnerable to: GHSA-5fw9-fq32-wv5p
- Warn: Project is vulnerable to: GHSA-px4h-xg32-q955
- Warn: Project is vulnerable to: GHSA-hj48-42vr-x3v9
- Warn: Project is vulnerable to: GHSA-hrpp-h998-j3pp
- Warn: Project is vulnerable to: GHSA-p8p7-x288-28g6
- Warn: Project is vulnerable to: GHSA-gcx4-mw62-g8wm
- Warn: Project is vulnerable to: GHSA-x2pg-mjhr-2m5x
- Warn: Project is vulnerable to: GHSA-c2qf-rxjj-qqgw
- Warn: Project is vulnerable to: GHSA-44c6-4v22-4mhx
- Warn: Project is vulnerable to: GHSA-4x5v-gmq8-25ch
- Warn: Project is vulnerable to: GHSA-4rq4-32rv-6wp6
- Warn: Project is vulnerable to: GHSA-64g7-mvw6-v9qj
- Warn: Project is vulnerable to: GHSA-vx3p-948g-6vhq
- Warn: Project is vulnerable to: GHSA-3jfq-g458-7qm9
- Warn: Project is vulnerable to: GHSA-r628-mhmh-qjhw
- Warn: Project is vulnerable to: GHSA-9r2w-394v-53qc
- Warn: Project is vulnerable to: GHSA-5955-9wpr-37jh
- Warn: Project is vulnerable to: GHSA-qq89-hq3f-393p
- Warn: Project is vulnerable to: GHSA-f5x3-32g6-xq36
- Warn: Project is vulnerable to: GHSA-jgrx-mgxx-jf9v
- Warn: Project is vulnerable to: GHSA-72xf-g2v4-qvf3
- Warn: Project is vulnerable to: GHSA-7p7h-4mm5-852v
- Warn: Project is vulnerable to: GHSA-38fc-wpqx-33j7
- Warn: Project is vulnerable to: GHSA-j8xg-fqg3-53r7
- Warn: Project is vulnerable to: GHSA-6fc8-4gx4-v693
- Warn: Project is vulnerable to: GHSA-3h5v-q93c-6h6q
- Warn: Project is vulnerable to: GHSA-c4w7-xm78-47vh
Score
1.3
/10
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