It was a caching problem. Sorry.

[:modules] Configuring build.
[:modules] Build failure:
FileNotFoundException: manifest.edn (No such file or directory)
	java.io.FileInputStream.open0 (FileInputStream.java:-2)
	java.io.FileInputStream.open (FileInputStream.java:219)
	java.io.FileInputStream.<init> (FileInputStream.java:157)
	 (io.clj:229)
	 (io.clj:229)
	 (io.clj:69)
	 (io.clj:165)
	 (io.clj:165)
	 (io.clj:69)
	 (io.clj:102)
	 (io.clj:86)
	clojure.core/apply (core.clj:669)
	clojure.core/slurp (core.clj:7009)
	clojure.core/slurp (core.clj:7009)
	shadow.build.targets.chrome-extension/configure (chrome_extension.clj:59)
	shadow.build.targets.chrome-extension/configure (chrome_extension.clj:48)
	shadow.build.targets.chrome-extension/process (chrome_extension.clj:310)
	shadow.build.targets.chrome-extension/process (chrome_extension.clj:305)
	clojure.lang.Var.invoke (Var.java:384)
	shadow.build/process-stage/fn--14625 (build.clj:161)
	shadow.build/process-stage (build.clj:158)
	shadow.build/process-stage (build.clj:150)
	shadow.build/configure (build.clj:389)
	shadow.build/configure (build.clj:274)
	shadow.cljs.devtools.server.worker.impl/build-configure (impl.clj:205)
	shadow.cljs.devtools.server.worker.impl/build-configure (impl.clj:156)
	shadow.cljs.devtools.server.worker.impl/do-config-watch (impl.clj:571)
	shadow.cljs.devtools.server.worker.impl/do-config-watch (impl.clj:565)
	shadow.cljs.devtools.server.util/server-thread/fn--15932/fn--15933/fn--15941 (util.clj:269)
	shadow.cljs.devtools.server.util/server-thread/fn--15932/fn--15933 (util.clj:268)
	shadow.cljs.devtools.server.util/server-thread/fn--15932 (util.clj:241)
	java.lang.Thread.run (Thread.java:829)

Configuration:

{:deps true
 :dev-http {7778 ["classpath:public"]}
 :builds
 {:modules
  {:js-options {;; don't bundle any npm libs
                :js-provider :import}
   :compiler-options {:infer-externs :auto}
   :target :chrome-extension
   :output-dir "resources/public/js"
   :modules
   {:nrepl_extension {:init-fn nrepl-extension.core/init}
    }
   :build-hooks [(shadow.cljs.build-report/hook
                  {:output-to "report.html"})
                 ]}}}

uhm that looks like you took a :esm config and just changed :target

thats not how that works

https://github.com/thheller/shadow-cljs/issues/279

there are no docs but that issue has all the info you should need

there is also a sample manifest.edn it is looking for

> thats not how that works Oops sorry, I kind of relied on the spec checking that shadow-cljs does in various other places :)

btw :compiler-options {:infer-externs :auto} has been the default for quite some time now. you never need to set it.

also the build-report hook won't work either

that's all fine with me, I just started with an ESM build I already had

https://github.com/thheller/shadow-cljs/blob/051b5ecc7d701ef45b3bbc839685ac6ea03d4ad7/shadow-cljs.edn#L117-L125

https://github.com/thheller/shadow-cljs/tree/master/packages/chrome-ext

4 years ago .. so I don't expect chrome to still accept this at all

:)

thanks, I'll check it out

here seems to be a newer example: https://github.com/binaryage/chromex/blob/master/examples/shadow/shadow-cljs.edn

which is a sign that apparently it still worked in 2020 I mean :)

well the shadow-cljs side didn't change, so that'll work 😉

but I believe chrome has a new manifest version that is apparantly different but I didn't look at that at all yet

yes, they have v3 now :/

I'll try optimizations simple with esm first...

https://github.com/thheller/shadow-cljs/issues/902

since I already noticed some deprecation warnings with a v2 extension I wrote in JS once :(

I can live with no REPL to get this bootstrapped. I'm developing an nREPL server in the browser...

nrepl server in the browser?

yeah, it's an experiment for now

so I need to open a tcp port in the browser and the only way seems to make an extension

I just looked over some of the docs of the chrome extension stuff

:target :esm is absolutely the way to go now and is fully supported. just may need to set "type":"module" in some places apparently

the article you linked is from Dec 27, 2017 so not accurate anymore

it should also properly support modules loading other modules so all the extra hacks :chrome-extension did to sometimes create standalone files should not be needed anymore

just content-scripts still seem to be a bit more limited, although might just work too

tcp server support however seems to be deprecated and removed soon

@U05224H0W I will try to get back on the ESM track, but I haven't seen an up to date example with a service_worker .js script that directly works as an ES6 module. Have you?

"type": "module" isn't supported as part of the v3 manifest, it says unknown key

Ah:

"background": { "service_worker": "bg.js", "type": "module" },

Got a basic setup working now

They have a tcpserver example here: https://github.com/GoogleChrome/chrome-extensions-samples/tree/main/apps/samples/tcpserver

still manifest v2, so yes, this might soon disappear :/

https://developer.chrome.com/docs/extensions/reference/sockets_tcpServer/

> This API is part of the deprecated Chrome Apps platform. Learn more about migrating your app.

Yes, I've already abandoned the whole idea

Thanks

Yup. Looks like the case:

Chrome web store does not allow publish manifest v2 extension from early this year.

@U04V15CAJ How’s your progress on your chrome extension?

@UGC0NEP4Y I stepped away from that since extensions do not allow you to open TCP ports. I solved my problem in a different way that doesn't require an extension