Closed sk337 closed 10 months ago
hmm... odd. will look into this. can you try again by running npm run build
from the root of the project? it might be because you're running it from a weird directory. might help. otherwise, I'd need to seriously debug this somehow.
runner@home: ~/work/tensurafan.github.io/tensurafan.github.io $ pwd
/home/runner/work/tensurafan.github.io/tensurafan.github.io
runner@home: ~/work/tensurafan.github.io/tensurafan.github.io $ ls -la
total 288
drwxr-xr-x 11 runner docker 4096 Dec 14 18:55 .
drwxr-xr-x 3 runner docker 4096 Dec 14 18:54 ..
drwxr-xr-x 8 runner docker 4096 Dec 14 18:55 .git
drwxr-xr-x 3 runner docker 4096 Dec 14 18:55 .github
-rw-r--r-- 1 runner docker 973 Dec 14 18:55 .gitignore
-rw-r--r-- 1 runner docker 558 Dec 14 18:55 404.html
-rw-r--r-- 1 runner docker 1066 Dec 14 18:55 LICENSE
-rw-r--r-- 1 runner docker 35520 Dec 14 18:55 Markdowntutorial.html
-rw-r--r-- 1 runner docker 516 Dec 14 18:55 README.md
-rw-r--r-- 1 runner docker 244 Dec 14 18:55 _build.js
-rw-r--r-- 1 runner docker 28 Dec 14 18:55 _config.yml
-rw-r--r-- 1 runner docker 3557 Dec 14 18:55 build.js
-rw-r--r-- 1 runner docker 36 Dec 14 18:55 build.txt
drwxr-xr-x 2 runner docker 4096 Dec 14 18:55 css
-rw-r--r-- 1 runner docker 1685 Dec 14 18:55 favicon-16x16.png
-rw-r--r-- 1 runner docker 2780 Dec 14 18:55 favicon-32x32.png
-rw-r--r-- 1 runner docker 9683 Dec 14 18:55 favicon-96x96.png
-rw-r--r-- 1 runner docker 1150 Dec 14 18:55 favicon.ico
drwxr-xr-x 2 runner docker 4096 Dec 14 18:55 foo
drwxr-xr-x 2 runner docker 4096 Dec 14 18:55 icons
drwxr-xr-x 2 runner docker 4096 Dec 14 18:55 img
-rw-r--r-- 1 runner docker 3365 Dec 14 18:55 index.html
drwxr-xr-x 12 runner docker 4096 Dec 14 18:55 js
drwxr-xr-x 3 runner docker 4096 Dec 14 18:55 ln
-rw-r--r-- 1 runner docker 9867 Dec 14 18:55 manga-index.json
-rw-r--r-- 1 runner docker 1872 Dec 14 18:55 manga.json
-rw-r--r-- 1 runner docker 949 Dec 14 18:55 manifest.json
drwxr-xr-x 158 runner docker 4096 Dec 14 18:55 node_modules
-rw-r--r-- 1 runner docker 114261 Dec 14 18:55 package-lock.json
-rw-r--r-- 1 runner docker 942 Dec 14 18:55 package.json
-rwxr-xr-x 1 runner docker 67 Dec 14 18:55 pre-commit
-rw-r--r-- 1 runner docker 377 Dec 14 18:55 serve.js
-rw-r--r-- 1 runner docker 2240 Dec 14 18:55 service-worker.js
runner@home: ~/work/tensurafan.github.io/tensurafan.github.io $ npm run build
> slime-reader@0.0.0 build
> npm install && node build
> slime-reader@0.0.0 postinstall
> cp pre-commit .git/hooks/pre-commit
up to date, audited 170 packages in 635ms
8 packages are looking for funding
run `npm fund` for details
5 moderate severity vulnerabilities
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
parsing Volume 6
parsing Volume 7
parsing Volume 8
parsing Volume 8.5 Side Stories
parsing Volume 9
parsing Volume 10
parsing Volume 11
parsing Volume 12
parsing Volume 13
parsing Volume 13.5 Side Stories
parsing Volume 14
parsing Volume 15
parsing Volume 16 - Edited MTL
parsing Volume 17 - Edited MTL
parsing Volume 18 - Edited MTL
parsing Volume 19 - Edited MTL
parsing Volume 20 - Edited MTL
skipping Volume 21 - In Progress
parsing Special Booklet 1
node:internal/process/promises:288
triggerUncaughtException(err, true /* fromPromise */);
^
[Error: ENOENT: no such file or directory, open '/home/runner/work/tensurafan.github.io/tensurafan.github.io/ln/v6/raw.html'] {
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: '/home/runner/work/tensurafan.github.io/tensurafan.github.io/ln/v6/raw.html'
}
Node.js v18.19.0
output of tree: https://termbin.com/2ula
Ah Right, I just remembered! A while back, we migrated away from using an NPM build command into a Python build setup to take advantage of markdown features and streamline edits, updates, deployment, etc. I'll have to ask @VoxelCubes what the new build setup is.
The previous build process using the raw.html files was deprecated. You don't need a build step, any changes to files outside the ln
folder will simply update live. You can run a local slime reader with npm start
from the project root directory. You'll be able to find it at localhost:9001 then.
So I talked to @VoxelCubes and it seems that the current most up to date builder script does not exist in this repo as it is a pile of spaghetti. According to vox: "I haven't released it because it's a bit finnicky due to markdown not being a specification per-se, every plain text file is valid markdown, so someone using it will always find a way to break it and I just don't wanna deal with that. Also, lots of slime-specific stuff just hard coded, so I either try to make this accommodating to other properties or it just stays as the slime tool."
If you want to run the server locally, you can use npm start
unfortunately, the only one who can actually build the app is vox right now. That said, if you want to submit a change, you can just update the corrisponding markdown file and vox will re-build it. If you want to addapt the slime reader for another series, I can probs help and adapt the original build.js to the new task.
my changes were to the volume source i will write my own build script
Changes to volume sources in the ln/sources
markdown files are welcome in a merge request, no modifications to auto-generated html in the ln
folder can be accepted.
when i run
build.js
i get this error