-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
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
build with example setup fails: goog.debug.Logger.level missing, required by fulcro/logging.cljc #65
Comments
I just hit this issue as well. By using this :cards {:target nubank.workspaces.shadow-cljs.target
:ns-regexp "-(test|cards)$"
:output-dir "public/js/workspaces"
:asset-path "/js/workspaces"
:preloads [] ; optional, list namespaces to be pre loaded
:js-options {:resolve {"goog.debug.Logger.Level"
{:target :global
:global "goog.log.Logger.Level"}}},
} however, this does not make the workspaces usable. Loading the workspaces file leads to these errors:
it's not yet clear whether this means the logger fix is incorrect, or that this is a different problem. |
I believe the For me, this builds correctly after downgrading from
I have added some more information and a minimal working example here given the specificity of this breakage, it's likely related to this issue: thheller/shadow-cljs#980 |
The These are tooling-side changes. For code-side changes:
I tried to look into what it takes to move, but it didn't look easy to me.
this error seems associated with clojure 1.9, but this error happens on a blank system with a fresh clojure 1.11 installation, so I stopped there
so for now, the easiest method I have is by including the |
What does this mean "including the [nubank/workspaces "1.1.2"] dependency directly"? What file do I put it in? |
put it in shadow-cljs |
Thank you I was able to get it to work |
From what I learned, google closure and cljs removed that api, but fulcro2 still depends on it.
I've just set up a project and ran into this:
This is with node 14 & 17 and OpenJDK 17.
I'm not really experienced with cljs and node dependency handling, any tips on how I can get around this?
Any help apreciated,
Mathias
The text was updated successfully, but these errors were encountered: