Rename @elastic/kbn-build to @kbn/build (#16507)

package.json

@@ -225,7 +225,7 @@
     "@elastic/eslint-config-kibana": "link:packages/eslint-config-kibana",
     "@elastic/eslint-import-resolver-kibana": "1.0.0",
     "@elastic/eslint-plugin-kibana-custom": "link:packages/eslint-plugin-kibana-custom",
-    "@elastic/kbn-build": "link:packages/kbn-build",
+    "@kbn/build": "link:packages/kbn-build",
     "angular-mocks": "1.4.7",
     "babel-eslint": "8.1.2",
     "backport": "2.2.0",

packages/kbn-build/package.json

@@ -1,5 +1,5 @@
 {
-  "name": "@elastic/kbn-build",
+  "name": "@kbn/build",
   "kibana": {
     "build": {
       "skip": true

tasks/build/package_json.js

@@ -1,4 +1,4 @@
-import { transformDependencies } from '@elastic/kbn-build';
+import { transformDependencies } from '@kbn/build';
 
 module.exports = function (grunt) {
   const pkg = grunt.config.get('pkg');

tasks/build/packages.js

@@ -1,4 +1,4 @@
-import { buildProductionProjects } from '@elastic/kbn-build';
+import { buildProductionProjects } from '@kbn/build';
 
 /**
  * High-level overview of how we enable shared packages in production:
@@ -6,15 +6,15 @@ import { buildProductionProjects } from '@elastic/kbn-build';
  * tl;dr We copy the packages directly into Kibana's `node_modules` folder,
  * which means they will be available when `require(...)`d.
  *
- * During development we rely on `@elastic/kbn-build` to find all the packages
+ * During development we rely on `@kbn/build` to find all the packages
  * in the Kibana repo and run Yarn in all the right places to create symlinks
  * between these packages. This development setup is described in-depth in the
- * readme in `@elastic/kbn-build`.
+ * readme in `@kbn/build`.
  *
- * However, for production we can't use `@elastic/kbn-build` as part of the
+ * However, for production we can't use `@kbn/build` as part of the
  * installation as we don't have an install "tool/step" that can kick it off.
  * We also can't include symlinks in the archives for the different platform, so
- * we can't run `@elastic/kbn-build` in the same way we do for development and
+ * we can't run `@kbn/build` in the same way we do for development and
  * just package the result. That means we have two options: either we prepare
  * everything in the built package or we perform the necessary actions when
  * Kibana is starting up in production. We decided on the former: all the Kibana

yarn.lock

@@ -112,10 +112,6 @@
   version "1.1.2"
   resolved "https://registry.yarnpkg.com/@elastic/filesaver/-/filesaver-1.1.2.tgz#1998ffb3cd89c9da4ec12a7793bfcae10e30c77a"
 
-"@elastic/kbn-build@link:packages/kbn-build":
-  version "0.0.0"
-  uid ""
-
 "@elastic/numeral@2.3.1":
   version "2.3.1"
   resolved "https://registry.yarnpkg.com/@elastic/numeral/-/numeral-2.3.1.tgz#743801971d8f0c975f9a122867d0e8939d31b3eb"
@@ -128,6 +124,10 @@
   version "0.2.3"
   resolved "https://registry.yarnpkg.com/@elastic/ui-ace/-/ui-ace-0.2.3.tgz#5281aed47a79b7216c55542b0675e435692f20cd"
 
+"@kbn/build@link:packages/kbn-build":
+  version "0.0.0"
+  uid ""
+
 "@types/json-stable-stringify@^1.0.32":
   version "1.0.32"
   resolved "https://registry.yarnpkg.com/@types/json-stable-stringify/-/json-stable-stringify-1.0.32.tgz#121f6917c4389db3923640b2e68de5fa64dda88e"