Configure lookup paths for composes/from

[dfreeman]

I'm still wrapping my head around the standard patterns for how PostCSS plugins consume configuration, but it doesn't look like there's currently a way to pass configuration through to postcss-import to configure the root and search path(s) for composes foo from 'bar' lookups.

Is this something that it would make sense to add, or am I missing something fundamental? I'm also happy to put together a PR if you have a form factor in mind for how you might want to consume such configuration.

[madyankin]

Hi, thank you for the feedback. You have to use paths relative to the root path right now, but I'm going to fix that soon.

[madyankin]

@hellosmithy, @dfreeman Fixed, the new version is published

[ghost]

I am having s similar issue on version 0.4.0 (latest today on npm):

{ [Error: ENOENT: no such file or directory, open '/Users/tarikansari/Workspace/sane-web/src/components/GenrePicker/theme/elements/button-dark']
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/Users/tarikansari/Workspace/sane-web/src/components/GenrePicker/theme/elements/button-dark' }

It is looking for the file next to the path of the file that includes the composes, instead of using the path option configured on postcss-import. I don't have this issue when using webpack/css-loader?modules as it used the resolves/root option of webpack to look into the correct paths for files.

How are we supposed to pass the include path to postcss-modules?

[madyankin]

@tarikihm thank you for the feedback! Could you make a minimal reproduceable example, please?

[ghost]

May not have time to write one until a couple days, for now here is more information: this is related to css-modules-loader-core which uses require.resolve() to resolve import

The way other tools handle this: css-loader instead uses the context of Webpack, and postcss-import accept a path option, which is probably the approach postcss-modules should take.

A quick hacky workaround for me was to add a symlink named theme pointing to src/theme into node_modules, however that is not all, postcss-modules then fails to resolves composes which omit the .css extension, which are properly resolved by both postcss-import and css-loader.

[ghost]

Should this issue be re-opened?

[madyankin]

@tarikihm I will make an option to set the root directory in a couple of days. For now you can use relative paths for composes.

[ghost]

Thank you @Outpunk, you may also want to follow postcss/postcss#240 where adding a path option to PostCSS is being discussed. This would allows you to make the new option invisible once PostCSS introduces this.

[bernardodiasc]

I see this is an old issue, but since still open. This plugin solved this problem for me https://www.npmjs.com/package/postcss-modules-resolve-path

[FezVrasta]

Is this issue under the radar?

[kamilic]

Need this feature.

[madyankin]

Added in #126