@mfikes I think you mean cljs.core.PersistentQueue.EMPTY in https://dev.clojure.org/jira/browse/CLJS-2916

Yep. Fixed.

Do we have any precedent for describing / communicating changes in default configuration? For :npm-deps I have added a note in the draft compiler option reference: https://github.com/clojure/clojurescript-site/blob/7a90a7a434f04ef0e29858fbc692f0fd7ba0593a/content/reference/compiler-options.adoc#npm-deps

(I'm thinking about the case where someone upgrades to the next release, only to find their build failing if it relied on the previous default of {}. The solution is to explicitly configure :npm-deps.)

@mfikes not other than communicating via the announcement

Cool. I’ll add a bit to the news.

What magic do I use to partition this (js/Buffer. #js [0x01 0x02 0x02 0x04])

partition?

Yeah into blocks. Like partition-all

I'm trying to chunk a image into packets to be sent over the wire

I can't figure out how to get the data into a native cljs seq for the life of me.

hrm not sure why you would want to partition Buffer instead of just sending it

Because Mqtt has a Max message size

right but Node.js has stuff for partitioning / slicing buffers

no need to introduce indirection here

Are you referring to the .slice function on Buffer? Or is there a partition somewhere that I'm missing.

I guess slice, shouldn’t that suffice?

It should, I was hoping to avoid some edge cases.

My implementation has been buggy.

And clojure core has all these amazing collection functions

Ty for the pointer I appreciate you guys hanging around a public forum.

I’ve updated the release notes to incorporate a bit about the new :npm-deps default. https://github.com/clojure/clojurescript-site/blob/5ebb74576f5471552c52245c65847763bf55a201/content/news/2018-09-01-release.adoc#noteworthy-changes