search

blitzcodes / slipstream-prj

A light weight interface for Meteor development; a handy and organized way to ride the slipstream of the great and evolving Meteor framework. My mission with this project is to address a few key concerns with developing a solid production ready system for Meteor.
MIT License
1 stars 0 forks source link

app crashing #2

Open orefalo opened 11 years ago

orefalo commented 11 years ago

not sure if it's ready to try but i get this

=> Meteor server restarted TypeError: Cannot set property 'id' of undefined at .extend (app/packages/underscore/underscore.js:771:21) at Array.forEach (native) at .each..forEach (app/packages/underscore/underscore.js:78:11) at Function..extend (app/packages/underscore/underscore.js:768:5) at new Slipstream.List (app/packages/slipstream/lib/Slipstream.List.js:11:32) at Object.Slipstream.Drift (app/packages/slipstream/lib/Slipstream.Drift.js:6:14) at app/lib/collections/Project.js:3:22 at /Users/orefalo/GitRepositories/slipstream-prj/.meteor/local/build/server/server.js:298:12 at Array.forEach (native) at Function..each._.forEach (/Users/orefalo/.meteorite/meteors/meteor/meteor/9bb2b5447e845c4f483df5e9b42a2c1de5ab909b/dev_bundle/lib/node_modules/underscore/underscore.js:78:11) => Exited with code: 1 => Your application is crashing. Waiting for file change.

blitzcodes commented 11 years ago

Sorry, the recent changes this week have broken the sample. I am considering taking the meteor TODO sample app (from http://todomvc.com/) or one of the default meteor examples to showcase the slipstream objects. I made a big break thought in how to abstract and manipulate the templates yesterday, and once the other elements are flushed hopefully over this next week, I'll be able to start working on the new sample beginning next weekend. :+1:

blitzcodes commented 11 years ago

Hi Oliver, I've been plugging away and flushing out the meteor package I'm building, getting closer to having it ready for use. Made a lot of improvements at how it will handle it's functionality by default, and how easily it can be overridden as needed.

I've decided on 3 various projects that I'm going to convert into using slipstream, and I'll be updating this git actively now as I set them up one by one. This has already risen some intricacies with running the actual mrt package vs. the local version which I've touched up, and I will continue to resolve glitches or restricted areas in the interface as I progress. Hopefully in the next week or two I'll be able to lock these all down. Once they're good, I can flush out all the wiki documentation on the package finally, and give an overview of how slipstream handles things in these samples vs the original.

This time around, I've made sure you can already jump into each sample project subfolder and run it's meteor instance without it failing so far! Because I'm not always working in the same spot, for now they may break at times as I'm pushing new code until I'm able to test it on my home setup, but I'll try and keep it working as much as possible between commits.

Cheers, Sean

orefalo commented 11 years ago

hi sean,

flying from france to the us today, will give it a try when i can get internet off my laptop

quick question, have you considered typescript?

Sent from my iPhone

On Jul 24, 2013, at 6:51 AM, blitzcodes notifications@github.com wrote:

Hi Oliver, I've been plugging away and flushing out the meteor package I'm building, getting closer to having it ready for use. Made a lot of improvements at how it will handle it's functionality by default, and how easily it can be overridden as needed.

I've decided on 3 various projects that I'm going to convert into using slipstream, and I'll be updating this git actively now as I set them up one by one. This has already risen some intricacies with running the actual mrt package vs. the local version which I've touched up, and I will continue to resolve glitches or restrict areas of the interface as I progress. Hoping in the next week or two I'll be able to lock these all down. Once they're good, I can flush out all the wiki documentation, and give an overview of how slipstream handles things in the samples vs the original.

This time around, I've made sure you can already jump into each sample project subfolder and run it's meteor instance without it failing so far! Because I'm not always working in the same spot, for now they may break at times as I'm pushing new code until I'm able to test it on my home setup, but I'll try and keep it working as much as possible between commits.

Cheers, Sean

— Reply to this email directly or view it on GitHub.