Closed juhamust closed 9 years ago
Apparently, this happens now in node 0.10.x too, with npm version v2.11.3.
@juhamust I've updated some extensions and mozaik to 1.x, but not the aws one hasn't been updated, feel free to create an issue on the dedicated repo. I've also changed the way extensions are loaded, you no more have to pre-compile jsx/es6, you can directly publish src and the top app (demo or extension) will handle transformation via babel automatically (won't be the case for <1.0.0 packages). I also plan to make a table with all available extensions and their current version/build status to replace the simple list on the wiki.
@plouc I believe the issue is having only -beta
releases, it does not need to be >= 1.x per se.
yes, but I'd like to migrate to new structure, not remove the beta flag
It should be done soon
Ok, good.
I close this issue as this extension is now available in non-beta version, feel free to create one on dedicated repos.
@juhamust here is the list of existing extensions with latest npm package version info http://plouc.github.io/mozaik/extensions/
Good work :+1:
Seems that the behavior of NPM has changed: If the module that has no stable release (only ones with -beta flag in version name) available, exact version names are needed on installing:
This issue currently applies with all the mozaik extensions released by you, @plouc. I'd propose to make "stable" releases from each, as it prevents also
mozaik-demo
to install out of the box.