hmm does (js/super.connectedCallback) work?

kind of a hack I guess, still need to add the same (super) logic that the constructor has I guess

No, js/super.connectedCallback doesn't work. It generates super$ symbol and then can't find it. And this one doesn't work either 😞 (.connectedCallback (super))

Spitting it out with (js* "super.connectedCallback()") doesn't work either, since there are some assignments before super call and javascripts crashes with 'super' keyword unexpected here

I have a bit of time later, I'll look into it

hmm yeah this will not be an easy fix unfortunately

I'm basically just creating the class basic construct with constructor

and then the regular extend-type from cljs core for the protocol and Object methods

but they to TheClass.prototype.whatever = function(...) {}

and super is not available in that context

https://github.com/thheller/shadow-cljs/issues/1137

(.. lit/LitElement -prototype -connectedCallback (call this)) should work I guess but isn't much better thant what you had

Thank you so much for looking into it. I'll follow the issue and will use the workaround for now.

how are you building the first place?

I assume :target :esm?

yes, :target :esm

stripe includes an export target for deno now, but I have no clue if and how I can use this.. not much experience in the js-world yet.

this is part of the package.json:

"exports": {
    "types": "./types/index.d.ts",
    "browser": {
      "import": "./esm/stripe.esm.worker.js",
      "require": "./cjs/stripe.cjs.worker.js"
    },
    "deno": {
      "import": "./esm/stripe.esm.worker.js",
      "require": "./cjs/stripe.cjs.worker.js"
    },
    "worker": {
      "import": "./esm/stripe.esm.worker.js",
      "require": "./cjs/stripe.cjs.worker.js"
    },
    "default": {
      "import": "./esm/stripe.esm.node.js",
      "require": "./cjs/stripe.cjs.node.js"
    }
  }

so this is running in deno? ie. it doesn't need packages to be bundled?

https://shadow-cljs.github.io/docs/UsersGuide.html#_third_party_tool_integration

then you can just set :js-options {:js-provider :import} in the build config

and just require directly (:require ["npm:stripe@^11.16$default" :as Stripe])

looks a bit weird but should be ok?

(:require ["npm:stripe@^11.16" :default Stripe]) also works but that is "deprecated" and unofficial

or when you need to bundle skip the :js-provider setting and just (:require ["stripe$default" :as Stripe])

the $default stuff is explained here https://shadow-cljs.github.io/docs/UsersGuide.html#_using_npm_packages

with {:js-provider :import} the require strings are just passed through directly to deno, shadow-cljs does nothing to them

so as long as deno can resolve then its fine

yeah it‘s running in deno - can I exclude only stripe though and include other npm libs directly?

I tried setting :js-options {:js-provider :import} and requiring with (:require ["npm:stripe@^11.16$default" :as Stripe]), but it fails with this error

Closure compilation failed with 1 errors
--- shadow.js.shim.module$npm_stripe$^11_16$default.js:2
Parse error. Semi-colon expected

if I bundle it and require it with (:require ["stripe$default" :as Stripe]), is there a way to choose the deno version? (as in the deno-export of the stripe npm package)

ah doh. I guess the ^ is not getting escaped

with the package.json above the browser is exactly the same as deno

so shouldn't matter?

you can set :js-options {:export-conditions ["deno" "import" "require" "default"]} to get the deno parts of the exports

oooh didn't see that browser and deno point to the same..

pheeeeew, it works again, thanks a lot! 😌

Parse error. Semi-colon expected should be fixed in 2.25.1

Thanks! I'll update..