Strange. After running npm install stripe/react-stripe-js my dependencies are borked, returning compilation error

../node_modules/@stripe/react-stripe-js specified entries but they were all missing

Also wondering why I have the deref symbol at stripe, seems like a mistake

Still having this problem, but I've audited the directory and the files exist.

deleting the ["@stripe/react-stripe-js" requirement, compiling, re-adding it, compiling hangs. Then breaks again.

It's hard for me to tell what went wrong. I fixed my build issues by deleting my global npm directory, reinstalling the latest npm, moving my src and .edn config file into a new directory, re-initializing npm, re-installing shadow-cljs, and re-installing all npm packages. However my invoice-frontend.js now returns

malformed hexadecimal character escape sequence

the @ in this case does not mean deref. it is just a way npm packages are grouped under an "organization". so @stripe is the organization and react-stripe-js is the package in that org

has nothing to do with CLJS, just coincidence they use the @

otherwise looks correct

you can always try to ["@stripe/react-stripe-js" :as x :refer (Elements CardElement useStripe useElements)] and (js/console.log "x" x) or (js/console.dir x)

just to find out what x actually is, and see what the package provides

seems like useStripe should exist, but you seem to be getting a bunch of weird errors. so might be your disk or something

What is the best way to determine how up does one need to go? Just by binary search? 🙂

Oh, that should be related classes so es6…?

why are you setting it in the first place? the default should be "safe" enough

I was not setting it

I was assuming your answer meant to set it higher

> if you are setting any at all

I guess the default is too low then. the default is :es2020 which I assumed would be good enough

I guess you can try :compiler-options {:output-feature-set :es-next}

that doesn't transpile anything, which doesn't mean it'll work unfortunately

https://shadow-cljs.github.io/docs/UsersGuide.html#js-provider-external

is an option instead

or upgrading, just in case you are using an old shadow-cljs version

I just updated shadow-cljs and recalculated the dependencies with yarn and this came up 🙂

that doesn't necessarily tell me if you upgraded shadow-cljs 😛

you could be using deps.edn or project.clj to manage dependencies

=== Version
jar:            2.22.8
cli:            2.22.8
deps:           1.3.4
config-version: 2.22.8

I used to have 2.11.x

and it worked before?

or did it work before because you were using an older react-virtualized-auto-sizer version?

Yes, I think recalculating the dependencies brought up some incompatible version.

always gotta be careful when upgrading npm package versions

could be the closure-compiler adding a check that wasn't there before as well

can't say for sure, the error you are getting is from the closure-compiler, not shadow-cljs

can't do anything about that

Yeah, this is my problem, not yours 😄

I was just interested in hearing if someone had hit this but I’ll investigate the package deps then and see where it broke. Thanks so much for your fast replies!

Yeah, downgrading it from 1.0.9 to 1.0.6 fixed that error. Nice.

It’s not always inconsequental to do even patch version level updates 😄

it pretty much never is in the npm world 😛