{"action":"created","issue":{"url":"https://api.github.com/repos/ipselon/structor/issues/35","repository_url":"https://api.github.com/repos/ipselon/structor","labels_url":"https://api.github.com/repos/ipselon/structor/issues/35/labels{/name}","comments_url":"https://api.github.com/repos/ipselon/structor/issues/35/comments","events_url":"https://api.github.com/repos/ipselon/structor/issues/35/events","html_url":"https://github.com/ipselon/structor/issues/35","id":125004920,"number":35,"title":"Use of Structor for real project on Mac OSX","user":{"login":"radman-x","id":9258904,"avatar_url":"https://avatars.githubusercontent.com/u/9258904?v=3","gravatar_id":"","url":"https://api.github.com/users/radman-x","html_url":"https://github.com/radman-x","followers_url":"https://api.github.com/users/radman-x/followers","following_url":"https://api.github.com/users/radman-x/following{/other_user}","gists_url":"https://api.github.com/users/radman-x/gists{/gist_id}","starred_url":"https://api.github.com/users/radman-x/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/radman-x/subscriptions","organizations_url":"https://api.github.com/users/radman-x/orgs","repos_url":"https://api.github.com/users/radman-x/repos","events_url":"https://api.github.com/users/radman-x/events{/privacy}","received_events_url":"https://api.github.com/users/radman-x/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":11,"created_at":"2016-01-05T16:49:29Z","updated_at":"2016-02-04T18:01:58Z","closed_at":null,"body":"We have been researching Structor and trying to use it but are having numerous problems. The concept is very good but the tool is still too immature and buggy to use for real work. Here are some of our results and problems.\r\n\r\nWe are running on Mac OSX, 10.8.5 (Mountain Lion).\r\nInitially, we started with:\r\n     Structor v0.2.2\r\n     node: v4.2.2 (LTS)\r\nWe were able to install and use this version of Structor somewhat. There were several errors but we were able to compose components and completed part 1 of the tutorial (https://www.youtube.com/watch?v=AY65e6Ry_rY). We were able to create custom components and partially complete part 2 of the tutorial fairly well (had a few errors but generally it seemed to work).\r\n\r\nNext, we upgraded to the following in an attempt to fix some of the errors above:\r\n    node: v5.3.0 (Stable)\r\n    Structor: v0.2.6\r\nWe first uninstalled the old Structor (v0.2.2) and then did:\r\n    sudo npm install Structor -g\r\nDuring the installation, we got numerous warnings:\r\ngyp WARN EACCES user \"root\" does not have permission to access the dev dir \"/Users/user_name/.node-gyp/5.3.0\"\r\ngyp WARN EACCES attempting to reinstall using temporary dev dir \"/usr/local/lib/node_modules/structor/node_modules/bufferutil/.node-gyp\"\r\nAnd errors such as:\r\nnpm ERR! Darwin 12.5.0\r\nnpm ERR! argv \"/usr/local/bin/node\" \"/usr/local/bin/npm\" \"install\" \"structor\" \"-g\"\r\nnpm ERR! node v5.3.0\r\nnpm ERR! npm  v3.3.12\r\nnpm ERR! code ECONNRESET\r\nnpm ERR! errno ECONNRESET\r\nnpm ERR! syscall read\r\nnpm ERR! network read ECONNRESET\r\nnpm ERR! network This is most likely not a problem with npm itself\r\nnpm ERR! network and is related to network connectivity.\r\nnpm ERR! network In most cases you are behind a proxy or have bad network settings.\r\nnpm ERR! network \r\nnpm ERR! network If you are behind a proxy, please make sure that the\r\nnpm ERR! network 'proxy' config is set properly.  See: 'npm help config'\r\nIt seems like some type of permissions problem or network error but we could not find anything obvious.\r\n\r\nWe then tried using Structor and could get to the point of starting a clone of Bootstrap pre-pack but then it just hung with the following error in console:\r\nPOST http://localhost:2222/invoke net::ERR_EMPTY_RESPONSE(anonymous function) @ main.js:28(anonymous function) @ main.js:26(anonymous function) @ main.js:26c.default.value @ main.js:66l.default.value @ main.js:66r @ main.js:9i @ main.js:9s @ main.js:9c @ main.js:9f @ main.js:9n @ main.js:9m.processEventQueue @ main.js:9r @ main.js:9a.handleTopLevel @ main.js:9i @ main.js:25a @ main.js:25o.perform @ main.js:23d.batchedUpdates @ main.js:24a @ main.js:23g.dispatchEvent @ main.js:25\r\n2016-01-05 10:15:02.570 main.js:8 Uncaught (in promise) Error: Minified exception occurred; use the non-minified dev environment for the full error message and additional helpful warnings.(…)\r\nAgain, this seems like some type of network error.\r\n\r\nDo you know what could be causing these errors and what the fix would be? If there is any other information you would like (npm-debug.log?), please let me know.\r\n\r\nWe would like to use this promising tool (and, possibly, provide some patronage if it can be used on our projects) but until these bugs are fixed, we must stop our research on it."},"comment":{"url":"https://api.github.com/repos/ipselon/structor/issues/comments/179969682","html_url":"https://github.com/ipselon/structor/issues/35#issuecomment-179969682","issue_url":"https://api.github.com/repos/ipselon/structor/issues/35","id":179969682,"user":{"login":"radman-x","id":9258904,"avatar_url":"https://avatars.githubusercontent.com/u/9258904?v=3","gravatar_id":"","url":"https://api.github.com/users/radman-x","html_url":"https://github.com/radman-x","followers_url":"https://api.github.com/users/radman-x/followers","following_url":"https://api.github.com/users/radman-x/following{/other_user}","gists_url":"https://api.github.com/users/radman-x/gists{/gist_id}","starred_url":"https://api.github.com/users/radman-x/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/radman-x/subscriptions","organizations_url":"https://api.github.com/users/radman-x/orgs","repos_url":"https://api.github.com/users/radman-x/repos","events_url":"https://api.github.com/users/radman-x/events{/privacy}","received_events_url":"https://api.github.com/users/radman-x/received_events","type":"User","site_admin":false},"created_at":"2016-02-04T18:01:58Z","updated_at":"2016-02-04T18:01:58Z","body":"Thanx @Bartekus for this suggestion. We fixed those permissions and now have installed the latest Structor without using sudo."}}