refactor(All): move build to rollup, update core deps

[bigopon]

Follow up the release of [email protected] & [email protected], we can register global resources with direct view model references. Now ux elements as a single bundle file, like following pic

The entry configure will look like this:

import {
  FrameworkConfiguration,
  bindingMode,
} from 'aurelia-framework';

import { ValueAttributeObserver, EventSubscriber } from 'aurelia-binding';

import { AureliaUX } from '@aurelia-ux/core';
import { UxSelect } from './ux-select';
import { UxOptGroup } from './ux-optgroup';
import { UxOption } from './ux-option';

export { UxOption, UxOptionElement } from './ux-option';
export { UxOptGroup, UxOptGroupElement } from './ux-optgroup';
export { UxSelect, UxSelectElement } from './ux-select';
export { UxSelectTheme } from './ux-select-theme';

export function configure(config: FrameworkConfiguration) {
  config.container.get(AureliaUX).registerUxElementConfig(uxSelectConfig);
  config.globalResources([
    UxSelect,
    UxOptGroup,
    UxOption,
  ]);
}

const uxSelectConfig = {
  tagName: 'ux-select',
  properties: {
    value: {
      defaultBindingMode: bindingMode.twoWay,
      getObserver(element: Element, _: string) {
        return new ValueAttributeObserver(element, 'value', new EventSubscriber(['change']));
      }
    }
  }
};

This can be applied for all elements, which should help reduce build time too.

@EisenbergEffect @ZHollingshead I not sure how to update jspm dependencies properly.

resolves #162

TODO list:

• Button c4a8297
• Card 9c20ebf
• Checkbox 3f3ae9a
• ChipInput ff825f8
• Components
• Core c114d78
• Datepicker e2273a4
• Form 6adda49
• Grid b4c8bb4
• Icons Renamed to Icon 9352545
• Input 12b61a6
• Input-info ce0d803
• List 31ebac0
• Radio 62f9215
• Select b8ccff4
• Switch 6025ed0
• Textarea a41573f

[serifine]

This looks great to me!

[bigopon]

@ZHollingshead Sorry Didn't state clearly WIP, I'm not sure if I should move wholesale to rollup, or one or few first and the rest later.

[bigopon]

@ZHollingshead @EisenbergEffect It would be also nice if we don't have to duplicate css files for each dist format, instead copy all css into a folder name css

[serifine]

@bigopon Oh, whoops. Yeah I will get in and start testing.

I would be okay with doing it all at once if it works.

On the folder structure, originally you proposed an idea where we had the dist folder look like the following:

css/
types/
amd-index.js
commonjs-index.js
es2015-index.js
native-modules.js

If we do that, then we can just put the folders in the root one time yeah? What is required for that to work though, is that a situation where we need to configure loaders specially?

To be honest I am not sure how to update JSPM dependencies either. I am most experienced with Webpack at this point.

[serifine]

Just doing this to clear my approval.

[bigopon]

we have an options to set dist folder of format or similarly named folder, maybe @jods4 can comment on how to have it work with webpack, without having to nested inside a folder.

[EisenbergEffect]

I'd love to see this converted all at once, if possible :)

[bigopon]

@EisenbergEffect @ZHollingshead That's pretty much it for the base work. Needs to update Webpack for html import in test, beside css test for all loaders to see if any issues.

[serifine]

Wouldn't we want the casing to be UxButtonView instead of UX_BUTTON_VIEW to be consistent?

[bigopon]

I was not sure about this, so I named it like a constant. Wouldn't be an issue if you want to proceed.

[serifine]

So I am not sure how I feel about the style injection happening in the index page. This feels like it would be a better fit in the components view-model, either in a custom decorator or just in the constructor.

The ideal scenario would have been figuring out why the require tag is not working in Webpack when using rollup to move everything into a single file.

[bigopon]

We can copy the .css files over to dist to have it dynamically bundled. It will work fine, we just need to adjust the test to have those css file properly mapped

[bigopon]

close as no longer relevant, resolved by #229