Is this project still active? about yalc HOT 13 OPEN

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

• Repo: https://github.com/coopbri/knit
• npm: https://www.npmjs.com/package/@omnidev/knit

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.

from yalc.

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.

from yalc.

@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.

from yalc.

@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 ❤️

from yalc.

@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. 🤝

from yalc.

@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.

from yalc.

What development? What features are you lacking?

from yalc.

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

from yalc.

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.

from yalc.

@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.

from yalc.

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.

from yalc.

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.

from yalc.

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?

from yalc.