Topic Suggestion:
We should update our QUnit tests on the generators and demos to use the documented 2.0 style syntax rather than the deprecated now undocumented style.
There is even a tool to help migrate automatically
Or, maybe we should consider switching to something like Mocha, Jest, or Jasmine
my thoughts about the naming of the ecosystem are:
we have a can core bundle with all the core modules and it version number depends on the feature or bugfixes on this core bundle.
we have a can ecosystem bundle that contains all the ecosystem modules. there version numbers depends on the features on the modules of the ecosystem.
if can ecosystem bundle changes the version number, it not changes the can core bundle.
otherwise if can core bundle major version changed, the can ecosystem also changed. e.g. can core 4.0 changes can ecosystem to can ecosystem 4.0
General problem: support all the combos of module formats, syntax, test library, etc.
Some discussion around creating generators versus transpilers:
– Make fewer transpilers that handle each conversion individually, e.g. one for QUnit to Mocha, CommonJS to ES6, etc.
– Make generators for each combination, e.g. a QUnit to Mocha CommonJS generator, QUnit to Mocha ES6 generator, etc.
Pro of transpilers: need to make fewer of them, can chain to support more combinations (e.g. QUnit to Mocha and Mocha to Jasmine transpilers make writing a QUnit to Jasmine transpiler unnecessary)
Pro of generators: generally easier to write and encourage forking for specific needs