Unable to build from source because pdf-parse-pro submodule is inaccessible

[rltaxandria]

In one of your last commits you added a git submodule that points to the repo https://github.com/pdf-parse/pdf-parse-pro.git. But that repo is inaccessible for us. So when I run npm install after cloning it throws an error now.

[acdvorak]

@rltaxandria Try changing the build:pdf-parse-pro script to echo in package.json:

pdf-parse/package.json

Line 122 in 1d59d3e

"build:pdf-parse-pro": "vite build -c vite.config.pro.ts && rolldown -c rolldown.config.pro.ts",

diff --git a/package.json b/package.json
index 85e8b2c..8c89cf8 100644
--- a/package.json
+++ b/package.json
@@ -119,7 +119,7 @@
                "postbuild": "node scripts/post-build.mjs",
 
                "build:pdf-parse": "vite build && rolldown -c",
-               "build:pdf-parse-pro": "vite build -c vite.config.pro.ts && rolldown -c rolldown.config.pro.ts",
+               "build:pdf-parse-pro": "echo",
                "build:worker": "vite build -c vite.config.worker.ts && rolldown -c rolldown.config.worker.ts",
                "build:node": "npm run build:node:cjs && npm run build:node:esm && rolldown -c rolldown.config.node.ts",
                "build:node:cjs": "esbuild src/node/index.ts --bundle --platform=node --format=cjs --target=node18 --outfile=dist/node.cjs --sourcemap",

[mehmet-kozan]

I am preparing to release a new version. The project will remain open source under the same license, and there will be no license change. However, to access the repository containing the pro features, you will need to support it through GitHub Sponsors. This approach is called supportware, developed to ensure the sustainability of open-source projects, and GitHub provides built-in support for it. I also want to prevent AI agents from freely using the code for training.

[mehmet-kozan]

README has been updated, you can take a look.

[rltaxandria]

Hey, thanks for the follow up. While I understand you and I even 100% agree with your statement on AI, the fact of the matter is that I cannot just pull in the repo and build it. If you want people to contribute to the project they need to be able to build it. And if a simple command like npm i is already failing I guarantee lots of people will just say "screw it" and move on.

[mehmet-kozan]

Current flow: Support > Checkout just main repo > npm i
** GitHub will automatically grant supporters access to the pdf-parse-pro repository.

You’re right, this could be an issue for contributions. To address it, I can permanently add interested users to the pdf-parse-pro package so they can build without problems. I’ll also add a note in the README about this, and I’m looking into ways to print an informative message to the console right before/after running npm i.

** I can make the initial npm i command run without errors. The tests would fail, which wouldn’t make much sense. The best approach is to find a way to print a warning to the console, so users are informed.

I’d appreciate any suggestions.