I don't seem to be getting any errors, but the values just aren't getting set during runtime

side-note: the actual ports example fails either way (with or without set!) -- the error there is that it can't seem to map over [{,,,}]

first of all. why is this a def with an anonymous function? makes its terribly hard to read.

(Container. stack "nginxContainer" {:port [{:internal 80 :external 8000}]) I assume Container is some JS Object and you are passing a CLJS map as an argument which it very likely won't understand

use (Container. stack "nginxContainer" (clj->js {:port [{:internal 80 :external 8000}]))

the last commented out set! has the same issue. trying to pass a CLJS map to any JS object will either fail directly or fail silently since they all expect plain JS objects

you can also construct JS objects directly via #js {:foo "bar"}

@U05224H0W: thanks! clj-js worked! #js {,,, did not

ah, if I'm doing #js, I gotta apply it more liberally:

(Container. stack "nginxContainer" #js {:image (.-latest image)
                                              :name "tutorial"
                                              :ports #js [#js {:internal 80
                                                               :external 8000}]})

😆 this should address your first-of-all:

(defn my-stack [app name]
  (let [stack (TerraformStack. app name)
        image (Image. stack "nginxImage" #js {:name "nginx:latest"
                                              :keepLocally false})]
    (DockerProvider. stack "default")
    (Container. stack "nginxContainer" (clj->js {:image (.-latest image)
                                                 :name "tutorial"
                                                 :ports [{:internal 80
                                                          :external 8000}]}))))

thank you again for your help!

yeah #js doesn't apply to nested values so clj->js is better for more complex structures where you don't care about performance

This is how my shadow-cljs.edn file looks like:

{:source-paths ["src/background"
                "src/popup"
                "src/content-script"]

#_#_ :dependencies [[binaryage/chromex "RELEASE"]
                [binaryage/devtools "RELEASE"]]
 
 :builds {:extension

          {:target           :chrome-extension
           :extension-dir    "resources/unpacked"
           :manifest-file    "resources/unpacked/manifest.edn"
           :compiler-options {; 
                              :closure-output-charset "US-ASCII"
                              ; we need to fully inline source maps to avoid devtools security restrictions of loading .map
                              ; files via chrome-extension://<extension-id>/out/cljs-runtime/goog.debug.error.js.map urls
                              :source-map-inline      true}
           :outputs          {:background     {:output-type :chrome/background
                                               :entries     [chromex-sample.background]}
                              :content-script {:output-type    :chrome/content-script
                                               :chrome/options {:matches [""]
                                                                :run-at  "document_end"}
                                               :entries        [chromex-sample.content-script]}
                              :popup          {:output-type :chrome/shared
                                               :entries     [chromex-sample.popup]}}}}}

This is how my manifest.edn file looks like:

{:name             "Test chrome extension"
 :version          "1.0"
 :description      "Test chrome extension"
 :manifest-version 2

 :permissions      ["http://*/*"
                    "https://*/*"]

 :browser-action   {:default-title "Show the popup"
                    :default-icon  "images/icon48.png"
                    :default-popup "popup.html"}

 :content-security-policy
                   ["default-src 'self';"
                    ;; FIXME: unsafe-eval should be injected for dev, user shouldn't have to write this
                    "script-src 'self' 'unsafe-eval' ;"
                    "connect-src * data: blob: filesystem:;"
                    "style-src 'self' data: chrome-extension-resource: 'unsafe-inline';"
                    "img-src 'self' data: chrome-extension-resource:;"
                    ;; FIXME: localhost only? don't want to allow any origin though
                    "frame-src 'self' :* data: chrome-extension-resource:;"
                    "font-src 'self' data: chrome-extension-resource:;"
                    "media-src * data: blob: filesystem:;"]}

shadow-cljs connects to the websocket and if I eval a println in the content_script.cljs I can see it in the console

Using this shadow-cljs connects to the websocket in localhost, but I get the websocket error in google classroom

This is the localhost console:

This is google classroom console:

And this is the shadow-cljs.edn file:

{:source-paths ["src/background"
                "src/popup"
                "src/content-script"]

 #_#_:dependencies [[binaryage/chromex "RELEASE"]
                    [binaryage/devtools "RELEASE"]]

 :builds {:extension

          {:target           :chrome-extension
           :extension-dir    "resources/unpacked"
           :manifest-file    "resources/unpacked/manifest.edn"
           :compiler-options {:closure-output-charset "US-ASCII"
                              :source-map-inline      true}
           :outputs          {:background     {:output-type :chrome/background
                                               :entries     [chromex-sample.background]}
                              :content-script {:output-type    :chrome/content-script
                                               :chrome/options {:matches ["" ""]
                                                                :run-at  "document_end"}
                                               :entries        [chromex-sample.content-script]}
                              :popup          {:output-type :chrome/shared
                                               :entries     [chromex-sample.popup]}}}}}

try ":*/*" instead of ""

not a clue really. been a while since I looked at any of this. maybe chrome got stricter security restrictions these days

do you still have some csp rules in your HTML maybe?

I'm using brave browser I don't know if that's a problem

might be. not a clue, never used it.

As far as I know brave uses the same extensions as chrome.

I will download chrome and try there.

more likely that something in your config doesn't quite match

what about your html?

is there any?

the only html is the popup, just a hello world 😛

ok, does that have some csp rules?

<meta name="Content-Security-Policy" ...>

nope

then I'm out of ideas

okay, no problem! Thanks a lot 🙂 I'll try a bit more and if I fail I'll just use javascript and suffer 😛

well the websocket is only used for hot-reload and REPL. if you don't care about those then you can just set :devtools {:enabled false} and it won't try to connect

good to know , maybe Ill do that

@U05224H0W I've noticed that I'm having this problem with https sites

hmm yeah that might be a reason. might need to setup ssl for shadow-cljs so is all ssl