question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Examples are not being generated with 'watch' script

See original GitHub issue

Most appropriate sections of the p5.js website?

Examples

What is your operating system?

Windows

Web browser and version

103.0.5060.114 (Official Build) (64-bit) (cohort: Stable)

Actual Behavior

When following the ‘setup’ and ‘running’ instructions in the readme, the npm run watch script generates examples/index.html, but none of the individual examples. All example pages, such as http://localhost:9000/examples/3d-basic-shader.html, return Cannot GET /examples/3d-basic-shader.html. All other pages, including reference pages, appear to be generated properly.

This might be some confusion or misconfiguration on my end, and if appropriate I’d like to update the readme to help others who run into the same issue.

Expected Behavior

I expect the individual example pages to be generated when either the npm run watch or npm run assemble commands are run.

Steps to reproduce

I forked p5.js-website, confirmed that Java is installed, ran npm install then npm run watch. Then, I navigated to http://localhost:9000/examples/, which displays properly, after which all individual examples return the same error.

Would you like to work on the issue?

If appropriate I’d be happy to update the readme with more info

Issue Analytics

  • State:open
  • Created a year ago
  • Comments:9 (8 by maintainers)

github_iconTop GitHub Comments

2reactions
aceslowmancommented, Jul 18, 2022

@takyano thanks for bringing this up, it appears that this was the problem! After running git config core.autocrlf false and doing a full refresh of my fork, it appears that the pages are being assembled properly.

Would there be any value in including a .gitattributes file to disable autocrlf for the repository?

1reaction
limzykennethcommented, Jul 19, 2022

Would there be any value in including a .gitattributes file to disable autocrlf for the repository?

I think that would help. You can file a PR for this if you like.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Troubleshooting | Apps Script - Google Developers
If you add a popular library to your script, you might receive an error message stating that it's missing, even though the library...
Read more >
actions/github-script: Write workflows scripting the GitHub API ...
Examples. Note that github-token is optional in this action, and the input is there in case you need to use a non-default ...
Read more >
Watchers | Vue.js
Watchers declared using the watch option or the $watch() instance method are automatically stopped when the owner component is unmounted, so in most...
Read more >
Watch and WatchOptions | webpack
Verify that webpack is not being notified of changes by running webpack with the --progress flag. If progress shows on save but no...
Read more >
Snakefiles and Rules — Snakemake 7.19.1 documentation
For example, if another rule in the workflow requires the file 101/file. ... Of course, the input file might have to be generated...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found