You and Scott created the AngularClass together, correct?
I Like listening to Scott as well. I have Sooo many questions about workflows and strategies.. I have built the first gen SPA for my teams Line-Of-Business app using Angular 1.4, ES6, Traceur, gulp... Now the rest of the company want's to follow suit and build apps for their LOB's. I put my investigation into webpack on hold until the first release was done, and now I am investigating how I can convert what I have to a better system. I started looking towards JSPM/SystemJS/SystemJS-Bundler, but that did not work out too well as discussed above. I am switching to Webpack, have your starter working with LESS, will be looking into how I can get the config.json file compiled on the fly.
When I have it all down I will be introducing it to the other teams. I want to invite you guys to come up and teach your class, but that won't be afore 3-6 months from now (or so I hear).
The config.json file contains all the RESTful service urls used by the application, they change depending on runtime (dev/staging/production).
@kburson the website is largely outdated so it’s best to email us directly for training
Then I have the static assets (fonts, images, mock json data) that I currently copy to a build folder where all the compiled assets go.
I am looking to configure webpack to handle more of this in place and have gulp do less work...
I like your 'yeoman'-like generator in your starters. Very clever.
are you saying have webpack build your static assets rather than a gulp task to copy it?
ok. I will collate a concise list and post it to an issue on the starter repo, although I am focusing on angular 1.x, because this will be the limitations of the other teams (while I can use A2, they must support IE8, I will have to investigate what the technical requirements are for them to use isomorphic rendering alongside their PHP services that can work around the various CORS issues).
Thank you for your time.
@kburson I’m working on having the repo both in both frameworks or at least make it easier for migration. So if all else fails I can update the angular 1 repo from your list
Where would I define my services in the NG6-Starter filetree?
Components might want to share services so I don't think you would want to define it on a per component basis
The general pattern I have seen is to have a "common" folder for shared services, directives and filters.
For non code assets like fonts and images I have seen some use an "assets" folder, others use a "public" folder. Following the WebPack model, where should these be stored relative to the code, index.html and the compiled bundle.js?
In the common folder I created directives, filters and services folders, each one with a module and then the common module
@kburson thank you! I'll try that and see how it works out :)
Also, JSPM is SUCH a nice tool for downloading and managing dependencies, it is a shame we cannot use it with webpack, or am I wrong with that assumption. I hate having to bounce between bower and npm (not everything I need is on npm), and JSPM has a nice ability to organize and manage.
BTW: I have forked the NG6-starter and am pushing my changes up to my fork and I progress thru my experiments on getting my desired workflow up and running.
you can think of webpack as unglifyjs so they should be able to work together
that would be cool... need to learn the proper incanctations :wink:
has anybody tried to access the $rootScope from app.js ?
nvm I found it :D
hi guys, where are you putting your images?
Given the layout from the repo, I'd recommend making an images/ directory inside of client/app
cc @nimamehanian what do you think of the error above?
I changed the gulpfile.babel.js file es5
var gulp = require('gulp'); var webpack = require( 'webpack-stream'); var path = require( 'path'); var sync = require( 'run-sequence'); var serve = require( 'browser-sync'); var rename = require( 'gulp-rename'); var template = require( 'gulp-template'); var fs = require( 'fs'); var yargs = require( 'yargs'); var lodash = require( 'lodash');