-
Notifications
You must be signed in to change notification settings - Fork 77
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
Publish to npm #29
Comments
I was unaware that simplify-scorm was published to NPM. It was not published by us, I have no idea what version was published, but version 0.0.1 was never a thing. It looks like it was published 24 days ago, but it only has SCORM 1.2 support, so it's much much older than the code that existed 24 days ago, as we have SCORM 2004 support. The NPM package is not supported by us, we do not condone the use of it. We have an issue opened here asking us to publish to NPM, issue #20. We still have not worked towards it though. I guess now we are kind of forced to do something about it though. |
Do you have some ETA on your mind ?? |
I do not have an ETA, no. I have reached out to the person who published the package to npm, asking them to add me as a maintainer or hand over control of the package. We'll see if / when they get back to me. In the meantime, could you help me understand exactly how one would use the npm package? I'm used to simply adding the js file to my project and loading it using a <script> tag, I need some help to understand why people want it on npm, what the packaged version would do, how you would want to use it, etc. |
So I saw there is a mismatch between the npm version and the version here. If it is npm, managing the dependency would have been easier plus the security provided by the npm. |
Installing via npm is still giving 0.0.1. This ticket is to make a new publish to npm.
The text was updated successfully, but these errors were encountered: