This repository has been archived by the owner on Feb 11, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 160
pepjs npm package is unusable #223
Milestone
Comments
That package is supposed to contain the The Other than figuring out why the |
jzaefferer
added a commit
to jzaefferer/PEP
that referenced
this issue
Sep 30, 2015
See #224 for a fix. |
Fantastic, thank you! |
jzaefferer
added a commit
to jzaefferer/PEP
that referenced
this issue
Oct 2, 2015
The entry in .gitignore tells npm to also ignore the dist/ folder, adding it to files overrides that. It also excludes everything else, so we add some more useful files explicitly. Fixes jquery-archive#223
WestonThayer
pushed a commit
to WestonThayer/framer-pep
that referenced
this issue
Oct 7, 2015
Includes a local version of pepjs.js 0.3.0 because of jquery-archive/PEP#223. Will remove and reference the npm package when that's fixed. Haven't tested with Framer Studio yet, only framer-cli.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
https://www.npmjs.com/package/pepjs
The package seems to just be a clone of this git repo. If I wanted to use pepjs in my application, I would either have to:
import
and directly referencepointerevents.js
It would be much more helpful if the pepjs npm package simply contained a copy of https://code.jquery.com/pep/0.3.0/pep.js. It's CommonJS compatible, so it can be easily incorporated without having to use option 1 or 2.
I'd be happy to submit a pull request fixing this for package.json, but wanted to check here first to ensure that I'm not off-base with this issue.
The text was updated successfully, but these errors were encountered: