-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Open
Labels
area-blazorIncludes: Blazor, Razor ComponentsIncludes: Blazor, Razor ComponentsbugThis issue describes a behavior which is not expected - a bug.This issue describes a behavior which is not expected - a bug.
Milestone
Description
Is there an existing issue for this?
- I have searched the existing issuesTo pick up a draggable item, press the space bar. While dragging, use the arrow keys to move the item. Press space again to drop the item in its new position, or press escape to cancel.
Describe the bug
With version 9.0.0
of the NuGet package Microsoft.AspNetCore.Components.CustomElements
, 3 config files are being added as Content
.
In combination with Microsoft.TypeScript.MSBuild
, that leads to the following error when building:
tsc error TS18003: Build:No inputs were found in config file 'C:/Users/luis/.nuget/packages/microsoft.aspnetcore.components.customelements/9.0.0/contentFiles/any/net9.0/js/tsconfig.json'. Specified 'include' paths were '["**/*"]' and 'exclude' paths were '[]'. [C:\Users\luis\source\repos\Trumpf\LDM_Editor_SDK\src\EditorSdk.OAppSdk\TL.LDM.EditorSdk.OAppSdk.csproj]
I don't believe, these 3 files should be included as Content
.
Expected Behavior
The mentioned files should not be added to Content
.
Steps To Reproduce
- Create a Blazor WebAssembly App
- Add
Microsoft.AspNetCore.Components.CustomElements
Exceptions (if any)
No response
.NET Version
9.0.100
Anything else?
No response
Bouke and a7son
Metadata
Metadata
Assignees
Labels
area-blazorIncludes: Blazor, Razor ComponentsIncludes: Blazor, Razor ComponentsbugThis issue describes a behavior which is not expected - a bug.This issue describes a behavior which is not expected - a bug.
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
Mindstyler commentedon Dec 4, 2024
i just ran into the same isue
Aeroverra commentedon Jan 10, 2025
Anyone have a solution to this? Im new to typescript and Don't have the time to go down a rabbit hole right now.
Edit: Marking them as none worked.
FreyLuis commentedon Jan 10, 2025
@Aeroverra you can remove those config files by adding the following content remove to your csproj file and setting
GeneratePathProperty
to true for the CustomElements nuget.AshleyGrant commentedon Jun 9, 2025
I just ran into this issue today. @javiercn without workarounds this Nuget package is broken currently, and the only way I found this issue with the workarounds was coming to the aspnetcore repo and searching the issues prior to filing a new issue. Is this going to be fixed?