building a bootstrap build:

[:doc-bootstrap] Build failure:
FileNotFoundException: ...project/js/compiled/bootstrap/js/cljs.core.js.map (No such file or directory)
	java.io.FileOutputStream.open0 (FileOutputStream.java:-2)
	java.io.FileOutputStream.open (FileOutputStream.java:270)
	java.io.FileOutputStream.<init> (FileOutputStream.java:213)
	 (io.clj:230)
	 (io.clj:230)

same last night.. almost forgot it

@mhuebert oops, fixed in [email protected]

I refactored the shadow-cljs code related to interop with the closure compiler a bit today

that means it is now more flexible when it comes to choosing which :js-provider to use

the goal is to use Closure for all projects .js sources while using :shadow for node_modules

so everything in the project runs through :advanced. I think that should be ok given that you control the .js and could fix :advanced issues if required

so far it is looking promising

I wanted to do this for a while but https://groups.google.com/d/msg/clojurescript/PTWne6hLAxI/UXgMDCNuDAAJ prompted me to work on it

is anyone here jumping through hoops to work with ES6+ code you wrote yourself? ie. not on npm?

basic gist is that

src/integrated/core.cljs

(ns integrated.core
  "Start here."
  (:require ["./lib" :as lib]))

(defn init! []
  (lib/debugMessage "Narf"))

src/integrated/lib.js

var debugMessage = (x = "any old string") => {
  console.log(`Printing ${x} from cljs!`);
};

export { debugMessage };

now works, the lib.js can even use any cljs code via import

or going a bit more extreme

import core from "goog:cljs.core";

import { createElement } from "react";

import { bar } from "./more-es6";

var foo = (x = "any old string") => {
  console.log(`Printing ${x} from cljs!`);
  console.log(core.assoc(null, 1, 2));
  console.log(createElement("h1", null, x));
  return bar(x);
};

export { foo };

full JS interop one step closer

on the surface it works just like before so hopefully it doesn’t break anything

would anyone here object to this new default behaviour? ie. running YOUR es6 code through :advanced?

only issue is that @dnolen said CLJS is never going to support relative requires, so no support for (:require ["./lib" :as lib]) in core 😞

I like the new automatic HTTP server options for the different builds

new options?