vercel 23.1.3-canary.4 → 23.1.3-canary.43

package/dist/VERCEL_DIR_README.txt

@@ -0,0 +1,11 @@
+> Why do I have a folder named ".vercel" in my project?
+The ".vercel" folder is created when you link a directory to a Vercel project.
+
+> What does the "project.json" file contain?
+The "project.json" file contains:
+- The ID of the Vercel project that you linked ("projectId")
+- The ID of the user or team your Vercel project is owned by ("orgId")
+
+> Should I commit the ".vercel" folder?
+No, you should not share the ".vercel" folder with anyone.
+Upon creation, it will be automatically added to your ".gitignore" file.

package/dist/builder-worker.js

@@ -0,0 +1,48 @@
+/**
+ * This file gets copied out of the `pkg` snapshot filesystem into the `vc dev`
+ * builder cache directory, so it's very important that it does not rely on any
+ * modules from npm that would not be available in that directory (so basically,
+ * only Vercel Runtimes and `@vercel/build-utils`.
+ */
+const { FileFsRef } = require('@vercel/build-utils');
+
+process.on('unhandledRejection', err => {
+  console.error('Exiting builder due to build error:');
+  console.error(err);
+  process.exit(1);
+});
+
+process.on('message', onMessage);
+
+function onMessage(message) {
+  processMessage(message).catch(err => {
+    Object.defineProperty(err, 'message', { enumerable: true });
+    Object.defineProperty(err, 'stack', { enumerable: true });
+    process.removeListener('message', onMessage);
+    process.send({ type: 'buildResult', error: err }, () => process.exit(1));
+  });
+}
+
+async function processMessage(message) {
+  const { requirePath, buildOptions } = message;
+  const builder = require(requirePath);
+
+  // Convert the `files` to back into `FileFsRef` instances
+  for (const name of Object.keys(buildOptions.files)) {
+    const ref = Object.assign(
+      Object.create(FileFsRef.prototype),
+      buildOptions.files[name]
+    );
+    buildOptions.files[name] = ref;
+  }
+
+  const result = await builder.build(buildOptions);
+
+  // `@vercel/next` sets this, but it causes "Converting circular
+  // structure to JSON" errors, so delete the property...
+  delete result.childProcesses;
+
+  process.send({ type: 'buildResult', result });
+}
+
+process.send({ type: 'ready' });