Add NUL byte removal to resolveFrom as well

Author: thecrypticace

packages/tailwindcss-language-server/src/util/resolveFrom.ts

@@ -56,5 +56,17 @@ export function resolveFrom(from?: string, id?: string): string {
 
   let result = resolver.resolveSync({}, from, id)
   if (result === false) throw Error()
+
+  // The `enhanced-resolve` package supports resolving paths with fragment
+  // identifiers. For example, it can resolve `foo/bar#baz` to `foo/bar.js`
+  // However, it's also possible that a path contains a `#` character as part
+  // of the path itself. For example, `foo#bar` might point to a file named
+  // `foo#bar.js`. The resolver distinguishes between these two cases by
+  // escaping the `#` character with a NUL byte when it's part of the path.
+  //
+  // Since the real path doesn't actually contain NUL bytes, we need to remove
+  // them to get the correct path otherwise readFileSync will throw an error.
+  result = result.replace(/\0(.)/g, '$1')
+
   return result
 }