Giter Site home page Giter Site logo

Comments (10)

UlisesGascon avatar UlisesGascon commented on April 27, 2024 1

I am working on it, thanks for the ping @drobnikj

from express.

UlisesGascon avatar UlisesGascon commented on April 27, 2024 1

I close the issue as this is now fixed. Thanks for the CLI tricks @jonchurch

Screenshot from 2024-03-21 09-47-00
Screenshot from 2024-03-21 09-47-21

from express.

fire015 avatar fire015 commented on April 27, 2024 1

Thanks, it just looked suspicious (you hear about NPM packages been hacked all the time) 👍

from express.

wesleytodd avatar wesleytodd commented on April 27, 2024

Was not on purpose. Just an oversight in a manual process being done for the first time in my part.

from express.

fire015 avatar fire015 commented on April 27, 2024

This is still visible on NPM fyi @wesleytodd @UlisesGascon

from express.

wesleytodd avatar wesleytodd commented on April 27, 2024
Screenshot 2024-03-25 at 9 23 42 AM

Not for me.

from express.

fire015 avatar fire015 commented on April 27, 2024

@wesleytodd Sorry what I meant was, is beta.2 supposed to be showing up at all in NPM considering there is no tag/release or changelog about it in this repo?

from express.

wesleytodd avatar wesleytodd commented on April 27, 2024

is beta.2 supposed to be showing up at all in NPM considering there is no tag/release or changelog about it in this repo?

Yes it was intentional to publish, just not without --tag=next. I added the releases on GH now (including the new one just published). Sorry for the confusion.

from express.

wesleytodd avatar wesleytodd commented on April 27, 2024

Yep! Thanks for checking!

from express.

jonchurch avatar jonchurch commented on April 27, 2024

Yep thanks for noticing and reporting @fire015

The impact this would have had during the couple of hours that latest pointed to v5 was that folks who npm i express would have gotten v5 beta instead of v4.

It also likely triggered some "hey there's a new major available" notices to folks.

because NPM lets you change where latest points without a republish, we just fixed it once we noticed by doing a
npm dist-tag add express@<version> latest to point to the correct v4 release

from express.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.