composes using absolute paths via webpack context doesn't resolve

[besh]

Hey there. So, what I think that I'm observing is that when I use this plugin, I get module build errors because

.class {
  composes: someclass from shared_styles/colors.css;` 
}

now resolves to

.class {
  composes: someclass from '/user/path/stuff/project/client/components/SomeComponent/SomeComponent/shared_styles/colors.css.';
}

Prior to using this plugin, composes was properly using the context key in webpack and resolving paths as

.class {
  composes: someclass from '/user/path/stuff/project/client/shared_styles/colors.css';
}

I believe I am setting everything correctly with the plugin. Doing some light logging within the plugin's index.js file, it is traversing and finding the correct js files that are attempting to use the styleName attribute.

Here is my webpack config for js stuff (shortened for brevity).

const APP_DIR  = path.resolve(__dirname, '../client');
{
  context: APP_DIR
  module: {
    rules: [
      {
        test: /\.js$/,
        include: APP_DIR,
        exclude: /node_modules/,
        use: [{
          loader: 'react-hot-loader/webpack'
        },{
          loader: 'babel-loader',
          options: {
            babelrc: false,
            presets: [
              ['es2015', { 'modules': false }],
              'stage-0',
              'react'
            ],
            plugins: [
              [
                'react-intl', {
                  messagesDir: './i18n/messages',
                  enforceDescriptions: true
                }
              ],[
                'react-css-modules', {
                  context: APP_DIR
                }
              ]
            ]
          }
        }]
      }
    ]
  }
}

I am not aliasing anything in webpack and composes is resolving from the context key without including this plugin. Any guidance here would be appreciated. I'll keep digging too.

Not sure if this is somewhat related to #25?

[besh]

@gajus any guidance on this one? Sorry if I'm missing something really dumb. With your recent article here, I'm even more excited to try this plugin out.

[SirbyAlive]

I've been stuck on the same problem.
On fetch in requireCssModule, the path resolve is used, totally outside of the babel resolver, so no configuration can actually affect how the path is resolved and it is always either resolved relatively from the file or absolutely.

[gajus]

Probably duplicate of:

• Adding "composes" doesn't update className #48 or
• composes .. from ... statements no longer work #22