Skip to content

—watch cli option prevents Worker execution  #56163

Open
@dandre3000

Description

@dandre3000

Version

v20.17.0

Platform

Microsoft Windows x64 [Version 10.0.19045.5131]

Subsystem

No response

What steps will reproduce the bug?

// main.js
import { Worker } from ‘worker_threads’

const w = new Worker(‘./worker.js’)
w.on(‘message’, event => console.log(event))

// worker.js
import { parentPort } from ‘worker_threads’

parentPort.postMessage(‘ayo’)

How often does it reproduce? Is there a required condition?

In terminal: node ./main.js —watch

What is the expected behavior? Why is that the expected behavior?

The worker should send a message to the main thread.

What do you see instead?

No response from the worker.

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    watch-modeIssues and PRs related to watch modewindowsIssues and PRs related to the Windows platform.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions