From e1c7e913061f401ce1cb7a1fcf0a8fd7921156f2 Mon Sep 17 00:00:00 2001 From: Jorge Calvar Date: Fri, 22 May 2026 12:49:37 +0200 Subject: [PATCH] fix(template): use public npm registry for @babel/parser The @babel/parser entry in template/package-lock.json was resolving from the Databricks dev npm proxy (npm-proxy.dev.databricks.com), which was inadvertently introduced in #347. External users do not have access to the proxy, causing `npm install` to fail for the template. Switch the `resolved` URL back to the public npm registry. The integrity hash is unchanged and matches the public registry's tarball. Signed-off-by: Jorge Calvar --- template/package-lock.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/template/package-lock.json b/template/package-lock.json index cc264cd9..2066912b 100644 --- a/template/package-lock.json +++ b/template/package-lock.json @@ -442,7 +442,7 @@ }, "node_modules/@babel/parser": { "version": "7.29.2", - "resolved": "https://npm-proxy.dev.databricks.com/@babel/parser/-/parser-7.29.2.tgz", + "resolved": "https://registry.npmjs.org/@babel/parser/-/parser-7.29.2.tgz", "integrity": "sha512-4GgRzy/+fsBa72/RZVJmGKPmZu9Byn8o4MoLpmNe1m8ZfYnz5emHLQz3U4gLud6Zwl0RZIcgiLD7Uq7ySFuDLA==", "dev": true, "license": "MIT",