Christophe Rosset

A solution (from this [twitter thread](https://twitter.com/revolunet/status/1031586841965879296)) might be to: * in local: * dont run frontend dev env in a docker container (use installed nodejs on the developer's computer) *...

The following resource may be useful as an intermediary step : https://nickjanetakis.com/blog/docker-tip-75-how-to-avoid-node-modules-in-your-volume-mounts

I've been told about this solution. You're right @pierreyves-lebrun , this might be the first one true elegant way to solve that problem in a long time. cc @warpdesign

Found the workaround : This problem is due to one of the vscode updates in the last weeks. It upgraded `vscode-stylelint` from `v0.x` to `v1.x`, which contains a breaking change...

> > Found the workaround : > > This problem is due to one of the vscode updates in the last weeks. It upgraded `vscode-stylelint` from `v0.x` to `v1.x`, which...

Here is a project boilerplate : https://github.com/topheman/vanilla-es6-jspm Regarding `karma-jspm`, you'll have the following features: - overriding your jspm configuration (to use stubs and mocks while testing) - using html fixtures...

I would really like this feature 👍

I tried to use esm with jest as a loader. I had the following problems, maybe it will help for the next steps. You can find a minimal reproducible case...

Hello @sepiropht Je viens de voir ta proposition de talk. Il y a un meetup spécial WebAssembly à la fin du mois, le mercredi 26 juin : https://www.meetup.com/fr-FR/Paris-js/events/260336640/ J'avais prévu...

An option would be to tag the current version of the project as `v1.0.0` and restart it from scratch using https://github.com/AngularClass/angular2-webpack-starter as boilerplate, adding the feature that were demonstrating reactive...