Modern Full-Stack Development

 Where the Action Is: PlayerBoard.tsx
The PlayerBoard component is what you see on the left-hand side of the screen and is 
where the player plays the game. It begins with some imports, as always:
import React, { CSSProperties, ReactElement } from "react";
Oh, but look, we have two new ones: CSSProperties and ReactElement. Keep those 
in mind, as we’ll see them in use soon, and I’ll explain what they’re all about then.
Before that, though, we have a series of imports, 42 of them to be precise, and that 
number should ring a bell:
import tile101 from "../../img/tile101.png";
import tile102 from "../../img/tile102.png";
...40 more...
Chapter 11   time for fun: BattleJong, the Client

---

320
Yes indeed, one for each image! As you’ll recall, Webpack will include our images 
as Base64-encoded strings in the final bundle and will also wrap them up in a module 
definition. That’s why we can import them here. It may seem weird to import images – 
and I’d agree it is! – but essentially, at this point, they are code, and we’ll be using them 
as such. But, before we can, we must solve for one small problem, and it’s where the d.ts 
file comes into play.