[2.1.1] fails to find `./schema/loader.json` (`schema-utils`)

[kimamula]

Updating to 2.1.1 results in the following error.

> Error: ENOENT: no such file or directory, open '/path/to/my/project/schema/loader.json'
>>     at Error (native)
>>     at Object.fs.openSync (fs.js:640:18)
>>     at Object.fs.readFileSync (fs.js:508:33)
>>     at validateOptions (/path/to/my/project/node_modules/schema-utils/dist/validateOptions.js:35:27)
>>     at Function.ExtractTextPlugin.extract (/path/to/my/project/node_modules/extract-text-webpack-plugin/index.js:206:3)
>>     at Object.<anonymous> (/path/to/my/project/webpack.config.js:19:32)
>>     at Module._compile (module.js:570:32)
>>     at Object.Module._extensions..js (module.js:579:10)
>>     at Module.load (module.js:487:32)
>>     at tryModuleLoad (module.js:446:12)

It is likely that you should use something like path.join(__dirname, 'schema/loader.json') instead of './schema/loader.json' in the following lines.

extract-text-webpack-plugin/index.js

Line 127 in 0271b39

validateOptions('./schema/plugin.json', options, 'Extract Text Plugin');

extract-text-webpack-plugin/index.js

Line 206 in 0271b39

validateOptions('./schema/loader.json', options, 'Extract Text Plugin (Loader)');

[michael-ciniawsky]

@kimamula Could you do me a favour and locally try by omitting the .json extname and test if it works ?

[kimamula]

No, omitting .json does not work.

[MirrorBytes]

Using path.resolve rectified the issue for me. @kimamula

[MirrorBytes]

Change line 127 to:
validateOptions(path.resolve(__dirname, './schema/plugin.json'), options, 'Extract Text Plugin');

Change line 206 to:
validateOptions(path.resolve(__dirname, './schema/loader.json'), options, 'Extract Text Plugin (Loader)');

Require path at the top, and everything works fine again.

[michael-ciniawsky]

hmm.. i need to check that again :), the paths should be resolved by validateOptions https://github.com/webpack-contrib/schema-utils/blob/master/src/validateOptions.js#L15 (but without using __dirname)

@MirrorBytes Do you want to send a PR with the fix? Otherwise I do it

[MirrorBytes]

The issue is that it's resolving based on the working directory.

[michael-ciniawsky]

Until now it worked at least for loaders :), but __dirname is seems to be the better solution, anyways we need a quick fix for this now 😛, please yes/no on sending PR (@MirrorBytes)

[MirrorBytes]

I'll send it.

[ahoym]

Got this error recently, fixed it temporarily by pinning to v2.0.0, though 2.1.0 may also work