-
-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
package.json is copied to the output directory #127
Comments
Yes, if user choose to use css, they won't need the package.json, but if they choose less, they need it. |
I understand that a user will need a package.json in general, in order to install and run a less-compiler. My question was what is the need to have a package.json in the output directory, in addition to the root package.json. |
Oh, we no nedd the package.json in the output directory |
Good to know, I will take a look how it can be excluded from the build, then. |
package.json and package-lock.json files are copied to the output (
bin/Debug/net6/
) directory whennpm run start
is executed. They are also copied to thedist/
directory whennpm run build
is executed.This produces an unnecessary clutter in the VSCode NPM Scripts section:
Is there any need for these files to be in the output folder? Can they be excluded from the build?
The text was updated successfully, but these errors were encountered: