This should now be available on npm to try out locally via https://www.npmjs.com/package/tslint-to-eslint-config/v/2.0.0-beta0. 🚀

cc @JamesHenry

Thanks so much for publishing that @JoshuaKGoldberg!

After some digging I was able to get to the bottom of why my conversion was not behaving the same as when using the CLI (the rule severities and configs were not being reflected if you remember).

It is because full and raw are not equivalents, which is what I had been treating them as (in fact your code and docs in this PR currently also seems to).

Full is the result of running tslint --print-config and it is this JSON result which is what contains the necessary data about the rule severity and config which is then used when converting the config.

So I have managed to get it fully working after extracting some more parts of the library into my code.

I believe, however, I can avoid the need for that if you just expose to me the findReportedConfiguration() utility.

Here is an abridged version of my full usage of the library:

const reportedConfiguration = await findReportedConfiguration(
  childProcessExec,
  'npx tslint --print-config',
  pathToTslintJson
);

// ... error handling here...

const originalConfigurations = {
  tslint: {
    full: reportedConfiguration,
    raw: rawTslintJson,
  },
};

const summarizedConfiguration = await createESLintConfiguration(
  originalConfigurations
);

const convertedESLintConfig = joinConfigConversionResults(
  summarizedConfiguration,
  originalConfigurations
);

Let me know if you have any questions!

Thanks for the updates! Please could you publish another beta whenever you get chance? Not urgent!

Super, published 2.0.0-beta1 @JamesHenry. 👍

This is looking really good! I haven't yet tackled the disable comment conversion logic, but for configs I think we are basically there. You can see my full usage of the API below for reference.

I have the following main request/callout as things stand:

With this usage below I am still ending up with an empty tslint-to-eslint-config.log being created on disk.

• I can of course manually clean this up, but the way that schematics work is that the user will be able to see that that file existed and that it was deleted as part of the run (which is very confusing cause it was not in there when they ran the command) [see screenshot]

  • 

• Please can we hunt down that createWriteStream and prevent it from being executed when using the Node API?

import type { Linter as ESLintLinter } from 'eslint';
import {
  createESLintConfiguration,
  findReportedConfiguration,
  joinConfigConversionResults,
} from 'tslint-to-eslint-config';

type TSLintRuleSeverity = 'warning' | 'error' | 'off';
type TSLintRuleOptions = {
  ruleArguments: any[];
  ruleName: string;
  ruleSeverity: TSLintRuleSeverity;
};

export async function convertToESLintConfig(
  pathToTslintJson: string,
  tslintJson: Record<string, unknown>,
): Promise<{
  convertedESLintConfig: ESLintLinter.Config;
  unconvertedTSLintRules: TSLintRuleOptions[];
}> {
  const reportedConfiguration = await findReportedConfiguration(
    'npx tslint --print-config',
    pathToTslintJson,
  );

  if (reportedConfiguration instanceof Error) {
    if (
      reportedConfiguration.message.includes('unknown option `--print-config')
    ) {
      throw new Error(
        '\nError: TSLint v5.18 required in order to run this schematic. Please update your version and try again.\n',
      );
    }
    throw new Error(`Unexpected error: ${reportedConfiguration.message}`);
  }

  const originalConfigurations = {
    tslint: {
      full: reportedConfiguration,
      raw: tslintJson,
    },
  };

  const summarizedConfiguration = await createESLintConfiguration(
    originalConfigurations,
  );

  const convertedESLintConfig = joinConfigConversionResults(
    summarizedConfiguration,
    originalConfigurations,
  ) as ESLintLinter.Config;

  return {
    convertedESLintConfig,
    unconvertedTSLintRules: summarizedConfiguration.missing,
  };
}

Indeed, we can: the issue, I think, is that processLogger.ts creates a write stream immediately:

const debugFileName = "./tslint-to-eslint-config.log";

export const processLogger = {
    debugFileName,
    info: fs.createWriteStream(debugFileName),

...even though it's not used in this code. I'll switch it to only creating that write stream once, when first needed in calling .info().

@JamesHenry try the latest beta2?

beta2 is looking good!

Informal approvals from @KingDarBoja (over Gitter) and @JamesHenry (by virtue of #173 existing and me presuming), so I'm going to merge this! 🚀

If anybody has further requests on it, please do let me know somewhere and/or file an issue -- I'd like to tackle them before we stable release 2.0.0.