chore(NA): moving @kbn/securitysolution-io-ts-list-types to babel transpile

[mistic]

One step forward on #69706

That PR moves the @kbn/securitysolution-io-ts-list-types from using tsc compiler to babel transpiler to produce the js outputs.

[elasticmachine]

Pinging @elastic/kibana-operations (Team:Operations)

[jbudz]

Any ideas on the bundle size changes?

[mistic]

@jbudz It is related with the way typescript and babel differently transpile exports. In most of the packages it is not noticeable but in packages like this one which are file and export intensive it can be noted. Here you have the differences in the outputs between the 2 transpilers:

TSC

"use strict";
/*
 * Copyright Elasticsearch B.V. and/or licensed to Elasticsearch B.V. under one
 * or more contributor license agreements. Licensed under the Elastic License
 * 2.0 and the Server Side Public License, v 1; you may not use this file except
 * in compliance with, at your election, the Elastic License 2.0 or the Server
 * Side Public License, v 1.
 */
Object.defineProperty(exports, "__esModule", { value: true });
const tslib_1 = require("tslib");
tslib_1.__exportStar(require("./common"), exports);
tslib_1.__exportStar(require("./request"), exports);
tslib_1.__exportStar(require("./response"), exports);
tslib_1.__exportStar(require("./typescript_types"), exports);
//# sourceMappingURL=index.js.map

BABEL

"use strict";

Object.defineProperty(exports, "__esModule", {
  value: true
});

var _common = require("./common");

Object.keys(_common).forEach(function (key) {
  if (key === "default" || key === "__esModule") return;
  if (key in exports && exports[key] === _common[key]) return;
  Object.defineProperty(exports, key, {
    enumerable: true,
    get: function () {
      return _common[key];
    }
  });
});

var _request = require("./request");

Object.keys(_request).forEach(function (key) {
  if (key === "default" || key === "__esModule") return;
  if (key in exports && exports[key] === _request[key]) return;
  Object.defineProperty(exports, key, {
    enumerable: true,
    get: function () {
      return _request[key];
    }
  });
});

var _response = require("./response");

Object.keys(_response).forEach(function (key) {
  if (key === "default" || key === "__esModule") return;
  if (key in exports && exports[key] === _response[key]) return;
  Object.defineProperty(exports, key, {
    enumerable: true,
    get: function () {
      return _response[key];
    }
  });
});

var _typescript_types = require("./typescript_types");

Object.keys(_typescript_types).forEach(function (key) {
  if (key === "default" || key === "__esModule") return;
  if (key in exports && exports[key] === _typescript_types[key]) return;
  Object.defineProperty(exports, key, {
    enumerable: true,
    get: function () {
      return _typescript_types[key];
    }
  });
});

I'll search to see if is there anything we can do about this

[FrankHassanabad]

LGTM,

• Looked over this PR and everything looks as advertised 👍

[mistic]

@elasticmachine merge upstream

[mistic]

@elasticmachine merge upstream

[mistic]

@jbudz do you think we are good to go here?

[mistic]

@elasticmachine merge upstream

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 2b2b6cf
• Storybooks Preview

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
lists	295.7KB	310.5KB	+14.8KB
securitySolution	6.5MB	6.5MB	+14.7KB
total			+29.4KB

History

• 💚 Build #148790 succeeded 9364741
• 💔 Build #148748 failed 55303dc
• 💚 Build #148278 succeeded cb8d49b
• 💔 Build #148168 failed fd24c0ded2d3be7e712afa0f2b77b998ff363b8d
• 💔 Build #148161 failed d435e5a6849ddcefda9cffef8dd87623d708feda

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[kibanamachine]

💚 Backport successful

Status	Branch	Result
✅	7.x

This backport PR will be merged automatically after passing CI.