librelist archives

« back to archive

Getting started with proton

Getting started with proton

From:
Michael Mathews
Date:
2011-04-29 @ 10:45
So none of the examples on the README page to run as they are written. 
This is not a good way to introduce yourself, proton.

-- 
Michael Mathews

Re: Getting started with proton

From:
Michael Mathews
Date:
2011-04-29 @ 11:51
Shouldn't the example just work as long as I followed all the steps? I'm 
ready to chuck trying to use proton now. Any ideas?

# ./bin/proton --webapp server.js 

node.js:134
throw e; // process.nextTick error, or 'error' event on first tick
^
Error: Cannot find module 'jsgi/jsgi-node'
at Function._resolveFilename (module.js:320:11)
at Function._load (module.js:266:25)
at require (module.js:348:19)
at Object.<anonymous> 
(/var/www/node/hydrogen/node_modules/proton/lib/proton.js:2:16)
at Module._compile (module.js:404:26)
at Object..js (module.js:410:10)
at Module.load (module.js:336:31)
at Function._load (module.js:297:12)
at require (module.js:348:19)
at Object.<anonymous> (/var/www/node/hydrogen/node_modules/proton/lib/cli.js:2:15)


-- 
Michael Mathews
On Friday, 29 April 2011 at 11:45, Michael Mathews wrote: 
> So none of the examples on the README page to run as they are written. 
This is not a good way to introduce yourself, proton.
> 
> -- 
> Michael Mathews
> 

Re: [nug] Re: Getting started with proton

From:
Tom Yandell
Date:
2011-04-30 @ 00:03
Yes, sorry this is fixed but not released. The npm api changed so that you
have to call the module jsgi/lib/jsgi-node rather than jsgi/jsgi-node. If
you clone proton (and others) and then run "npm link" inside the cloned dirs
it should work. Will try to get changes into npm tomorrow, but might end up
being Sunday.

Tom

On 29 April 2011 12:51, Michael Mathews <micmath@gmail.com> wrote:

>  Shouldn't the example just work as long as I followed all the steps? I'm
> ready to chuck trying to use proton now. Any ideas?
>
> # ./bin/proton --webapp server.js
>
> node.js:134
>         throw e; // process.nextTick error, or 'error' event on first tick
>         ^
> Error: Cannot find module 'jsgi/jsgi-node'
>     at Function._resolveFilename (module.js:320:11)
>     at Function._load (module.js:266:25)
>     at require (module.js:348:19)
>     at Object.<anonymous>
> (/var/www/node/hydrogen/node_modules/proton/lib/proton.js:2:16)
>     at Module._compile (module.js:404:26)
>     at Object..js (module.js:410:10)
>     at Module.load (module.js:336:31)
>     at Function._load (module.js:297:12)
>     at require (module.js:348:19)
>     at Object.<anonymous>
> (/var/www/node/hydrogen/node_modules/proton/lib/cli.js:2:15)
>
>
> --
> Michael Mathews
>
> On Friday, 29 April 2011 at 11:45, Michael Mathews wrote:
>
>  So none of the examples on the README page to run as they are written.
> This is not a good way to introduce yourself, proton.
>
> --
> Michael Mathews
>
>
>

Re: [nug] Re: Getting started with proton

From:
Michael Mathews
Date:
2011-04-30 @ 07:33
Ultimately I'd like to just be able to just run `npm install proton` and 
then follow a simple "hello world" tutorial that works?

