next-google-docs VS globby

/* File: content/projectData.js */ module.exports = [ { id: 15, name: "Google Docs with Next.js", coverURL: "https://imgur.com/bQkEGlb.png", description: "Next Google Docs is a web app which uses draft.js to create a document for you. It also uses Firebase to store all the user's data.", githubURL: "https://github.com/j471n/next-google-docs", previewURL: "https://google-next-docs.vercel.app/", tools: ["Next.js", "Tailwind CSS", "Firebase", "Draft.js", "Next Auth"], pinned: true, }, /* ..............Other Projects......... */ ];

Files to be scanned/excluded are defined via globby which is based on node-glob

The snippet above uses globby to find each page.tsx in the app directory (collectPaths). After the file paths are collected, each path is transformed to the url path (createPath). The last step is to create the sitemap (createSitemap) and write to the public directory.

First install globby and prettier.

If you mean node module, try https://www.npmjs.com/package/qnm If you need to search fs by pattern try https://github.com/sindresorhus/globby

We need to do a few things in our local-intercept.js file to identify and load these files. So we are going to use globby again to find our targetables files.

Because of this, we need to get all our page routes or at least the ones that are public. This is an easy task with globby, this lib allows us to get the name of the files based on regex URL on our folder structure.

Identifying local styling globby is a great tool for recursively scanning directories to find files or folders matching specific criteria, so we need to add that to our project.