Skip to content

Conversation

@RezaRahmati
Copy link
Contributor

Description

Fixing #829

Code sample

@samtstern
Copy link
Contributor

@RezaRahmati thank you for this PR! I can confirm the behavior you described:

> const x = undefined;
undefined
> `${x}`
'undefined'
> `${process.env.NONSENSE}`
'undefined'
> process.env.NONSENSE || 'foo'
'foo'

Assigning to @joehan to approve and merge.

@samtstern samtstern requested a review from joehan January 5, 2021 10:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants