These are chat archives for systemjs/systemjs

28th
Jan 2016
Dean Sofer
@ProLoser
Jan 28 2016 00:00
i feel iffy about everybody clinging to event streams and observables like it's god's gift, they've been around forever and i have found just as many architectural scaling problems with them as you do anything else
Debjit Biswas
@debjitbis08
Jan 28 2016 08:24
Is it possible to transpile only some of the ES6 features by blacklisting features in babel config?
Guy Bedford
@guybedford
Jan 28 2016 08:27
@debjitbis08 yes certainly, which features are you looking to blacklist?
Debjit Biswas
@debjitbis08
Jan 28 2016 09:54
@guybedford I want to blacklist arrow functions.
I went through the issue list for jspm and it seems and jspm 0.17 support this. I am currently using 0.16.
Guy Bedford
@guybedford
Jan 28 2016 10:21
@debjitbis08 no the blacklist was exactly right - System.config({ babelOptions: { blacklist: ['es6.arrowFunctions'] } }) I believe
jspm 0.17 doesn't actually offer this feature
(currently)
Chris Smola
@Smolations
Jan 28 2016 21:28

i feel like this problem has an easy solution, but i haven't found it yet: how do i load up the minified versions of dependencies instead of the unminified? for instance, if my package.json dependencies include "angular": "github:angular/bower-angular@1.4.7", is there some way to make the "angular" alias and anything that depends on it load the minified file? i can alias it my config map:

  map: {
    "angular": "github:angular/bower-angular@1.4.7/angular.min",

but there are other libs which depend on it, so those trigger a load of the full library, leaving me with both minified/unminified versions.. =[

do i really have to comb through my config for all references to that lib and add /angular.min to get it to work? it would be really neat if i could just use the "angular" alias to reference those dependencies....then i'd only have to change the reference in a single place...
orrrrr is this a job for overrides?
Chris Smola
@Smolations
Jan 28 2016 21:48
so i verified that adding /angular.min to all references to that library works. however, i would want to use minified versions for many of the third party libs i'm using. it would be quite disappointing if i had to go through and specify minified versions for all the libs i wanted... =[
Chris Smola
@Smolations
Jan 28 2016 22:31
still here and stumped if anyone has a clue ^^^^
Peter Uithoven
@peteruithoven
Jan 28 2016 22:57
@Smolations why load minified versions?
isn't this something for a final bundle step? not for during development?
if you want it minified during development you can pretty easilly make a (minified) bundle of all you dependencies
Chris Smola
@Smolations
Jan 28 2016 23:12
working on a team and we're transitioning from requirejs and pure amd while also revving up a bunch of new features. the upgrade path has to be nimble and come in small chunks at a time. so at this point we are switching to jspm, followed soon after by a bunch of file/directory restructuring, followed soon after by converting everything to es6 and establishing a final build process. so we currently aren't able to put the time in to implement bundling seeing as we are fairly new to jspm to begin with. =]
and small update to my previous post, adding the minified file on the end of each module in the map breaks the jspm install process because there are styles references from some of those libraries elsewhere in the app.
Peter Uithoven
@peteruithoven
Jan 28 2016 23:21
I understand the need to take small steps, but creating a dependencies bundle is probably much much easier than what you're doing right now.
If you have all your js in a js folder you can run:
jspm bundle 'js/**/* - [js/**/*] bundle.js --inject
The inject step makes sure systemjs will automatically get the bundled modules.
Each developer can do this when he wants and he'll just notice a quicker load time.
You just need to run it again when you change your dependencies.
Chris Smola
@Smolations
Jan 28 2016 23:49
well one of the prereqs is that it doesn't interrupt or complicate current flows for anyone in the near term. we're trying to fix the architecture because, right now, the list of dependencies is really long. we're loading up angular services, directives, plugins, etc. all before the app bootstraps. that means we'd have to run a watcher during development, which none of us currently do. while that isn't horrible, we would then need to write the gulp tasks to do the watching so that the build file is recompiled any time one of those files changes.
i am the only one working on this project, and i had to fight for the very little time i have in order to get something in before the next big feature comes rolling down my way.
ceo's and board member needs can cause serious detriment to a product's quality. ;]
but i don't understand why that isn't an option anyway. why force devs to use unminified versions of a library when a project could have 30+ 3rd party libs/dependencies that the dev will probably never have a need to debug directly?
i don't need the unminified angular code for debugging. it works fine. it's usually our code that does the breaking. lol
Peter Uithoven
@peteruithoven
Jan 28 2016 23:53
I think I understand, but again, you don't really need a watcher, since you're only bundling the dependencies (the ones in jspm_packages).
but then again, maybe there are other solutions, I'm just sharing what is working with our project.