Error thrown when running demo project
See original GitHub issueI tried to run the demo project, and I got an error saying “cannot use lexical scope value ‘Polygon’ before initialization’”. When I commented out import { Rectangle } from './Rectangle'
from packages/geometry/src/Polygon
the error went away. Not sure if this is intended or why this is happening.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Error monitoring and exception handling in large-scale ...
Learn how to handle errors and exceptions on large scale software projects, with best practices, tools and tips.
Read more >Android Studio new project can not run, throwing error
Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Could not...
Read more >Manage exceptions with the debugger in Visual Studio
When the debugger breaks, it shows you where the exception was thrown. You can also add or delete exceptions. With a solution open...
Read more >Build error throws when running dotnet pack with multiple ...
NET 6.0 preview 1 SDK, it throws build error when running dotnet pack command line. The problem is occur when the project file...
Read more >What is Exception Handling? - SearchSoftwareQuality
A catch statement is a group of statements that handle the specific thrown exception. Catch parameters determine the specific type of exception that...
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
it’s a circular dependency issue, potentially duplicate of #406 #437
workaround is to run in the root
_Originally posted by @stereobooster in https://github.com/projectstorm/react-diagrams/issues/406#issuecomment-534142125_
here is a good explanation and some solutions: https://medium.com/visual-development/how-to-fix-nasty-circular-dependency-issues-once-and-for-all-in-javascript-typescript-a04c987cf0de
Running build in the root is not a workaround, but the correct way of building this library