-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
A few things I saw during install.
shadow-cljs warns on startup
± npx shadow-cljs watch :dashboard
npx: installed 99 in 3.974s
------------------------------------------------------------------------------
WARNING: shadow-cljs not installed in project.
See https://shadow-cljs.github.io/docs/UsersGuide.html#project-install
------------------------------------------------------------------------------
but the project-install section doesn't exist anymore in the docs. Maybe outdated warning.
warning about missing react
The required namespace "react" is not available, it was required by "day8/re_frame_10x/inlined_deps/reagent/v0v10v0/reagent/core.cljs".
The namespace was provided via :foreign-libs which is not supported.
Please refer to https://shadow-cljs.github.io/docs/UsersGuide.html#cljsjs for more information.
You may just need to run:
npm install react
Don't think we should be relying on globally-available dependencies. The build tool should resolve this for us.
lein integration?
Is there a way to encapsulate all the shadow-cljs stuff in leiningen? It's nice to have a single build tool that does everything. Not sure if this is normal with shadow-cljs - I've never used shadow. Or maybe I'm thinking about it wrong. I did see the lein specific docs. Is that an alternative to building with shadow-cljs?
dev/dev.clj usage
If I start a lein repl it defaults to user namespace. How do we load dev? Should dev exist under src??
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels