So I run “box install” in a directory with an existing box.json and it is asking me for a slug to install.
My box.json looks like this (certain names changed to “myproject”):
{
“name”:“myproject”,
“version”:“2.6.2”,
“author”:“Sean Coyne my@email.com”,
“location”:"",
“directory”:"",
“Homepage”:“https://myproject.org/”,
“Documentation”:“See README.md”,
“Repository”:{
“type”:“git”,
“url":"git@bitbucket.org:seancoyne/myproject.git”
},
“Bugs”:“https://bitbucket.org/seancoyne/myproject/issues”,
“slug”:“myproject”,
“shortDescription”:“My Project”,
“description”:“My Project”,
“instructions”:“See README.md”,
“changelog”:“See README.md”,
“type”:“application”,
“keywords”:[
],
“private”:true,
“engines”:[
{
“type”:“adobe”,
“version”:">=9.0.1"
}
],
“defaultEngine”:“adobe”,
“defaultPort”:80,
“ProjectURL”:“https://myproject.org/”,
“License”:[
{
“type”:“NONE”,
“url”:""
}
],
“Contributors”:[
],
“Dependencies”:{
},
“DevDependencies”:{
“mockbox”: “3.0.0.00028”
},
“ignore”:[
“logs*”,
“readme.md”
],
“PACKAGENAME”:“myproject”
}
Now, since “box install mockbox --saveDev” is not working for me (see my other thread) I took a stab at guessing what the devDependencies object syntax should look like. I created the box.json with “box init” then updated the values.
So, first question is the syntax I used for the devDependencies object correct? If not what should that look like? (I assumed it was npm-like and looking at the commandbox source seems to have confirmed this)
Second question, shouldnt “box install” see the box.json and not ask for a slug?
Thanks
I watch the repo on github and keep my fork up to date so I see when the changes are made. For the --flag syntax, I did see you added that, but today when I tried it I just assumed it was “npm-like” and tried it. Then when it didn’t work I dug into the source code and found that it should have been working.