Skip to content

Don't overwrite global.process #40

@parshap

Description

@parshap

TcpSocket.js#L11 overwrites the process global. This causes existing process.env values to be lost. I think this library should leave it to the end-user to shim the global process object (example). Regardless, I don't think it should clobber existing process.env values as it causes the rest of my program, which depend on the process.env values, to fail.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions