Open Hidfeel opened 7 years ago
@Hidfeel I don't have much windows development experience, and I haven't seen this particular issue. Could you try with kvlt 0.1.4-SNAPSHOT
, as it depends on a newer version of promesa?
Also the dependencies section of your project file would be great.
:plugins [[lein-cljsbuild "1.1.4"] [lein-resource "16.9.1"] ]
:dependencies [
[org.clojure/clojurescript "1.9.293"]
[org.clojure/clojure "1.8.0"]
[io.nervous/kvlt "0.1.4-SNAPSHOT"]
]
0.1.4-SNAPSHOT
also has the same problem, tomorrow I'll try on mac, and add more info
Cool. I'd be curious to know if you see this issue with the 1.8 series of cljs, e.g. 1.8.51
I test it on mac and use cljs@1.8.51 ,problem is still here. project is here
Thanks, will look today
On 23 Nov 2016 03:42, "Hidfeel" notifications@github.com wrote:
I test it on mac and use cljs@1.8.51 ,problem is still here. project is here https://github.com/Hidfeel/cljs-test
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/nervous-systems/kvlt/issues/18#issuecomment-262428997, or mute the thread https://github.com/notifications/unsubscribe-auth/ABYuK1IySYEbDekTTj1WXAbD_k1pS777ks5rA7YzgaJpZM4K5Ycb .
@Hidfeel A couple of things:
This isn't specific to your problem above, but with cljs projects which don't bundle their js dependencies (like kvlt), lein-npm
is required so that lein deps
fetches the node modules. Because plugin dependencies are not transitive, you need to explicitly add [lein-npm "0.6.2"]
to your project's :plugins
vector. Run lein deps
once, and the node deps will be fetched. This won't fix your problem, but will fix issues you would likely see later on at runtime (or else allow you to skip having to globally install the dependencies, if that's what you did).
:asset-path
is messing with the relative paths - I've never used that feature, but if you remove it and rebuild, then node js-src/main.js
from the project directory will fix your problem
thanks for your kindness to help me try to solve my problem.
I would like to use package.json
to manage js dependences ,because my deploy env is something like heroku ,package.json
is necessary .lein-npm
is a nice choice if I dont need package.json
, I will look deeper in it. The project is try to show that my without any other libs, and as you say , dependencies is not the main problem.
why I use :asset-path
,that is I hope to complie js in a single dir js-src
and run nodejs app in the js-src
directly, The point is the package.json
and node command line
is executing in the js-src
and If I want to deploy,I just need to deploy js-src
as submodule or anything else , without any other clj
and cljs
files .
If I remove :assert-path
I will get other Cannot find module
error like:
Error: Cannot find module '/Users/chita/test/cljs-test/js-src/js-src/goog/bootstrap/nodejs.js'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object.<anonymous> (/Users/chita/test/cljs-test/js-src/main.js:19:1)
at Module._compile (module.js:397:26)
at Object.Module._extensions..js (module.js:404:10)
at Module.load (module.js:343:32)
I hope I have show my reason to use :assert-path
clearly , and I agree with you that :asset-path
mess these deps up
OK - I understand why lein npm doesn't make sense if you're managing your own package.json.
I don't know if the issue with the bluebird dependency is to do with promesa, or if it's a more general clojurescript compiler issue.
Nor do I . One of them misunderstand something with :assert-path
or other things, promesa
I guess.
:assert-path
is not a option that often be used.
looks like something wrong with
promesa
my compiler config