search

wclr / yalc

Work with yarn/npm packages locally like a boss.
MIT License
5.64k stars 147 forks source link

Is this project still active? #212

Open gpalsingh opened 1 year ago

gpalsingh commented 1 year ago

Hi, I was just wondering if the project is still active and if there are any plans for future development

wclr commented 1 year ago

What development? What features are you lacking?

JordanAdams commented 1 year ago

What development? What features are you lacking?

I suspect this question arose from there being a number of open issues and PRs with little movement. I'm certainly not one to suggest that open source developers have any obligation to maintain or continuously work on their projects; however it's a totally fair to question to ask if the project is still active.

wclr commented 1 year ago

@JordanAdams Do you have anything concrete to say, are there any issues you are waiting to be addressed?

Answering the question Is this project still active, yes it is.

JordanAdams commented 1 year ago

@wclr Not really sure why you have such a defensive response to a simple observation, particularly when I was defending you. But thank for you for the clarification ❤️

wclr commented 1 year ago

@wclr Not really sure why you have such a defensive response to a simple observation, particularly when I was defending you. But thank for you for the clarification ❤️

Ha, sorry, I've missread your message. 🤝

quantuminformation commented 1 year ago

@wclr I wonder if we still need yalc, given that pnpm link will work on windows computers using the linux subsystem (WSL)?

wclr commented 1 year ago

@quantuminformation I don't know if you need it or no, I use yalc to avoid cross projects symlinks while making a package accessible to multiple dependants in more stable manner.

jkhartshorne commented 1 year ago

I was wondering the same thing and for the same reason (lots of open PRs). Glad to know it is being maintained, since I use it! I was worried I needed to migrate to something else.

stellarhoof commented 1 year ago

@wclr Perhaps you can designate someone to help merging PRs and resolve issues. As it is, there are outstanding bugs that will probably never get resolved.

coopbri commented 1 year ago

Hi everyone, I decided to create an active fork of this project (called "knit") to breathe some new life into it.

Still getting a feel for the codebase, but so far I revamped the CI, updated the documentation, upgraded the dependencies, and some other minor updates.

Nantris commented 12 months ago

I'd love to have auto-push functionality but it seems like that idea was shut down because we can use nodemon, but that's a pain compared to having a more out-of-the-box approach.

That's the only additional feature I'd like to see. @wclr and @coopbri. Then yalc would offer the workflow of yarn link with the benefits of yalc.

coopbri commented 12 months ago

I'd love to have auto-push functionality but it seems like that idea was shut down because we can use nodemon, but that's a pain compared to having a more out-of-the-box approach.

That's the only additional feature I'd like to see. @wclr and @coopbri. Then yalc would offer the workflow of yarn link with the benefits of yalc.

What about yalc/knit publish? Does that suit your needs?

Nantris commented 12 months ago

I don't mind needing to run the publish command once - it's the problem of running a command whenever I make a change that's troublesome for me. The promised workflow of yarn link is what I'm after, at least as close to it as possible.

The use case is that we have two packages outside of a monorepo which we're working to integrate and it involves expanding the API on one project and using it on the other. Needing to run to the terminal in-between editing files does not bring joy.