Skip to content

Transfer the Multer package to the express organization on NPM. #337

Closed

Description

@bjohansebas

This is just a reminder that the Multer package has not been transferred to the Express organization.

https://www.npmjs.com/org/expressjs

cc: @expressjs/express-tc

Activity

  1. added
    top priorityIssues which the TC deem our current highest priorities for the project
    on Feb 19, 2025
  2. UlisesGascon commented on Feb 19, 2025

    @UlisesGascon
    Member

    It will be great to do a deep review, just in case that we are missing other packages 🤔

  3. bjohansebas commented on Feb 19, 2025

    @bjohansebas
    MemberAuthor

    Good idea, I can do it this afternoon when I get home

  4. bjohansebas commented on Feb 19, 2025

    @bjohansebas
    MemberAuthor

    These are the packages that are in npm but are not in the npm organization, yet their repositories live in one of the three GitHub organizations we have.

    api-error-handler
    connect-markdown
    connect-rid
    domain-middleware
    express-expose
    express-namespace
    express-paginate
    flash
    multer
    restful-router
    urlrouter
    extend-proto
    re2js-legendary
    templation
    spdy-push

  5. wesleytodd commented on Feb 20, 2025

    @wesleytodd
    Member

    Some of this we need to just deprecate. We can archive many of the repos I think as well.

  6. LinusU commented on Mar 20, 2025

    @LinusU
    Member

    Which Team should own multer? Should I create a pkg_multer team?

    Image

    edit: there was already a pkg_multer team, I think I managed to add the package! 🎉

    Image

    (the UI for the teams is a bit clunky 😅)

  7. bjohansebas commented on Mar 20, 2025

    @bjohansebas
    MemberAuthor

    Now that multer is already in the npm organization, what are we going to do with the rest of the packages that are not in the organization? Even if they are not important, they are in our GitHub organization, which means we should have control to deprecate them on npm if we want to.

  8. ctcpip commented on Mar 31, 2025

    @ctcpip
    Member

    this is done! 🙏

  9. bjohansebas commented on Apr 1, 2025

    @bjohansebas
    MemberAuthor

    @expressjs/express-tc what is the decision on the other packages?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    tc agendatop priorityIssues which the TC deem our current highest priorities for the project

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions