Closed gdanov closed 1 year ago
do older versions still work for you? how did you install nbb, locally, globally? can you provide a repro repository?
I just erased everything in the node folder and ran npx i nbb -g
then nbb
before that tested with npx, same.
I can reproduce this locally too:
npm install -g nbb@1.1.149
gives this problem, but:
npm install -g nbb@1.1.148
doesn't.
right. 148 and 147 are good.
Releasing 1.1.150 now. It seemed this bug is introduced by upgrading shadow-cljs. I tested with 2.20.6 and the bug first starts happening with 2.20.7. cc @thheller
@thheller If you're interested in reproducing:
deps.edn
and change shadow's versionbb release
./cli.js
for testingnpm install -g nbb@1.1.150
now works for me. Let's leave the issue open until we sorted it out with shadow. I'd be happy to create an issue with shadow-cljs if necessary.
How do I turn on --pseudo-names
for the release build? No clue what happens where.
Nevermind. It is passed through in the bb release
command.
Found the problem. In 2.20.7 I changed how the ESM import
statements are handled, so that JS tools can tree-shake them properly. What I guess I missed is that in this case it moves the code from the nbb-main-impl module to the nbb-main module and calls it there. The code does not account for ESM references moving cross modules, so this fails now.
@thheller
bb release --pseudo-names
should work. Thanks for looking into it.
Should be fine again in 2.20.13.
@thheller Thanks!
version
"version": "1.1.149",
platform
osx ventura
problem
repro
nbb stopped working, not sure why. fresh node re-install does not help.