Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Several instances of webpack #11

Closed
sochix opened this issue Jan 15, 2016 · 4 comments
Closed

Several instances of webpack #11

sochix opened this issue Jan 15, 2016 · 4 comments

Comments

@sochix
Copy link

sochix commented Jan 15, 2016

Hi! I bind webpack -watch to solution open event. Every time I'm open a solution i get a new instance of webpack watch. Can it be only one instance?

@madskristensen
Copy link
Owner

I'm not sure I understand. When binding to project open, a process is kicked off running webpack watch. When you close the solution or VS then that process is terminated. Is that not what you experience?

@sochix
Copy link
Author

sochix commented Jan 16, 2016

Nope. When you update your project from version control system visual
Studio triggers open project event and I get two running instances of
webpack. The same will happen if you click unload on project and load it
again.
15 янв. 2016 г. 19:42 пользователь "Mads Kristensen" <
[email protected]> написал:

I'm not sure I understand. When binding to project open, a process is
kicked off running webpack watch. When you close the solution or VS then
that process is terminated. Is that not what you experience?


Reply to this email directly or view it on GitHub
#11 (comment)
.

@scottaddie
Copy link
Collaborator

@sochix I am definitely able to reproduce this myself. I opened the project, which already had the "Watch - Development" task bound to Project Open. I then unloaded the project and then reloaded it from Solution Explorer. At that point, I had 2 "Watch - Development (running)" tabs in TRX.

@madskristensen I would expect the aforementioned "Watch - Development" task to terminate when the project is unloaded. That would solve the problem of 2 running instances. Thoughts? I have logged issue aspnet/Tooling#373 for this, as it appears to be a core TRX bug.

@madskristensen
Copy link
Owner

Correct, this is a bug in TRX. Thanks for opening the bug. I'll close it here since it has to be fixed by VS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants