String >. Compares character by character — unsafe for versions.
Why it lies."9" beats "1" even though 1.9 < 1.13.
Numeric parts. Split, convert, then compare.
Loaded build. Last line prints the real _.VERSION.
Compatibility
Browser & Runtime Support
_.VERSION ships with Underscore.js (1.x). It runs anywhere Underscore runs — modern browsers (CDN or bundle) and Node.js / Bun / Deno with npm install underscore.
✓ Stable · Underscore 1.x
_.VERSION
Available in [email protected] (UMD / ESM). The official docs sample is 1.13.8. Works in evergreen browsers and current Node LTS when Underscore is loaded.
100%With Underscore 1.x
Google ChromeSupported · Desktop & Mobile
Full support
Mozilla FirefoxSupported · Desktop & Mobile
Full support
Apple SafariSupported · macOS & iOS
Full support
Microsoft EdgeSupported · Chromium
Full support
Internet ExplorerNo native support · Use a polyfill
Polyfill
OperaSupported · Modern versions
Full support
Samsung InternetSupported · Android
Full support
BunSupported · JavaScript runtime
Supported
DenoSupported · JavaScript runtime
Supported
Node.jsSupported · Server runtime
Supported
Android WebViewSupported · Modern WebView
Full support
_.VERSIONUnderscore 1.x+
Bottom line: Safe for production once Underscore is on the page or in your bundle. Not a native browser API — load Underscore first. Prefer a pinned CDN version (e.g. [email protected]).
Frequently Asked Questions
_.VERSION is a string property on the Underscore object that reports which release is loaded. The official docs sample is 1.13.8. It is metadata, not a function: read it, do not call it.
_.VERSION by itself. The docs show => 1.13.8, the version of the library those docs describe. A CDN pin such as [email protected] prints the same string.
No. It is a property. typeof _.VERSION is string. _.VERSION() throws because a string is not callable. Write _.VERSION with no parentheses.
No. Underscore sets it when the file loads. Reloading the page or swapping the script tag is how you pick up a different build.
Avoid it. Lexicographic compare is wrong for semver: '1.9.0' > '1.13.8' is true as strings because '9' > '1'. Split on dots and compare numbers, or test exact equality for one known build.
No. It is a stable Underscore property. The current docs and the 1.13.8 UMD build used in these labs both report 1.13.8.