Sebastian Porto

Thanks for reporting this. I need to update the tutorial to latest version of Webpack. Will try to do it soon.

In https://www.elm-tutorial.org/en/06-fetching-resources/06-views.html the List.view function was changed to handle this. Did you maybe miss this step?

Probably, there was a good reason why I had to create a file for this at some point, but it looks like there is no need now. I will try...

Sounds good, I agree. Will try to put some work on this or add a good link if someone has already written a great explanation.

I am doing this manually e.g. ``` goweb.Map(goweb_http.MethodOptions, "/{*}", func(ctx context.Context) error { ctx.HttpResponseWriter().Header().Set("Access-Control-Allow-Origin", "http://localhost:9000") ctx.HttpResponseWriter().Header().Set("Access-Control-Allow-Methods", "GET, POST, PUT") ctx.HttpResponseWriter().Header().Set("Access-Control-Allow-Headers", "origin, x-requested-with, accept") return nil }) ``` But I wonder...

It would be nice to have a simple catch all method like: ``` goweb.AllowCORSFor(whitelistedDomains, options) ``` don't really know what kind of options would you pass, I haven't done too...

Sorry, closed this by mistake, when trying to comment. Looking at the documentation MapBefore could be more flexible, or it could be some special handler you pass to Map: ```...

I would like to, if I can find the spare time to have a go I will do it. Thanks

@jvoigtlaender the reactor server might be running in port 8000 as set by --port, but the JS might be running in a different port entirely when embedded in another application....

We upgraded to Webpack 5 and this works fine provided that you have `--watch`. In version 6 of this plugin somehow the flag `--watch` was not necessary.