chore(NA): manage npm dependencies within bazel

[mistic]

One step forward on #69706

That PR introduces a complete Bazel WORKSPACE and by declaring an yarn_install repo rule within a managed_directory it makes Bazel the one responsible for calling the yarn install where previously it was @kbn/pm responsibility.

The yarn_install rule is declaring a data dependency on node_modules/.yarn-integrity so we can still have the yarn install running after an yarn kbn clean otherwise bazel won't install the dependencies as for its state nothing changed within a yarn kbn clean (package.json and yarn.lock file don't present any changes).

By having Bazel managing our dependencies installation we will have the ability to declare fine grained dependencies within our Bazel rules as BUILD files will be generated in the external @npm Bazel repository as part of the workspace installation.

It will allow us to start introduce packages to being able to built within Bazel as soon as our RFC lands.

[tylersmalley]

I believe in the preinstall_check we will want to prevent using yarn install directly, right?

diff --git a/preinstall_check.js b/preinstall_check.js
index d6d0cdf1ffb..41049b72151 100644
--- a/preinstall_check.js
+++ b/preinstall_check.js
@@ -33,9 +33,10 @@
       return;
     }
 
-    if (argv.cooked.includes('install')) {
-      console.log('\nWARNING: When installing dependencies, prefer `yarn kbn bootstrap`\n');
-    }
+if (argv.cooked.includes('install')) {
+  console.error('\nWhen installing dependencies, use `yarn kbn bootstrap`\n');
+  process.exit(1);
+}
   } catch (e) {
     // if it fails we do nothing, as this is just intended to be a helpful message
   }

[tylersmalley]

@jbudz, do you have a windows VM to test this on?

[jbudz]

I do - testing now.

edit: Windows setup is working

[mistic]

@tylersmalley regarding the preinstall check, I believe even if you use yarn install everything will be okay as you only need the Bazel generated build files for each node_module for Bazel compilations (and when they are in fault Bazel will re run an install to generate them). In any case, do you still prefer to log the error in the preinstall check?

[tylersmalley]

@mistic, then no need to prevent it if it doesn't create issues.

[mistic]

@tylersmalley just tested it and I can confirm it doesnt cause issues

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: d1221cf
• Storybooks Preview
• Documentation Changes

Metrics [docs]

✅ unchanged

History

• 💚 Build #110603 succeeded 3e5aac2
• 💚 Build #110595 succeeded 3e5aac2
• 💚 Build #110381 succeeded 5d67d00
• 💚 Build #110044 succeeded 511568e
• 💔 Build #110019 failed 551d476

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

[kibanamachine]

💚 Backport successful

✅ 7.x / #93474

Successful backport PRs will be merged automatically after passing CI.