Closed JonPSmith closed 8 years ago
OK, I found what is different between the two package.json files that fixes this.
If I remove line "private": true
from the package.json then my myTest
script works!
That's fine and I will continue like that, but for my own education I would like to know why, as I believe the default is for "private": true
.
It would also be great to get rid of the Defaults if I can, especially for the article.
It has nothing to do with private:true
. You made a typo by calling it karam instead of karma
Doh! Really sorry to have wasted your time. I should have seen that!
No worries :)
Installed product versions
Description
I have been using your npm task runner successfully for a week or two with a number of custom commands, like webpack build. All has been fine, but I added a new project with a different package.json file and one of the commands won't work. The steps are given below.
Note: The solution will go with a long article I am writing and as such is open-source the actual code can be found at JonPSmith/AspNetReactSamples, ReactTests.
A second minor issue, but one that I would also like to fix if I can, is that the Task Runner Explorer (TRE) window does not look the way you describe it, as it has a Default and Custom section (see point 2 below). It would be create to only have the scripts I have installed, especially for people who want to try it.
Steps to recreate
test
then it works, with the following logmyTest
it fails with the following logNotes
In the solution JonPSmith/AspNetReactSamples the project ReactWebPack.MVC5 works fine, but the project ReactTests does not. I can't see any difference in what I am doing.
Your help would be appreciated.