-- 
Michael Mathews
On Saturday, 30 April 2011 at 01:03, Tom Yandell wrote: 
> Yes, sorry this is fixed but not released. The npm api changed so that 
you have to call the module jsgi/lib/jsgi-node rather than jsgi/jsgi-node.
If you clone proton (and others) and then run "npm link" inside the cloned
dirs it should work. Will try to get changes into npm tomorrow, but might 
end up being Sunday.
> 
> Tom
> 
> On 29 April 2011 12:51, Michael Mathews <micmath@gmail.com> wrote:
> > Shouldn't the example just work as long as I followed all the steps? 
I'm ready to chuck trying to use proton now. Any ideas?
> > 
> > # ./bin/proton --webapp server.js 
> > 
> > node.js:134
> > throw e; // process.nextTick error, or 'error' event on first tick
> > ^
> > Error: Cannot find module 'jsgi/jsgi-node'
> > at Function._resolveFilename (module.js:320:11)
> > at Function._load (module.js:266:25)
> > at require (module.js:348:19)
> > at Object.<anonymous> 
(/var/www/node/hydrogen/node_modules/proton/lib/proton.js:2:16)
> > at Module._compile (module.js:404:26)
> > at Object..js (module.js:410:10)
> > at Module.load (module.js:336:31)
> > at Function._load (module.js:297:12)
> > at require (module.js:348:19)
> > at Object.<anonymous> 
(/var/www/node/hydrogen/node_modules/proton/lib/cli.js:2:15)
> > 
> > 
> > -- 
> > Michael Mathews
> > On Friday, 29 April 2011 at 11:45, Michael Mathews wrote:
> > > So none of the examples on the README page to run as they are 
written. This is not a good way to introduce yourself, proton.
> > > 
> > > -- 
> > > Michael Mathews
> > > 
> > 
> 

Re: [nug] Re: Getting started with proton

From:
Tom Yandell
Date:
2011-04-30 @ 07:50
That'll be the case when I push out my latest changes. Think I might have
time now...

Tom

On 30 April 2011 08:33, Michael Mathews <micmath@gmail.com> wrote:

>  Ultimately I'd like to just be able to just run `npm install proton` and
> then follow a simple "hello world" tutorial that works?
>
> --
> Michael Mathews
>
> On Saturday, 30 April 2011 at 01:03, Tom Yandell wrote:
>
> Yes, sorry this is fixed but not released. The npm api changed so that you
> have to call the module jsgi/lib/jsgi-node rather than jsgi/jsgi-node. If
> you clone proton (and others) and then run "npm link" inside the cloned dirs
> it should work. Will try to get changes into npm tomorrow, but might end up
> being Sunday.
>
> Tom
>
> On 29 April 2011 12:51, Michael Mathews <micmath@gmail.com> wrote:
>
>  Shouldn't the example just work as long as I followed all the steps? I'm
> ready to chuck trying to use proton now. Any ideas?
>
> # ./bin/proton --webapp server.js
>
> node.js:134
>         throw e; // process.nextTick error, or 'error' event on first tick
>         ^
> Error: Cannot find module 'jsgi/jsgi-node'
>     at Function._resolveFilename (module.js:320:11)
>     at Function._load (module.js:266:25)
>     at require (module.js:348:19)
>     at Object.<anonymous>
> (/var/www/node/hydrogen/node_modules/proton/lib/proton.js:2:16)
>     at Module._compile (module.js:404:26)
>     at Object..js (module.js:410:10)
>     at Module.load (module.js:336:31)
>     at Function._load (module.js:297:12)
>     at require (module.js:348:19)
>     at Object.<anonymous>
> (/var/www/node/hydrogen/node_modules/proton/lib/cli.js:2:15)
>
>
> --
> Michael Mathews
>
> On Friday, 29 April 2011 at 11:45, Michael Mathews wrote:
>
>  So none of the examples on the README page to run as they are written.
> This is not a good way to introduce yourself, proton.
>
> --
> Michael Mathews
>
>
>
>
>

Re: [nug] Re: Getting started with proton

From:
Tom Yandell
Date:
2011-04-30 @ 07:57
Proton 0.2.0 is now on npm, will do others shortly. Got to love the npm
publish process (think somebody wrote a good blog post about it). Publish
process was:

update package.json version number and commit
git tag v0.2.0
git push --tags
npm publish https://github.com/tomyan/proton.js/tarball/v0.2.0

Is really simple, on to micro.js...

On 30 April 2011 08:50, Tom Yandell <tom@yandell.me.uk> wrote:

> That'll be the case when I push out my latest changes. Think I might have
> time now...
>
> Tom
>
>
> On 30 April 2011 08:33, Michael Mathews <micmath@gmail.com> wrote:
>
>>  Ultimately I'd like to just be able to just run `npm install proton` and
>> then follow a simple "hello world" tutorial that works?
>>
>> --
>> Michael Mathews
>>
>> On Saturday, 30 April 2011 at 01:03, Tom Yandell wrote:
>>
>> Yes, sorry this is fixed but not released. The npm api changed so that you
>> have to call the module jsgi/lib/jsgi-node rather than jsgi/jsgi-node. If
>> you clone proton (and others) and then run "npm link" inside the cloned dirs
>> it should work. Will try to get changes into npm tomorrow, but might end up
>> being Sunday.
>>
>> Tom
>>
>> On 29 April 2011 12:51, Michael Mathews <micmath@gmail.com> wrote:
>>
>>  Shouldn't the example just work as long as I followed all the steps? I'm
>> ready to chuck trying to use proton now. Any ideas?
>>
>> # ./bin/proton --webapp server.js
>>
>> node.js:134
>>         throw e; // process.nextTick error, or 'error' event on first tick
>>         ^
>> Error: Cannot find module 'jsgi/jsgi-node'
>>     at Function._resolveFilename (module.js:320:11)
>>     at Function._load (module.js:266:25)
>>     at require (module.js:348:19)
>>     at Object.<anonymous>
>> (/var/www/node/hydrogen/node_modules/proton/lib/proton.js:2:16)
>>     at Module._compile (module.js:404:26)
>>     at Object..js (module.js:410:10)
>>     at Module.load (module.js:336:31)
>>     at Function._load (module.js:297:12)
>>     at require (module.js:348:19)
>>     at Object.<anonymous>
>> (/var/www/node/hydrogen/node_modules/proton/lib/cli.js:2:15)
>>
>>
>> --
>> Michael Mathews
>>
>> On Friday, 29 April 2011 at 11:45, Michael Mathews wrote:
>>
>>  So none of the examples on the README page to run as they are written.
>> This is not a good way to introduce yourself, proton.
>>
>> --
>> Michael Mathews
>>
>>
>>
>>
>>
>

Re: [nug] Re: Getting started with proton

From:
Tom Yandell
Date:
2011-04-30 @ 08:02
Okay, micro and spectrum also done. Let me know if anything else doesn't
work as advertised.

Tom

On 30 April 2011 08:57, Tom Yandell <tom@yandell.me.uk> wrote:

> Proton 0.2.0 is now on npm, will do others shortly. Got to love the npm
> publish process (think somebody wrote a good blog post about it). Publish
> process was:
>
> update package.json version number and commit
> git tag v0.2.0
> git push --tags
> npm publish https://github.com/tomyan/proton.js/tarball/v0.2.0
>
> Is really simple, on to micro.js...
>
>
> On 30 April 2011 08:50, Tom Yandell <tom@yandell.me.uk> wrote:
>
>> That'll be the case when I push out my latest changes. Think I might have
>> time now...
>>
>> Tom
>>
>>
>> On 30 April 2011 08:33, Michael Mathews <micmath@gmail.com> wrote:
>>
>>>  Ultimately I'd like to just be able to just run `npm install proton`
>>> and then follow a simple "hello world" tutorial that works?
>>>
>>> --
>>> Michael Mathews
>>>
>>> On Saturday, 30 April 2011 at 01:03, Tom Yandell wrote:
>>>
>>> Yes, sorry this is fixed but not released. The npm api changed so that
>>> you have to call the module jsgi/lib/jsgi-node rather than jsgi/jsgi-node.
>>> If you clone proton (and others) and then run "npm link" inside the cloned
>>> dirs it should work. Will try to get changes into npm tomorrow, but might
>>> end up being Sunday.
>>>
>>> Tom
>>>
>>> On 29 April 2011 12:51, Michael Mathews <micmath@gmail.com> wrote:
>>>
>>>  Shouldn't the example just work as long as I followed all the steps?
>>> I'm ready to chuck trying to use proton now. Any ideas?
>>>
>>> # ./bin/proton --webapp server.js
>>>
>>> node.js:134
>>>         throw e; // process.nextTick error, or 'error' event on first
>>> tick
>>>         ^
>>> Error: Cannot find module 'jsgi/jsgi-node'
>>>     at Function._resolveFilename (module.js:320:11)
>>>     at Function._load (module.js:266:25)
>>>     at require (module.js:348:19)
>>>     at Object.<anonymous>
>>> (/var/www/node/hydrogen/node_modules/proton/lib/proton.js:2:16)
>>>     at Module._compile (module.js:404:26)
>>>     at Object..js (module.js:410:10)
>>>     at Module.load (module.js:336:31)
>>>     at Function._load (module.js:297:12)
>>>     at require (module.js:348:19)
>>>     at Object.<anonymous>
>>> (/var/www/node/hydrogen/node_modules/proton/lib/cli.js:2:15)
>>>
>>>
>>> --
>>> Michael Mathews
>>>
>>> On Friday, 29 April 2011 at 11:45, Michael Mathews wrote:
>>>
>>>  So none of the examples on the README page to run as they are written.
>>> This is not a good way to introduce yourself, proton.
>>>
>>> --
>>> Michael Mathews
>>>
>>>
>>>
>>>
>>>
>>
>

Re: [nug] Re: Getting started with proton

From:
Michael Mathews
Date:
2011-04-30 @ 07:57
I have no idea what the software would do, but I already have two ace 
names for the framework I would build on top of Proton: HydrogenJS or 
Deuterium. I think I'm better at names than code.

-- 
Michael Mathews
On Saturday, 30 April 2011 at 08:50, Tom Yandell wrote: 
> That'll be the case when I push out my latest changes. Think I might 
have time now...
> 
> Tom
> 
> On 30 April 2011 08:33, Michael Mathews <micmath@gmail.com> wrote:
> > Ultimately I'd like to just be able to just run `npm install proton` 
and then follow a simple "hello world" tutorial that works?
> > 
> > -- 
> > Michael Mathews
> > On Saturday, 30 April 2011 at 01:03, Tom Yandell wrote:
> > > Yes, sorry this is fixed but not released. The npm api changed so 
that you have to call the module jsgi/lib/jsgi-node rather than 
jsgi/jsgi-node. If you clone proton (and others) and then run "npm link" 
inside the cloned dirs it should work. Will try to get changes into npm 
tomorrow, but might end up being Sunday.
> > > 
> > > Tom
> > > 
> > > On 29 April 2011 12:51, Michael Mathews <micmath@gmail.com> wrote:
> > > > Shouldn't the example just work as long as I followed all the 
steps? I'm ready to chuck trying to use proton now. Any ideas?
> > > > 
> > > > # ./bin/proton --webapp server.js 
> > > > 
> > > > node.js:134
> > > > throw e; // process.nextTick error, or 'error' event on first tick
> > > > ^
> > > > Error: Cannot find module 'jsgi/jsgi-node'
> > > > at Function._resolveFilename (module.js:320:11)
> > > > at Function._load (module.js:266:25)
> > > > at require (module.js:348:19)
> > > > at Object.<anonymous> 
(/var/www/node/hydrogen/node_modules/proton/lib/proton.js:2:16)
> > > > at Module._compile (module.js:404:26)
> > > > at Object..js (module.js:410:10)
> > > > at Module.load (module.js:336:31)
> > > > at Function._load (module.js:297:12)
> > > > at require (module.js:348:19)
> > > > at Object.<anonymous> 
(/var/www/node/hydrogen/node_modules/proton/lib/cli.js:2:15)
> > > > 
> > > > 
> > > > -- 
> > > > Michael Mathews
> > > > On Friday, 29 April 2011 at 11:45, Michael Mathews wrote:
> > > > > So none of the examples on the README page to run as they are 
written. This is not a good way to introduce yourself, proton.
> > > > > 
> > > > > -- 
> > > > > Michael Mathews
> > > > > 
> > > > 
> > > 
> > 
>