Update dependencies babel 7

[EECOLOR]

Also updated some other dependencies.

[klaasman]

Shouldn't this dependency be part of the library?
remove this depedency

[klaasman]

as discussed: let's test these changes (both development as deployment) with some real world codebases before merging

[klaasman]

Not sure if it should be part of this PR, but eslint needs some attention:

[klaasman]

Take a look at: https://babeljs.io/docs/en/babel-plugin-proposal-decorators#decoratorsbeforeexport

previously we had decorators before exports, but now it defaults to exports before decorators. Here's a discussion about this: tc39/proposal-decorators#69.

I don't have a strong opinion about the issue, but it would be an easier transition if we stick to the old way.

[EECOLOR]

The setting is set to classic right? As far as I can tell classic is 'before export' anyway.

[EECOLOR]

The setting is set to classic right? As far as I can tell classic is 'before export' anyway.

[klaasman]

There appear to be some changes regarding to css-modules values variables. Previously the @value syntax worked out of the box, but now it seems to be missing.

[klaasman]

Module not found: Error: Can't resolve '@babel/runtime/regenerator'

[EECOLOR]

There appear to be some changes regarding to css-modules values variables. Previously the @value syntax worked out of the box, but now it seems to be missing.

It should still work when I look at the source code: https://github.com/css-modules/css-modules-loader-core/blob/master/src/index.js

[EECOLOR]

I think the problem is caused by having both postcss 6 and 7...

Does the postcss nightmare ever stop?

[EECOLOR]

Ok, so the problem is nasty.

We waited quite some time for cssnano to move to postcss 6. When it did (as version 4 was released) they quite quickly moved to postcss 7. A lot of the 4.0 issues have been fixed later (4.1.x), part of the release that contained these fixes was the move to postcss 7.

Now postcss-modules or actually css-modules-loader-core (and it's dependencies) are still stuck on postcss 6. It seems however that this project is problematic: css-modules/css-modules-loader-core#174

Another one keeping postcss 6 is cssnext: Deprecating cssnext.

I am not seeing a clear way out. When I push away the depression that creeps up and look at the related community from a non-judging / observational standpoint it seems this is not the right technology to be using. I'm sure we are not alone in this struggle, but we should be looking for one of the following:

• An alternative
• Copy all related code we need into a repository and clean it up

[EECOLOR]

css-modules/css-modules#306
css-modules/css-modules-loader-core#231
css-modules/icss-utils#58
css-modules/postcss-modules-extract-imports#150
css-modules/postcss-icss-selectors#125
css-modules/postcss-icss-composes#169
css-modules/postcss-icss-values#113

[EECOLOR]

There is some movement on the css module issues

[klaasman]

I've been working on a higgins+kaliberjs project while depending on this branch without any issues 👍

[EECOLOR]

It seems there is a solution available for css modules. The webpack css loader plugin solves it by working around the postcss-modules plugin: https://github.com/webpack-contrib/css-loader/blob/master/src/index.js#L77

This should also simplify our css loader plugin.

[EECOLOR]

Support https://github.com/css-modules/postcss-modules-extract-imports is tricky, so we won't add it

[EECOLOR]

The problem of this branch is that it introduces 2 versions of the postcss library. I started working on a solution (going without the unsupported css modules plugin) in the eecolor-css-troubles branch. That work needs to be complete before we can merge it.

A shortterm alternative would be to update non-css related dependencies.

[EECOLOR]

Closed in favor of #159