We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
version
v1.2.168
platform
win11
problem
error when calling a macro referencing a $default namespace symbol: Could not resolve symbol: nbb.internal.moment$default/now
Could not resolve symbol: nbb.internal.moment$default/now
repro
nbb.edn
{:paths ["src"]}
moment
npm init npm i moment
src/macros.cljs
$default
(ns macros (:require ["moment$default" :as mmt])) (.now mmt) ;; => 1677315062961 ;; (issue.case 1) Can't call instance method on $default namespace ;; (defmacro mm-1 [] `(.now mmt)) #_(mm-1) ;; => Could not find instance method: now (macroexpand-1 '(mm-1)) ;; => (.now "nbb.internal.moment$default") (mmt/now) ;; => 1677315113666 ;; (issue.case 2) Neither can call fn on $default namespace (defmacro mm-2 [] `(mmt/now)) #_(mm-2) ;; => Could not resolve symbol: nbb.internal.moment$default/now (macroexpand-1 '(mm-2)) ;; => (nbb.internal.moment$default/now)
expected behavior
Should be able to use the $default namespace in macros as any other js library namespace.
Thanks,
(this is a follow up from #311)
The text was updated successfully, but these errors were encountered:
Fixed in 1.2.169
Sorry, something went wrong.
Thanks a lot! it works like a charm now 🙇
No branches or pull requests
version
v1.2.168
platform
win11
problem
error when calling a macro referencing a $default namespace symbol:
Could not resolve symbol: nbb.internal.moment$default/now
repro
nbb.edn
moment
src/macros.cljs
to test$default
namespace callsexpected behavior
Should be able to use the
$default
namespace in macros as any other js library namespace.Thanks,
(this is a follow up from #311)
The text was updated successfully, but these errors were encountered: