mike-works / vscode-fundamentals

👨‍🏫 Mike's Visual Studio Code Course
https://frontendmasters.com/courses/visual-studio-code/
BSD 3-Clause "New" or "Revised" License
201 stars 108 forks source link

Can't successfully start the project up due to TypeScript errors #255

Closed adrian-gray closed 5 years ago

adrian-gray commented 5 years ago

Start up log showing first 2 (of 180) TS errors

➜  vscode-fundamentals git:(master) npm start

> @mike-works/vscode-fundamentals@0.0.0-development start /Users/adriangray/work/fem/vscode-fundamentals
> node ./server/index.js

sequelize deprecated String based operators are now deprecated. Please use Symbol based operators for better security, read more at http://docs.sequelizejs.com/manual/tutorial/querying.html#operators node_modules/sequelize/lib/sequelize.js:242:13
(node:37187) DeprecationWarning: Tapable.plugin is deprecated. Use new API on `.hooks` instead
ℹ 「atl」: Using typescript@3.3.3 from typescript
ℹ 「atl」: Using tsconfig.json from /Users/adriangray/work/fem/vscode-fundamentals/tsconfig.json
ℹ 「atl」: Checking started in a separate process...
✖ 「atl」: Checking finished with 180 errors
   68 modules

ERROR in [at-loader] ./node_modules/@types/prop-types/node_modules/@types/react/index.d.ts:2307:19
    TS2320: Interface 'Element' cannot simultaneously extend types 'ReactElement<any>' and 'ReactElement<any, any>'.
  Named property 'type' of types 'ReactElement<any>' and 'ReactElement<any, any>' are not identical.

ERROR in [at-loader] ./node_modules/@types/prop-types/node_modules/@types/react/index.d.ts:2308:19
    TS2320: Interface 'ElementClass' cannot simultaneously extend types 'Component<any, {}, any>' and 'Component<any, {}, any>'.
  Named property 'props' of types 'Component<any, {}, any>' and 'Component<any, {}, any>' are not identical.
adrian-gray commented 5 years ago

NVM, it's working now.

I deleted node_modules and retried the installs with npm, same deal.

I deleted node_modules again, and rebooted. I then re-yarned the install, and this time it started successfully. I think it was the reboot that got it going.