Let's discuss where this project is headed and who can drive it
People
Repo info
Activity
Sean Anderson
@MeoMix
I agree I should I just have been doing non-software development things for a while (it's festival season) and I didn't want to essentially repeat Geelen by disappearing
but I've got the code open atm and going to try and get my boilerplate example up to date w/ latest jspm tonight
maybe shoot him a msg this week
λex Vincent
@alexisvincent
Awesome man :) that's great news :)
Sean Anderson
@MeoMix
:balloon:
λex Vincent
@alexisvincent
There are certain dependencies that it might be worth forking, just until they work again, for people trying to set this up for the first time.
This is (apparently) not the right way to express this
since that's for Browserify
and I was talking to Guy about how to do it properly but
I think his suggestion was to convert the whole thing to jspm
idk
λex Vincent
@alexisvincent
I think I got around this another way. But I can't remember. I think the only issue I had with cssnano was trying to load svgo
But that turned out to be because i wasn't serving dotfiles.
To get it to work for me I had to override the caniuse-API features file
And add some config for
Although this might have just been for cssnext
Sean Anderson
@MeoMix
I know what solution you're talking about
I tried out that one first
but
that's more of a bandaid
You don't even care about cssnext loading in development
λex Vincent
@alexisvincent
But in production we do
Don't want to just get rid of it
Sean Anderson
@MeoMix
err
what I mean is
cssnano has a dep on svgo. svgo was written with the intent of being ran in a node environment. serving dot files allows it to try and load in a browser environment, but really only because jspm has a naive implementation of fs (node-fs) and that only exists for the time being to help support browserify. Without node-fs, it'd error out when attempting to use the 'fs' object since that doesn't exist in the browser
cssnano is being loaded in development by jspm-loader-css
but
it isn't used in development at all
it's only ran when you try and make a bundle
so while trying to get it to load in development is noble it's really just a bandaid
the proper solution is to express to jspm that you only want it for production and not for development
and then it'll work fine b/c your production build is in node
λex Vincent
@alexisvincent
Oh I see, so you're saying to specify for instance in JSPM.browser.json the empty tag
Sean Anderson
@MeoMix
Yes, except the JSPM.browser field is intended for Browserify support and shouldn't be relied upon in 0.17+
The code I have should technically work, but there's a bug in Guy's code and he isn't keen on fixing it since it's an edge case for backwards compat
but I haven't figured out how to express it properly in 0.17 yet
Dimitri Rosenberg
@rosendi
Hi, guys! Can't figure out why it fails with:
Unable to dynamically transpile ES moduleas SystemJS.transpiler set tofalse.
Error loading http://0.0.0.0:7070/jspm_packages/npm/jspm-loader-css@1.1.0.js
Seems like it's trying to process it as JS.
MohannadKhasawneh
@MohannadKhasawneh
It is failing on my end as well for the same reason:
> Unable to dynamically transpile ES moduleas SystemJS.transpiler set tofalse.
> Error loading http://0.0.0.0:7070/jspm_packages/npm/jspm-loader-css@1.1.0.js