Re: [racket-users] Trying out a Racket-powered Webpack alternative

Disregard last message. Looks like I have results now. ~slg ‐‐‐ Original Message ‐‐‐ On Sunday, August 25, 2019 9:34 AM, Sage Gerard wrote: > I'd be thrilled to include those libsass bindings as an opt-in feature! > Starred and watched. > > Follow-up troubleshooting question: > > http

Re: [racket-users] Trying out a Racket-powered Webpack alternative

I'd be thrilled to include those libsass bindings as an opt-in feature! Starred and watched. Follow-up troubleshooting question: https://pkgd.racket-lang.org/pkgn/package/unlike-assets https://pkgd.racket-lang.org/pkgn/package/polyglot My package listings are still not built. I read https://pk

Re: [racket-users] Trying out a Racket-powered Webpack alternative

Sage Gerard writes: > - unlike-assets: A build tool for interdependent assets. Similar to Webpack, > if you are familiar with the JS ecosystem. Cool stuff! I was very close to building an asset pipeline for koyo[1] a couple months ago, but I settled on just using broccoli.js instead. I'm glad t

[racket-users] Trying out a Racket-powered Webpack alternative

Hi Racket, I'm excited to show off two new packages if you'll indulge me: - unlike-assets: A build tool for interdependent assets. Similar to Webpack, if you are familiar with the JS ecosystem. - polyglot: A specific configuration of `unlike-assets` that builds static websites using any #lang a