awkward / ember-pods Goto Github PK

grunt server should be emberpods server or even emberpods s etc.

Instead, it should 1) create a package.json with the information you give to the CLI or 2) append the needed scripts to package.json

Especially when you use a /

Ok. The reason I went for stylus is because its node based compile step whereas sass is relying on Ruby for its compile step. The downside of Stylus is that it isn't as popular as Sass.

We might want to checkout libsass + grunt-sass and node-sass. What are the advantages? Speed wise? Are these projects well maintained?

Add grunt task like grunt build:production that generates the production ready version of the project.

• include ember.prod.js instead of ember.js
• minify, concat (gzip) project

Include something like https://github.com/chriso/cli to make the CLI part of ember-pods smoother

When adding a pod, add the route automatically to the router.coffee file.

We should find a way to read and parse coffee files and dynamically add routes to it.

We should have an option to enable source maps

We should use more of the native callback methods of Ember.DefaultResolver instead of implementing our own

Please 'xplain to me what this is.

• Error on missing hyphen (-) in component name
• more?

We should use a different way of executing code on init.
see:
http://reefpoints.dockyard.com/2014/04/28/dont-override-init.html

just call super in init, if that works

Split up the grunt file in various parts to have a more readable build setup