Getting started with problems

I wanted to be smart and set up things on my own. First, I grabbed this. Seems nice, but rewriting code from a video is too inconvenient and downloading the ready stuff is NOT as free as the video… Then I went here. It looks very similar but is an article. Unfortunately, I got stuck when trying to start the application after installing the concurrently package because:

error TS18003: No inputs were found in config file ‘<mypath>/Addregator/tsconfig.json’. Specified ‘include’ paths were ‘[” **/*”]’ and ‘exclude’ paths were ‘[“node_modules”,”bower_components”,”jspm_packages”]’.

The solution here says that adding some .ts file helped, but in the tutorial there is none and they say it works. And even when I added an empty .ts file, I got a bunch of additional errors (this is only an excerpt):

node_modules/@types/core-js/index.d.ts(1280,36): error TS2339: Property ‘for’ does not exist on type ‘SymbolConstructor’.
node_modules/@types/core-js/index.d.ts(1284,43): error TS2339: Property ‘hasInstance’ does not exist on type ‘SymbolConstructor’.
node_modules/@types/core-js/index.d.ts(1288,50): error TS2339: Property ‘isConcatSpreadable’ does not exist on type ‘SymbolConstructor’.

On the other hand, there is an issue on GitHub, whose status is open… How lovely. And I found yet another tutorial which suggested cloning some boilerplate from GitHub just like the official one. So the world seems to be against me and now I’m obediently going back to the only politically correct version, which is basing on the project template from the official page.


2 thoughts on “Getting started with problems”

  1. I saw both the errors you got: TS18003 and TS2339. I also did not find a solution after hours of trying. Because of this, every time I change a ts or tsx file, I must manually recompile.

    Sad how brittle and painful Typescript development is even in 2018! The Internet is full of posts about these same problems (for years) from people using VisualStudio, IntelliJ, or the command line. If the main IDE companies can’t make Typescript work smoothly and efficiently, does a non-expert web developer have any hope?

    Thought I made some progress learning Typescript, I feel it cannot be trusted for a professional webapp. New problems are always appearing. There no good sources of help or fixes for Typescript tool chain and other problems. Bugs are opened, but not fixed. However, the bugs are often closed with no answer for “housekeeping” reasons:-(

    After six frustrating months with Typescript, it’s time to try Facebook’s Flow for Javascript data typing.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s