(How To) Use the globalize-compiler in build process?

[sunsande]

Here I would like to address the following problem:
if one wants to use the globalize-compiler during the build process of a web project there are no the configuration files for that.
Specifically I am building in .Net in Azure. So I would expect to be able to download the latest package.json, containing only the dependencies needed the globalize-compiler to run - currently these are:
cldr-data
globalize
iana-tz-data
and globalize-compiler itself.
Of course this could change in the future. Thus I expect to get the package.json automatically from the actual repository instead of doing it by myself every time (or at least check if it is actual or leave it as is until the build will break missing some new dependency).

Further one would like to get all of the needed files (globalize-runtime.xxx) ready for copy in the output directory. It is just not nice to go and search in node_modules/globalize/dist.... and look for them ... one can also automatically detect which one are needed. So if for example we do not need globalize-runtime/currency.js it would be automatically not present in the output dir.

And last but not the least: why does the output from the compiler not working with the globalize.js files but needs another globalize-runtime.js files?

Best regards,
Alex

[rxaviers]

So I would expect to be able to download the latest package.json, containing only the dependencies needed the globalize-compiler to run - currently these are:
cldr-data
globalize
iana-tz-data
and globalize-compiler itself.

Yeap, we need to copy peerDependencies into dependencies.

It is just not nice to go and search in node_modules/globalize/dist.... and look for them ... one can also automatically detect which one are needed. So if for example we do not need globalize-runtime/currency.js it would be automatically not present in the output dir.

It would be better if we had an npm package for each module, and probably use https://www.npmjs.com/package/lerna for that. That means a breaking change and therefore a major bump in the library. I'm open for that, PRs welcome. Ref globalizejs/globalize#467

[klihelp]

@rxaviers Any progress on lerna implementation?