Previously, the compiler would crash when binding a non-top-level property assignment on the symbol of an unresolved module: ```js import x from 'arglebaz' { x.bar = 1 } ``` That's because `x` looks like an alias but doesn't have a valueDeclaration (since there is no file named 'arglebaz'), and the new code for binding Object.defineProperty calls forgot to check for an undefined valueDeclaration. This change adds the checks for an undefined valueDeclaration. |
||
---|---|---|
.. | ||
compiler | ||
conformance | ||
fourslash | ||
project | ||
projects | ||
test262-harness | ||
unittests | ||
user |