Confusing statement on project/external-modules.md

[lifenautjoe]

As seen here

Import type only

The following statement:

import foo = require('foo');

actually imports two things:

• The type information from the imported file.
• Takes are runtime dependency on the foo module.

You can pick and choose so that only the type information is loaded and no runtime dependency occurs. Before continuing you might want to recap the declaration spaces section of the book.

What does the second list item meant? Perhaps it should be

• The runtime dependencies on the foo module

If it is what was meant with the statement, I'll submit a PR .

[basarat]

Takes are runtime dependency on the foo module.

i.e. the current file cannot work unless foo is loaded first

[lifenautjoe]

I believe the statement doesn't make sense grammatically, I have consulted with a few colleagues which are native english speakers and also find it confusing.

The sentence should be read as an extension of actually imports two things:, meaning read as

actually imports two things: Takes are runtime dependency on the foo module.

I believe it should still be rephrased.

[basarat]

I believe it should still be rephrased.

Agreed 🌹 How about:

Actually does two things:

• Imports the type information of the foo module.
• Specifes a runtime dependency on the foo module.

[lifenautjoe]

Way better! Make the Specifes a Specifies and good to go 😄 , should I change it or do you have time?

[basarat]

I'll do it and reference 🌹