Anatolii

Neat! I somehow missed this feature, which indeed allows to reconfigure app in a way that produces desired effect to build a webcomponent. At least it looks so from the...

Yep, that works. I will be working on that npm module, then.

I've pushed my first take on this plugin here: https://github.com/1602/create-elm-app-webcomponent-plugin I hope I get this idea of using plugin right, also looking for suggestion regarding naming of the plugin. Perhaps...

Sure, thanks for the naming suggestion. I've published `elm-app-webcomponent` [npm package](https://www.npmjs.com/package/elm-app-webcomponent), [gh repo](https://github.com/1602/elm-app-webcomponent).

Yep, that would simplify discovery of this solution for others. Thank you!

@akavel I run into the same issue while using create-elm-app, couldn't find an option other than ejecting and dealing with webpack. There are few things that required to package elm...

Due to [elm compiler bug](https://github.com/elm/compiler/issues/1763) I had to rename all my packages: `1602/json-value -> json-tools/json-value` `1602/json-schema -> json-tools/json-schema` `1602/elm-feather -> feathericons/elm-feather`

You can use non-evaluated code to write your controllers, it is not recommended to use eval-style. Here's where `action` defined: https://github.com/1602/kontroller/blob/master/lib/flow-control.js#L209

if you rename `some_controller.js` to `some.js` it should indeed turn off eval mode and you will need to rewrite your controller to not use `actionName(...`, and use `ControllerName.prototype.actionName = (c)...

Yes, probably.