Determine where your code is running
npm install @wider/utils_where-am-icommand
npm install "@wider/utils_where-am-i"
`
Use
`javascript
// from ES MOdule
import { genre, os, engine, version, _genres } from "@wider/utils_where-am-i/index.js";
// from commonJS module
const { genre, os, engine, version, _genres } = require ("@wider/utils_where-am-i");
// from non-module environments
yourLinkOrImportMethod("a/path/to/@wider/utils_where-am-i/index.js)
var where = whereAmI();
`
The code in this package has been written deliberately in an early dialect of javascript so that identical code can run on legacy environments by just loading the file ./index.js which then exposes the whereAmI() method. This generates a simple object with the same properties that are exported in the node environment.
See the Example for the earliest versions of supported environments.
Documentation and Example Results
On npm, you can run this in RunKit and see the details for the linux server that runs npm. Typically that will return
`javascript
{
_genres: /unknown|server|browser|script/,
genre: "server",
engine: "node",
version: "v14.17.4",
computerName: "YDR-HP-2015"
os: "linux"
}
``