Sorry for the inconvenience caused.
We have rolled out a new release on July 1st which caused this problem. Our new version has lot of breaking changes and I recommend you to go through these changes
before you migrate to the new version.
Important changes have been done in naming convention for consistency with Blazor framework:
NuGet Package name is changed to - Syncfusion.EJ2.Blazor
Namespace name is changed to - Syncfusion.EJ2.Blazor
Syncfusion Blazor components have been upgraded to .NET Core 3.0 Preview 6 from 17.1.51. If you are using older than .NET Core 3.0 Preview 6, then you would need to make some code syntaxes and configurations to be updated as per the following blog. Please ensure that you update them too before you run your application in .NET Core 3.0 Preview 6.
However, if you want to stay with the older version, ensure that you refer to the version specific scripts which is equivalent to the NuGet version.
- Version specific script location
Please let me know if this helps.