-
-
Notifications
You must be signed in to change notification settings - Fork 682
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fetching latest p5.js code from npm #501
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for working on this, @endurance21 !
I'm wondering if we should re-add p5.js (and p5.min.js) to the git repo as part of this PR? They were removed in #483.
I'd prefer to figure out how to avoid checking those files into the repo and to just let npm install those files when we need them:
- for local development (which this PR handles 🎉 )
- for automated testing (I believe we're also covered by the post-install script here?)
- and for gh-pages (this one I'm not sure about)
We could look at gh-pages as a separate ticket if you'd prefer to focus on the install script with this PR. We could use a library like this https://www.npmjs.com/package/gh-pages to publish just what we need to the gh-pages branch, without checking it into the main branch. For this PR, I'd say either add both files (p5.js and p5.min.js), or don't add either of them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we nixing this for a smaller pr?
* modifications in postinstall script * removed p5.js file
@therewasaguy @kyle1james it's good to go now ! |
#484
some highlights
installing latest p5 from npm version "1.0.0"
post-install Scripts :