Closed andersosthus closed 7 years ago
Yeah, there's no start
at the root. Better update those docs a notch.
Which OS are you running? I have to patch NODE_PATH
at those sites so that could be it. It's most likely failing to look up the package from the sibling directory. We may have to change the patching mechanism.
Hi,
I forgot to mention OS in my original post. I've done these tests in Bash on Windows. Basically it's Ubuntu 14.04 binaries. I've successfully ran other node projects in this environment before.
Ok, I have a rough fix in mind. I'll try to patch that in later today. 👍
Here we go. Try this:
npm run build
(now that I think of it, I think this was the missing step earlier, npm run init
builds the project initially now)npm start
(runs the smoketest)npm run site
should run the site (styling in progress).
There's also npm run watch
. It should pick up changes made to the source, run tests, and generate code. It's not particularly fast, but it should work.
I've revamped the project a lot. Please give it a go again and re-open if this is still relevant. Thanks. 👍
Hi,
I'm trying out the steps listed in Contributing.md, but I'm unable to get it to work.
After cloning the repo I ran
npm run init
. This completed fine. I then triednpm start
. This doesn't work in the root folder, sincepackage.json
doesn't specify a start script.I then navigate to
./site
and runnpm run start
. Here I get the following error:So basically it looks like it doesn't search for imports properly in
../packages
since, if I'm not mistaken, therequire('antwar')
statement inbootstrap.js
should be using that one?The same issue in
smoketest
as well.Am I doing something wrong here or ?