Use enhanced-resolve for node resolution (#36)

This moves to using `enhanced-resolve` for resolving reporters in the
CLI. Primarily because it is more up to date with the node resolution
algorithm, but seems we dropped a few deep dependencies along the way
too (which is good).

Author: 43081j

fixtures/custom-reporter/node_modules/dual/package.json

@@ -1,6 +1,6 @@
 import path from 'path';
 import fs from 'fs';
-import resolve from 'resolve';
+import resolve from 'enhanced-resolve';
 import { command as createCommand, Error as CliError } from 'clap';
 import * as reporters from './reporter/index.js';
 import { validatePath, validateString } from './helpers.js';
@@ -29,6 +29,10 @@ function printResult(result, reporter) {
     }
 }
 
+const nodeResolver = resolve.create.sync({
+    conditionNames: ['node', 'import']
+});
+
 const command = createCommand('csstree-validate [fileOrDir]')
     .version(version)
     .option(
@@ -43,7 +47,7 @@ const command = createCommand('csstree-validate [fileOrDir]')
 
             if (!hasOwnProperty.call(reporters, nameOrFile)) {
                 try {
-                    const resolvedPath = resolve.sync(nameOrFile, { basedir: process.cwd() });
+                    const resolvedPath = nodeResolver(process.cwd(), nameOrFile);
                     return import(resolvedPath);
                 } catch (e) {}