The proper convention for doing a nuget packages is to compile it and then have those files be referenced. Not by injecting a file into the consuming project.
This is particularly bad if for any reason your source file and/or its conventions do not 100% agree with the project you're forcing it into.
It also gives less experienced users a sense that they can modify the file, when really they can't and shouldn't (otherwise it defeats the purpose of having a package).
The proper convention for doing a nuget packages is to compile it and then have those files be referenced. Not by injecting a file into the consuming project.
This is particularly bad if for any reason your source file and/or its conventions do not 100% agree with the project you're forcing it into.
It also gives less experienced users a sense that they can modify the file, when really they can't and shouldn't (otherwise it defeats the purpose of having a package).