You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 21, 2022. It is now read-only.
I love this project very much, but I'm unable to find the time to work on it to the degree that I would like. I've been effectively been keeping this project in "maintenance mode" over the last 6-ish months, as I'm sure many of you have noticed.
This post is not me saying that this project is abandoned, it's the opposite. I still believe in its mission, I continue to use @pika/pack in my existing and new projects, and I only want it to succeed and grow. With the introduction of ESM support in Node.js, the ability to abstract away all of the complexity of package creation & configuration is more important today than ever.
Features that have been discussed but not yet build:
multi-package entrypoint support
a watch mode
export map support for Node v12+
So this post is a request to the community: would anyone be interested in taking over lead maintenance & leadership of the @pika/pack project? This would start with working on some projects in the repo to get a feel for the project and how it's built, but down the road if if someone were interested in sustained ownership/maintenance over a longer period of time I would also be happy to give over the reigns to the project entirely. I think this is what would be best for the project.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I love this project very much, but I'm unable to find the time to work on it to the degree that I would like. I've been effectively been keeping this project in "maintenance mode" over the last 6-ish months, as I'm sure many of you have noticed.
This post is not me saying that this project is abandoned, it's the opposite. I still believe in its mission, I continue to use @pika/pack in my existing and new projects, and I only want it to succeed and grow. With the introduction of ESM support in Node.js, the ability to abstract away all of the complexity of package creation & configuration is more important today than ever.
Features that have been discussed but not yet build:
So this post is a request to the community: would anyone be interested in taking over lead maintenance & leadership of the @pika/pack project? This would start with working on some projects in the repo to get a feel for the project and how it's built, but down the road if if someone were interested in sustained ownership/maintenance over a longer period of time I would also be happy to give over the reigns to the project entirely. I think this is what would be best for the project.
The text was updated successfully, but these errors were encountered: