Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cant get it to work on Raspberry Pi 2 #81

Open
Horkyze opened this issue Mar 14, 2016 · 2 comments
Open

Cant get it to work on Raspberry Pi 2 #81

Horkyze opened this issue Mar 14, 2016 · 2 comments

Comments

@Horkyze
Copy link

Horkyze commented Mar 14, 2016

I installed npm without problem.

After running npm install and npm run webpack I get the following error:
The node_modules dir was empty.

ERROR in ./~/css-loader!./~/less-loader!./src/browser/components/main.less Module build failed: ReferenceError: Promise is not defined at LazyResult.async (/home/pi/Apps/fb-sleep-stats/node_modules/postcss/lib/lazy-result.js:157:31) at LazyResult.then (/home/pi/Apps/fb-sleep-stats/node_modules/postcss/lib/lazy-result.js:79:21) at processCss (/home/pi/Apps/fb-sleep-stats/node_modules/css-loader/lib/processCss.js:198:5) at Object.module.exports (/home/pi/Apps/fb-sleep-stats/node_modules/css-loader/lib/loader.js:24:2) @ ./src/browser/components/main.less 4:14-127

Here is the full console log:
http://pastebin.com/raw/pSFg4fMv

I decided to ignore the error and run scrape anyway, but all I got was:
Polling every 600 seconds Tue Mar 15 2016 00:08:06 GMT+0100 (CET) - Active users: 63 / 258 Tue Mar 15 2016 00:08:06 GMT+0100 (CET) An error occured while scraping. Please check to make sure your development.json config is correct [ReferenceError: Promise is not defined]

This is my development.json (not real values ofc..)
{ "fbCookie": { "c_user": "2431254960", "xs": "539%3A2b6ALG3g4H1nWQ%3A2%3A1657993299%3A1012" }, "pollingInterval": 600, "appId": 534315541561821, "server": { "port": 3000 } }

BTW I am running pi-hole to block ads, hope that wont be an issue.

@sorenlouv
Copy link
Owner

This seems to be a duplicate of #75. Updating Node to the latest version should fix it.

@aleknak
Copy link

aleknak commented Jul 28, 2016

take a look at #98

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants