version 0.10.10 (promise-friendly)

[Bruno Jouhier]

I just published it.

The big novelty is promise support. See https://github.com/Sage/streamlinejs#interoperability-with-promises

I added fibers and galaxy as optional dependencies in package.json, to get the right versions of these libraries. They may fail to install and you may get a scary output in npm install (galaxy requires node >= 0.11.10 and fibers does not compile with node 0.11.13 so there is a very small window that's ok for both) but this should not prevent the install from succeeding. If you don't want the scary output, you can install with npm --no-optional and install fibers and galaxy separately, according to your needs.

Also, this should only be transient and I hope that fibers will install ok once 0.12 comes out. If you are into bleeding edge stuff, I have put a quick and dirty fix for fibers + node 0.11.13 in https://github.com/bjouhier/node-fibers/commit/4bd02761d90d93599bea773e79d99a343534461e.

Bruno

[Bruno Jouhier]

I had messed up the dependency on galaxy. So I tried to unpublish and republish quickly with the fix but NPM failed during unpublish and I was stuck (could not unpublish nor publish again).

So I've just published 0.10.11 with the right dependency on galaxy.

0.10.10 is in limbo.
0.10.11 is the right one.

Bruno

[Aseem Kishore]

This is great stuff Bruno, thank you!

Quick q: if you precompile ._js or ._coffee to regular .js, do you still enable promise support by compiling with the --promise option? The use case here is publishing a library to npm as regular JS. Callers should be able to get back promises from this library.

Aseem

--
You received this message because you are subscribed to the Google Groups "streamline.js" group.
To unsubscribe from this group and stop receiving emails from it, send an email to streamlinejs...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Bruno Jouhier]

On Monday, May 12, 2014 2:43:11 PM UTC+1, Aseem Kishore wrote:

This is great stuff Bruno, thank you!

Quick q: if you precompile ._js or ._coffee to regular .js, do you still enable promise support by compiling with the --promise option? The use case here is publishing a library to npm as regular JS. Callers should be able to get back promises from this library.

Yes, it should work and I think that the recommendation should be to compile published libraries with --promise.

The only drawback is that people who consume the library from streamline won't get the diagnostics about missing underscores. But during dev they can work from the original streamline source or they can recompile with a different option.

Bruno

Aseem

On Wed, May 7, 2014 at 8:05 PM, Bruno Jouhier <bjou...@gmail.com> wrote:

I had messed up the dependency on galaxy. So I tried to unpublish and republish quickly with the fix but NPM failed during unpublish and I was stuck (could not unpublish nor publish again).

So I've just published 0.10.11 with the right dependency on galaxy.

0.10.10 is in limbo.
0.10.11 is the right one.

Bruno

On Thursday, May 8, 2014 1:08:32 AM UTC+2, Bruno Jouhier wrote:

I just published it.

The big novelty is promise support. See https://github.com/Sage/streamlinejs#interoperability-with-promises

I added fibers and galaxy as optional dependencies in package.json, to get the right versions of these libraries. They may fail to install and you may get a scary output in npm install (galaxy requires node >= 0.11.10 and fibers does not compile with node 0.11.13 so there is a very small window that's ok for both) but this should not prevent the install from succeeding. If you don't want the scary output, you can install with npm --no-optional and install fibers and galaxy separately, according to your needs.

Also, this should only be transient and I hope that fibers will install ok once 0.12 comes out. If you are into bleeding edge stuff, I have put a quick and dirty fix for fibers + node 0.11.13 in https://github.com/bjouhier/node-fibers/commit/4bd02761d90d93599bea773e79d99a343534461e.

Bruno

--
You received this message because you are subscribed to the Google Groups "streamline.js" group.

To unsubscribe from this group and stop receiving emails from it, send an email to streamlinejs+unsubscribe@googlegroups.com.