mapseed/platform

Migrate build to node/npm

Closed this issue · 5 comments

  • Migrate from Bower to NPM for our dependencies

  • Migrate bundler from node script (or no bundler in dev) to webpack that can be used for both production and dev environments: #559

  • Migrate Sass/SCSS preprocessor using Ruby's compass gem into node via npm's libsass module: #529

zmbc commented

As far as I can tell, we do not currently use bower. I will work on this issue when I get a chance.

zmbc commented

The way our project is currently laid out, all models/views/everything are put into the S global. Our files are then cat-ed in a particular order, so that everything is preceded by its dependencies (except when those dependencies are only needed at runtime, which further complicates the ordering rules). When we replace this with webpack, we will instead have the entry point (app-view.js) require its dependencies, and they will require theirs in turn. I think this will completely obviate the S global, and we should just remove it.

Think about migrating the whole project to Angular2, using components will make everything easier for development and maintenance.
Here's a seed project in case we consider going this way: https://github.com/haoliangyu/angular2-leaflet-starter

zmbc commented
  • This issue is about our build process. Unrelated to Backbone vs. Angular. Using scss and having a bundler would still be necessary.
  • I'm all for drastic changes if we think they are warranted, but our front-end framework would be the last item on my list. Backbone is (still, after all these years) a solid option and I don't think it's giving us a lot of problems.

This was resolved in #604