search

madskristensen / NpmTaskRunner

Visual Studio extension
Other
88 stars 32 forks source link

Is this project abandoned? #80

Closed dangrussell closed 3 years ago

dangrussell commented 3 years ago

Installed product versions

Description

It's too bad that this very useful extension seems to be abandoned.

It's still referred to in official Microsoft docs: https://docs.microsoft.com/en-us/visualstudio/javascript/compile-typescript-code-npm?view=vs-2019#automate-build-tasks

jwbats commented 3 years ago

Is this the repo for Task Runner Explorer on the VS Marketplace?

I'm asking because there's also a WebpackTaskRunner repo in @madskristensen's github now. Updated shortly after NpmTaskRunner. Are we supposed to use WebpackTaskRunner, instead?

Anyway... for me, Task Runner Explorer has stopped working. It's probably incompatible with a recent VS update. No more task configurations are found.

I'd love it if it would get fixed. Now I have to run these commands manually, in a terminal outside my VS.

madskristensen commented 3 years ago

No, the Task Runner Explorer (TRE) itself is built into Visual Studio. There are just extensions that extends TRE

jwbats commented 3 years ago

Yeah, I just found that out as well. I also seem to have task runner extensions and repos mixed up.

I'll just report the problem via VS Feedback.

jwbats commented 3 years ago

My issue submission on VS developer community.

alex-jitbit commented 3 years ago

So, can we have an answer if this is abandoned or not? It's OK if it is, just need to know.

The only reason my company stays away from npm-runner (and uses more old-school grunt/gulp) is because it's unclear whether this project has any future and/or official support form MS.

PS. although I guess even being an "official" MS product doesn't mean it can't be abandoned - just look at SignalR ;)

madskristensen commented 3 years ago

@alex-jitbit I still take pull requests and will publish new versions, but I don't actively work on this project beyond that.

jwbats commented 3 years ago

@alex-jitbit

The only reason my company stays away from npm-runner (and uses more old-school grunt/gulp) is because it's unclear whether this project has any future and/or official support form MS.

You can run your npm tasks in any terminal. VS has an in-built terminal as well. It might even be possible to have it start a task on startup.

NPM Task Runner only brings a little bit of added convenience. It's not mission critical.

alex-jitbit commented 3 years ago

@jwbats I know I can do everything manually :) but that's not how things should work. I need everything to happen automatically on project load, and I need the settings to propagate to other team members (and to CI/CD servers) seamlessly by just doing a git pull

jholland918 commented 3 years ago

FYI - I updated to Visual Studio 16.9.2 and the npm task runner project open bindings are now working for me.

jwbats commented 3 years ago

For me as well.

dangrussell commented 3 years ago

Thank you for the recent updates!