Error: Cannot find module '../../third-party/specifications' about spark-server

[jlkalberer]

So, you'll need to delete npm_modules or just npm_modules/spark-protocol and npm install

That will run the postinstall script to fetch this file.

[jlkalberer]

@crenwick - I added in the ability for the server to automatically flash system updates if your device needs an update. This feature automatically downloads the necessary firmware updates from the spark-firmware releases during the post-install step.

The new issue you are seeing is coming from another feature I added. You can use the particle CLI or the particle IDE to flash source directly to your device. In order to do so, you need to clone the https://github.com/spark/firmware repository somewhere on your machine. It will use this repo to compile you application (FIRMWARE_REPOSITORY_DIRECTORY).

Anyways, I'm going to write a readme on this that explains how to set the feature up.

[pintaric]

I should mention that I ran this on OSX using node v7.4.0 / npm v3.10.8.

[crenwick]

Same problem on node v6.9.4 / npm v4.1.1

[jlkalberer]

Looks like particle-cli just updated their code. We have a fix but are investigating long-term fixes.

[jlkalberer]

Yeah, `node_modules`. The only thing I can think of is that `spark-protocol` is being cached for some reason. You can check the package and make sure this change is there - https://github.com/Brewskey/spark-protocol/pull/47/files

…

On Tue, Jan 24, 2017 at 8:48 AM Charles Renwick ***@***.***> wrote: You mean node_modules ? I've deleted that several times to rerun a fresh npm install, with no luck. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#98 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABDlxPyCa4lGTgrlZCVw34yC5ZnPngZQks5rVitPgaJpZM4LsWVy> .

[jlkalberer]

@crenwick @pintaric - is this issue solved for you two?

[crenwick]

I think so. Getting a few different errors on other tests, but several are now passing.

[jlkalberer]

Hmm.. the tests should all be passing. Can you let us know which ones are failing for you? A gist of the output would be good enough.

[pintaric]

It's now working for me, thanks for the quick response! :)

[crenwick]

Sure! https://gist.github.com/crenwick/282644be38fae360526757760a3a8922

This is with a fresh install of the npm modules.

[jlkalberer]

Ahh... ok, I have an idea of what's going on.

Did you change the path for the FIRMWARE_REPOSITORY_DIRECTORY ?

Can you let me know what the path is for spark-server on your local machine?

[jlkalberer]

Sorry that you're the guinea pig.. We haven't tested on OSX or Linux and that's a brand new feature that's failing.

[pintaric]

I forgot to mention that I manually created the src/data directory and edited src/settings.js (to point FIRMWARE_REPOSITORY_DIRECTORY to the correct path on my machine) in order to get the server to run on OSX.

(Otherwise, I would get the same errors as described in https://gist.github.com/crenwick/282644be38fae360526757760a3a8922).

[jlkalberer]

@pintaric - are things working for you then? You just needed to manually create src/data?

[crenwick]

Oh interesting. Maybe I'm misunderstanding the scope of this project. I didn't know it was so coupled with firmware.

Is there a specific firmware repo that this requires? I pointed the FIRMWARE_REPOSITORY_DIRECTORY to my custom firmware repo, but its content is very different than what this project assumes (no /user/applications dir).

[pintaric]

As far as I know, the official device firmware repo is located at https://github.com/spark/firmware.

Also, from what I learned so far, the term "firmware" is used quite ambiguously for both "device firmware" and "user firmware".

[jlkalberer]

@pintaric - I'm talking about the local install path. That's how you get cloud compile working.

[crenwick]

Sounds great, @jlkalberer

Love the project.

[pintaric]

@jlkalberer - Thanks! Haven't gotten to that step yet, but I'll let you know if I run into any issues on OSX/Linux. Eventually, I'd like to run your spark-server fork in a Docker Container, so maybe that's something I can contribute in the future.

[jlkalberer]

@pintaric - pull latest and you shouldn't see any issues with running for the first time.

A docker container would be nice. I actually don't see there being any issues running it there.