@urbanslug you can import using the default keyword (see shadow user manual) or just access the property named “default”

@lee.justin.m I swear I gleaned over this manual a couple of times and didn't see this

Hmm, trying to use the aws-sdk package and it is bundling the node.js version:

(ns my-ns.aws 
  (:require ["aws-sdk/lib/util" :as util]))

(prn [(util/isNode) (util/isBrowser)])
;; => [true false]

"browser": {
    "lib/aws.js": "./lib/browser.js",
    "fs": false,
    "./global.js": "./browser.js",
    "./lib/node_loader.js": "./lib/browser_loader.js"
  },

there is a also this field

"browserify": {
    "transform": "./dist-tools/transform.js"
  },

which target? :browser?

yes

hehe that result is kind of hilarious

isBrowser: function isBrowser() { return process && process.browser; },
  isNode: function isNode() { return !util.isBrowser(); },

very sophisticated checking logic 😉

haha yeah

but the check should succeed. checking why it doesn't

try setting :closure-defines {shadow.js.process.browser true}

thats supposed to be set for :browser target by default but for some reason isn't

👍:skin-tone-2: that works

yeah browser target only set this for release builds

will fix but setting it manually is fine for now

great. i was worried this would be related to some weirdness with how the aws-sdk package is built

the browser field in package.json is fully supported. its just that checked that failed