[CommonJS] Packages/1.0 engines issue

[Kris Kowal]

I don't suppose it's too late to change the "engine" (as specified) or
"engines" property (as in the example) to an "engines" property that
maps engine names to versions, just like dependencies? 1.0.1
timeline?

Kris Kowal

--
You received this message because you are subscribed to the Google Groups "CommonJS" group.
To post to this group, send email to comm...@googlegroups.com.
To unsubscribe from this group, send email to commonjs+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/commonjs?hl=en.

[Christoph Dorn]

Kris Kowal wrote:
> I don't suppose it's too late to change the "engine" (as specified) or
> "engines" property (as in the example) to an "engines" property that
> maps engine names to versions, just like dependencies? 1.0.1
> timeline?

No problem here.

Christoph

[Wes Garland]

Kris:

Not a bad idea. I've already bumped into this locally, albeit only for native modules.

Do the other engines also support the concept of *javascript* version?  I can see that being useful too.

Wes

--
Wesley W. Garland
Director, Product Development
PageMail, Inc.
+1 613 542 2787 x 102