mirror of
https://github.com/elastic/kibana.git
synced 2025-06-27 18:51:07 -04:00
1b85815402
Fixes https://github.com/elastic/kibana/issues/149344 This PR migrates all plugins to packages automatically. It does this using `node scripts/lint_packages` to automatically migrate `kibana.json` files to `kibana.jsonc` files. By doing this automatically we can simplify many build and testing procedures to only support packages, and not both "packages" and "synthetic packages" (basically pointers to plugins). The majority of changes are in operations related code, so we'll be having operations review this before marking it ready for review. The vast majority of the code owners are simply pinged because we deleted all `kibana.json` files and replaced them with `kibana.jsonc` files, so we plan on leaving the PR ready-for-review for about 24 hours before merging (after feature freeze), assuming we don't have any blockers (especially from @elastic/kibana-core since there are a few core specific changes, though the majority were handled in #149370). --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
62 lines
2.5 KiB
JavaScript
62 lines
2.5 KiB
JavaScript
/*
|
|
* 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.
|
|
*/
|
|
|
|
module.exports = () => ({
|
|
presets: [
|
|
// plugins always run before presets, but in this case we need the
|
|
// @babel/preset-typescript preset to run first so we have to move
|
|
// our explicit plugin configs to a sub-preset
|
|
{
|
|
plugins: [
|
|
require.resolve('babel-plugin-add-module-exports'),
|
|
|
|
// The class properties proposal was merged with the private fields proposal
|
|
// into the "class fields" proposal. Babel doesn't support this combined
|
|
// proposal yet, which includes private field, so this transform is
|
|
// TECHNICALLY stage 2, but for all intents and purposes it's stage 3
|
|
//
|
|
// See https://github.com/babel/proposals/issues/12 for progress
|
|
require.resolve('@babel/plugin-proposal-class-properties'),
|
|
|
|
// Optional Chaining proposal is stage 4 (https://github.com/tc39/proposal-optional-chaining)
|
|
// Need this since we are using TypeScript 3.7+
|
|
require.resolve('@babel/plugin-proposal-optional-chaining'),
|
|
|
|
// Nullish coalescing proposal is stage 4 (https://github.com/tc39/proposal-nullish-coalescing)
|
|
// Need this since we are using TypeScript 3.7+
|
|
require.resolve('@babel/plugin-proposal-nullish-coalescing-operator'),
|
|
|
|
// Proposal is on stage 4, and included in ECMA-262 (https://github.com/tc39/proposal-export-ns-from)
|
|
// Need this since we are using TypeScript 3.8+
|
|
require.resolve('@babel/plugin-proposal-export-namespace-from'),
|
|
|
|
// Proposal is on stage 4, and included in ECMA-262 (https://github.com/tc39/proposal-export-ns-from)
|
|
// Need this since we are using TypeScript 3.9+
|
|
require.resolve('@babel/plugin-proposal-private-methods'),
|
|
|
|
// It enables the @babel/runtime so we can decrease the bundle sizes of the produced outputs
|
|
[
|
|
require.resolve('@babel/plugin-transform-runtime'),
|
|
{
|
|
version: '^7.12.5',
|
|
},
|
|
],
|
|
],
|
|
},
|
|
|
|
require.resolve('@babel/preset-react'),
|
|
|
|
[
|
|
require.resolve('@babel/preset-typescript'),
|
|
{
|
|
allowNamespaces: true,
|
|
allowDeclareFields: true,
|
|
},
|
|
],
|
|
],
|
|
});
|