max-mapper / max-mapper/adventure-time

Trying to set up locally

Open
#10 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
97
Forks
16
PR merge metrics
No merged PRs in 30d

Description

I have tried to set up using the following instructions:

I have also installed the https://github.com/mafintosh/docker-adventure-time docker image.

In order to run I am using the following commands:

  • Start docker-browser-server: node ./bin.js mafintosh/docker-adventure-time --port 8080 (I had to update some NPM packages to get it node-gyp to compile).
  • Start adventure-time: npm run start.

I have the following adventure-time config:

adventureTime({
  guide: "http://maxogden.github.io/get-dat/guide",
  server: "localhost:8080",
  id: Math.random().toString(36).slice(2)
})

If I navigate to http://localhost:8080 docker-browser-server works fine.
If I navigate to http://localhost:9966 adventure-time serves up but I get no output in the console window.

I am receiving the following error when adventure-time is starting the server:

Error: ENOENT: no such file or directory, open '/vagrant/hatchway/node_modules/edit/node_modules/codemirror/lib/codemirror.css' while parsing file: /vagrant/hatchway/node_modules/edit/index.js

Which is odd because I have double checked and the file is there...? But I can not see how this would effect the console anyway as codemirror is only used for the editor.

@maxogden & @mafintosh I know you guys haven't worked on either of these projects in awhile but I thought I would tag you in just in case you have some insight sorry if this bothers you! :L

BTW the tech you guys have put together is pretty amazing, couldn't believe it when I actually ran a terminal emulator in my browser :)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing npm run start with the reported adventure-time configuration and the docker-browser-server command. Inspect the failure at node_modules/edit/index.js and the referenced node_modules/edit/node_modules/codemirror/lib/codemirror.css, then verify the browser-server and adventure-time interaction. Done means the server starts without the ENOENT error and produces the expected console output at localhost:9966.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, javascript, nodejs
Domain
developer-experience, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.