fix(processor): resolve metadata extraction failure on Vercel

[moshams272]

Summary

The Edit this page link works locally well, but in Vercel it doesn't. After debugging, I found in the file plugins/processor/source.mjs that:

export const applySourceMetadata = (
  project,
  { libDir = './webpack/lib' } = {}
) => {
  const absoluteLibDir = resolve(libDir);
  if (!existsSync(absoluteLibDir) || !statSync(absoluteLibDir).isDirectory()) {
    return;
  }
...}

The existsSync function works well locally, as there is a webpack repo in the root path, but we don't have it in vercel.

This PR uses the cached repo instead of that one in the root path.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
webpack-doc-kit	Ready	Preview, Comment	Jul 12, 2026 10:05am

[avivkeller]

nit do all this logic inside of applySourceMetadata

[moshams272]

I don't want to edit this function, but if u see it'll be better, that's my suggestion:

const getWebpackPath = ()=>{
    const versions = JSON.parse(readFileSync('./versions.json'));
    return versions? `./.cache/webpack/${versions[0]}/lib` : `./webpack/lib`
}

const applySourceMetadata = project => {
    const libDir = getWebpackPath();
    ...
}

Make isolated function besides applySourceMetadata, and remove the second option object in function logic as it now like this:

const applySourceMetadata = (project, {libDir = './webpack/lib'} = {}) => {...}

WDUT?!