npm detect-browser 4.0.1

latest releases: 5.3.0, 5.2.1, 5.2.0...
5 years ago

FIX: Address babel static analysis issue

TL; DR; If you were having "critical dependency" (see issue #84) warning when using detect-browser@4.0.0 it's now fixed (see PR #85). You should upgrade to 4.0.1 to resolve the issue.


Due to the use of the TypeScript umd transpilation target, the generated index.js file included code that implied dynamic require behaviour (something that is inherent in the UMD header pattern apparently). The TypeScript compiler has now been switched to generating a standard commonjs output file.

Given that a UMD compilation target was selected for the 4.x only very recently to satisfy a potential use case of detect-browser within a requirejs context, I feel this is an acceptable (and necessary) change.

I will look to create a transpiled file that can be used in a requirejs context as part of completing #83 sometime in the future.

Don't miss a new detect-browser release

NewReleases is sending notifications on new releases.