Skip to content
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

Code in NPM registry is not latest #50

Open
seriflafont opened this issue Oct 19, 2020 · 4 comments
Open

Code in NPM registry is not latest #50

seriflafont opened this issue Oct 19, 2020 · 4 comments

Comments

@seriflafont
Copy link

The js that is downloaded via npm install does not match the latest in the repo... can this please be fixed? The 'equals' and the 'pattern' both have issues in the version in the registry but they work great on the demos using the most current code. Our project relies on the registry as part of the build process for 3rd party code. Thanks in advance!

@t0byman
Copy link

t0byman commented Oct 23, 2020

Yes, please fix this. When I download your package via NPM the addMessages and setLocale functions aren't in there!

@zecompadre
Copy link

still missing latest version on NPM and jsdelivr

@kevinmu17
Copy link

Here's a "fix" "pristinejs": "git+https://github.com/sha256/Pristine.git" Use this in your package.json and rerun npm install

@sha256 you left this repo for dead?

@manifestinteractive
Copy link

manifestinteractive commented Jan 29, 2022

Agreed. Looks like the author just forgot to bump their NPM package version in package.json and publish the new version, which is why we are getting the old code via npm install pristinejs. The README was correctly updated though, making it reference functions in NPM on the NPM website that don't actually exist. Must use @kevinmu17 solution until resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants