fix #2495: strip non-go ignorePatternData stuff

CHANGELOG.md

@@ -26,7 +26,20 @@
 
     So instead of publishing a native esbuild binary executable to npm, this release publishes a WebAssembly fallback build. This is essentially the same as the `esbuild-wasm` package but it's installed automatically when you install the `esbuild` package on Android ARM. So packages that depend on the `esbuild` package should now work on Android ARM. This change has not yet been tested end-to-end because I don't have a 32-bit Android ARM device myself, but in theory it should work.
 
-    This inherits the drawbacks of WebAssembly including significantly slower performance than native as well as potentially also more severe memory usage limitations. If you want to use a native binary executable of esbuild on Android ARM, you may be able to build it yourself from source after installing the Android build tools.
+    This inherits the drawbacks of WebAssembly including significantly slower performance than native as well as potentially also more severe memory usage limitations and lack of certain features (e.g. `--serve`). If you want to use a native binary executable of esbuild on Android ARM, you may be able to build it yourself from source after installing the Android build tools.
+
+* Attempt to better support Yarn's `ignorePatternData` feature ([#2495](https://github.com/evanw/esbuild/issues/2495))
+
+    Part of resolving paths in a project using Yarn's Plug'n'Play feature involves evaluating a regular expression in the `ignorePatternData` property of `.pnp.data.json`. However, it turns out that the particular regular expressions generated by Yarn use some syntax that works with JavaScript regular expressions but that does not work with Go regular expressions.
+
+    In this release, esbuild will now strip some of the the problematic syntax from the regular expression before compiling it, which should hopefully allow it to be compiled by Go's regular expression engine. The specific character sequences that esbuild currently strips are as follows:
+
+    * `(?!\.)`
+    * `(?!(?:^|\/)\.)`
+    * `(?!\.{1,2}(?:\/|$))`
+    * `(?!(?:^|\/)\.{1,2}(?:\/|$))`
+
+    These seem to be used by Yarn to avoid the `.` and `..` path segments in the middle of relative paths. The removal of these character sequences seems relatively harmless in this case since esbuild shouldn't ever generate such path segments. This change should add support to esbuild for Yarn's [`pnpIgnorePatterns`](https://yarnpkg.com/configuration/yarnrc/#pnpIgnorePatterns) feature.
 
 ## 0.15.7
 

internal/resolver/resolver.go

@@ -445,6 +445,9 @@ func (rr *resolver) Resolve(sourceDir string, importPath string, kind ast.Import
 						r.pnpManifest = compileYarnPnPData(absPath, r.fs.Dir(absPath), json)
 					}
 				}
+				if r.debugLogs != nil && r.pnpManifest != nil && r.pnpManifest.invalidIgnorePatternData != "" {
+					r.debugLogs.addNote("  Invalid Go regular expression for \"ignorePatternData\": " + r.pnpManifest.invalidIgnorePatternData)
+				}
 				break
 			}
 		}

internal/resolver/yarnpnp.go

@@ -28,7 +28,8 @@ type pnpData struct {
 	// the classic Node.js resolution algorithm rather than the Plug'n'Play one.
 	// Note that unlike other paths in the manifest, the one checked against this
 	// regexp won't begin by `./`.
-	ignorePatternData *regexp.Regexp
+	ignorePatternData        *regexp.Regexp
+	invalidIgnorePatternData string
 
 	// This is the main part of the PnP data file. This table contains the list
 	// of all packages, first keyed by package ident then by package reference.
@@ -438,7 +439,26 @@ func compileYarnPnPData(absPath string, absDirPath string, json js_ast.Expr) *pn
 
 	if value, _, ok := getProperty(json, "ignorePatternData"); ok {
 		if ignorePatternData, ok := getString(value); ok {
-			data.ignorePatternData, _ = regexp.Compile(ignorePatternData)
+			// The Go regular expression engine doesn't support some of the features
+			// that JavaScript regular expressions support, including "(?!" negative
+			// lookaheads which Yarn uses. This is deliberate on Go's part. See this:
+			// https://github.com/golang/go/issues/18868.
+			//
+			// Yarn uses this feature to exclude the "." and ".." path segments in
+			// the middle of a relative path. However, we shouldn't ever generate
+			// such path segments in the first place. So as a hack, we just remove
+			// the specific character sequences used by Yarn for this so that the
+			// regular expression is more likely to be able to be compiled.
+			ignorePatternData = strings.ReplaceAll(ignorePatternData, `(?!\.)`, "")
+			ignorePatternData = strings.ReplaceAll(ignorePatternData, `(?!(?:^|\/)\.)`, "")
+			ignorePatternData = strings.ReplaceAll(ignorePatternData, `(?!\.{1,2}(?:\/|$))`, "")
+			ignorePatternData = strings.ReplaceAll(ignorePatternData, `(?!(?:^|\/)\.{1,2}(?:\/|$))`, "")
+
+			if reg, err := regexp.Compile(ignorePatternData); err == nil {
+				data.ignorePatternData = reg
+			} else {
+				data.invalidIgnorePatternData = ignorePatternData
+			}
 		}
 	}
 

require/yarnpnp/bar/index.js

@@ -0,0 +1 @@
+exports.bar = require('bar-pkg').bar

require/yarnpnp/in.mjs

@@ -17,4 +17,7 @@ if (mm.default.getType('txt') !== 'text/plain') throw '❌ mime'
 import * as foo from 'foo'
 if (foo.default !== 'foo') throw '❌ foo'
 
+import * as bar from './bar/index.js'
+if (bar.bar !== 'bar') throw '❌ bar'
+
 console.log('✅ Yarn PnP tests passed')

scripts/test-yarnpnp.js

@@ -37,6 +37,9 @@ function reinstallYarnIfNeeded() {
     run('yarn set version 3.2.3')
   }
 
+  const rc = fs.readFileSync(path.join(rootDir, '.yarnrc.yml'), 'utf8')
+  fs.writeFileSync(path.join(rootDir, '.yarnrc.yml'), `pnpIgnorePatterns: ["./bar/**"]\n` + rc)
+
   run('yarn install')
 }