fix(indexer): incorrect path on Windows (#141)

README.md

@@ -226,6 +226,10 @@ By default, the deployed Azure web app will have no authentication or access res
 
 To then limit access to a specific set of users or groups, you can follow the steps from [Restrict your Azure AD app to a set of users](https://learn.microsoft.com/azure/active-directory/develop/howto-restrict-your-app-to-a-set-of-users) by changing "Assignment Required?" option under the Enterprise Application, and then assigning users/groups access. Users not granted explicit access will receive the error message -AADSTS50105: Your administrator has configured the application <app_name> to block users unless they are specifically granted ('assigned') access to the application.-
 
+### Additional security considerations
+
+We recommend deploying additional security mechanisms. When applicable, consider setting up a [VNet](https://learn.microsoft.com/azure/virtual-network/virtual-networks-overview) or setting up a [Proxy Policy](https://learn.microsoft.com/en-us/azure/api-management/proxy-policy).
+
 ### Enabling CORS for an alternate frontend
 
 By default, the deployed search API will only allow requests from the same origin as the deployed web app origin. To enable [CORS](https://developer.mozilla.org/docs/Web/HTTP/CORS) for a frontend hosted on a different origin, run:

packages/indexer/bin/index-files.js

@@ -1,21 +1,5 @@
 #!/usr/bin/env node
 import process from 'node:process';
-import { execSync } from 'node:child_process';
 import { run } from '../dist/lib/cli.js';
 
-if ((process.env.NODE_OPTIONS ?? '').includes('--no-warnings')) {
-  run(process.argv);
-} else {
-  // Silence experimental warnings
-  try {
-    execSync(process.argv.join(' '), {
-      stdio: 'inherit',
-      env: {
-        ...process.env,
-        NODE_OPTIONS: `${process.env.NODE_OPTIONS ?? ''} --no-warnings`,
-      },
-    });
-  } catch {
-    // Do nothing
-  }
-}
+run(process.argv);