I've noticed that you've removed the p5.play.js file and moved the p5Play JS file to p5play.js. All that's there in p5.play.js is a throw telling the user that the developer needs to change files. Moving to a different file is fine, but the way that it's currently done breaks existing projects that use p5.play.js.
I know GitHub Pages doesn't support server-side redirects, so as an alternative, I've crafted an alternative p5.play.js file that warns in the console that the file has moved, and creates a new Githubissues.
Githubissues is a development platform for aggregating issues.
I've noticed that you've removed the p5.play.js file and moved the p5Play JS file to p5play.js. All that's there in p5.play.js is a throw telling the user that the developer needs to change files. Moving to a different file is fine, but the way that it's currently done breaks existing projects that use p5.play.js.
I know GitHub Pages doesn't support server-side redirects, so as an alternative, I've crafted an alternative p5.play.js file that warns in the console that the file has moved, and creates a new Githubissues.