Build error
See original GitHub issueI fetched the latest changes. I get this error when I try to build:
Property 'metaKey' does not exist on type 'KeyboardEvent | React.KeyboardEvent<Element>'
This is building a copy of master. No local changes, except cross-env
added in package.json to these two lines:
"build:app:docker": "cross-env REACT_APP_DISABLE_SENTRY=true react-scripts build",
"build:app": "cross-env REACT_APP_GIT_SHA=$VERCEL_GIT_COMMIT_SHA react-scripts build",
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (4 by maintainers)
Top Results From Across the Web
Project build errors and warnings (PRJxxxx) - Microsoft Learn
The Visual Studio compilers and build tools can report many kinds of errors and warnings. After an error or warning is found, the...
Read more >Fix a build error
Fix a build error · Right-click anywhere in the Error List window. · Select Copy List. · Open Microsoft Excel or Word (or...
Read more >BUILD Error Messages - IBM
BUILD Error Messages. The messages in the pop-up panel showing the command progress indicate error and warning situations. In most cases, it should...
Read more >Oh dear! Build errors? - LoopDocs - GitHub Pages
This page contains build error help for people updating their Loop app as well as brand new Loop app builders. Review the "obvious"...
Read more >Remove "There were build errors. Would you like to continue ...
FYI. In Visual Studio 2019 Update 16.5 or later you can go to Tools > Options > Projects and Solutions > Build and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I updated node to 16.13 and that resolved the issue. Sorry for the false alarm.
I think the root cause is that it seems it’s been years that I’ve updated node. I am installing the latest and will see.