This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-08-20
Channels
- # announcements (1)
- # bangalore-clj (27)
- # beginners (82)
- # boot (4)
- # chestnut (1)
- # cider (22)
- # cljs-dev (26)
- # cljsrn (4)
- # clojure (118)
- # clojure-dev (18)
- # clojure-italy (2)
- # clojure-losangeles (1)
- # clojure-nl (2)
- # clojure-russia (1)
- # clojure-spec (15)
- # clojure-uk (125)
- # clojurescript (61)
- # core-async (74)
- # cursive (2)
- # datomic (41)
- # duct (6)
- # editors (7)
- # emacs (3)
- # events (1)
- # figwheel-main (3)
- # fulcro (111)
- # hoplon (11)
- # jobs-discuss (97)
- # lein-figwheel (99)
- # off-topic (34)
- # onyx (4)
- # parinfer (9)
- # pedestal (4)
- # precept (2)
- # re-frame (5)
- # reagent (2)
- # reitit (4)
- # ring-swagger (11)
- # shadow-cljs (104)
- # spacemacs (4)
- # tools-deps (19)
- # vim (8)
- # yada (15)
First of all: Thanks for shadow-cljs. I'm still learning the details, but it has simplified my things a lot!
I'm not sure how to deal with error messages like this though:
failed to convert sources
{:tag :shadow.build.closure/convert-error, :sources [[:shadow.build.npm/resource "node_modules/openpgp/dist/openpgp.js"]]}
error was caused by
Caused by:
RuntimeException: INTERNAL COMPILER ERROR.
Please report this problem.
INTERNAL COMPILER ERROR.
Please report this problem.
null
Node(FUNCTION ): node_modules/openpgp/dist/openpgp.js:38406:70
SymmetricallyEncrypted.prototype.encrypt = async function (algo, key) {
Parent(CALL): node_modules/openpgp/dist/openpgp.js:38406:70
SymmetricallyEncrypted.prototype.encrypt = async function (algo, key) {
thanks for the help and if there's a tip jar somewhere for shadow-cjls, let me know š
@beders looks like a bug in the closure compiler. that INTERNAL COMPILER ERROR.
message is from Closure not shadow-cljs.
openpgp.js:34964: ERROR - This code cannot be converted from ES6. Undecomposable expression: Please rewrite the yield or await as a separate statement.
not much we can do for now. you could probably process it with babel first but that is not usually recommended or required.
maybe I should switch all pre-processing of node_modules
to babel. currently its only down when the file has import/export
@beders I forgot that you can set :js-options {:language-out :ecmascript-2017}
which will skip the transpilation
i feel like this is a dep error?
thank you. did deps-tree go in the new ver?
[maven] com/google/guava/guava/20.0/guava-20.0.jar
yeah donāt worry, using 25.1-jre worked
haha yeah that one worked perfectly
thank you
sure, 1 sec
could be expound or orchestra. deps i havenāt looked at in depth before
is it possible to get more context with this error?
[2018-08-20 10:43:41.614 - INFO] :shadow.build.npm/js-invalid-requires - {:requires [{:line 37, :column 17}]}
yeah unfortunately thatās all i get š
is that a require within a cljs file?
or is this after cljs has been compiled?
iāll ignore then
ah right
nice. it took me 20 minutes to move from project.clj to shadow on this project! š
literally no hiccups
haha well that was luckily pretty small š
and iām used to those errors now, from my fight with jackson
yeah iāll do that too, thank you
possible
so this is new:
getting a lot of those in my console
ah really
ah, yes, there are two types of ravens. one for client and one for server (node)
i was using the node one š
can shadow-cljs deploy to maven?
can shadow resolve deps that use S3p? https://github.com/s3-wagon-private/s3-wagon-private
if it uses deps.edn to resolve, then i assume yes?
ah i see. iād need to add a āwagonā, via Pomegranate
so i can work around this (by using a build clj script), but it would be great if we could specify wagons in build config
like https://github.com/circleci/s3-wagon-private/blob/master/src/main/resources/leiningen/wagons.clj
@biscuitpants using tools.deps did have too many bugs so currently it doesn't use tools.deps and no s3 is not supported
ah okay @thheller yeah i see its using a mix of custom code and also pom
for now I'd recommend lein/deps.edn for that since I have never looked into anything related
okay thank you
have you ever worked with pnpm
?
i think it does unfortunately, worthwhile to open an issue? iām not sure if you aim to support it
interesting. i didnāt know that. i found their method of installing (and sharing deps) to be clever
but, i have not used it too much yet
Can I trace module dependencies with shadow-cljs? I know about shadow-cljs.build.release-report, but can I get more fine-grained info? for example "which namespaces require cljs.pprint")
@arne-clojurians there is a (shadow.cljs.devtools.api/find-resources-using-ns 'cljs.pprint)
but its very basic
can't repeat it often enough: super nice tool and your support is always helpful. thanks!
:resolve is just meant for js packages, right? or can i easily switch debux for debux-stubs like described here? https://github.com/philoskim/debux#3-installation
its only for JS yes. I'm a bit hesitant addding something similar for CLJS since it would be incompatible with any other tool
I think the whole solution of stubs is kinda bad though. you can do the stubs using deps.edn
or project.clj
if you really have to
It's not such a big issue for me tbh. I can also just clean up after myself and remove the requires before doing a release
what's kind of interesting is i thought google closure compiler would be smart enough to do it by itself. i had a :require redux.core :refer [dbg] in a namespace that lands in production, but no call to dbg in it. still a lot of the pprint and analyzer stuff landed in the optimized file, resulting in something like a 150kbit pre-gzip (~50kb gzipped) decrease when i removed it