{"push_id":915213521,"size":1,"distinct_size":1,"ref":"refs/heads/feature/npm-change-cwd","head":"97373a2d02b63a9a95c225d9aa1c2ce5101716c2","before":"2c007545124f004d5e7b447db55174dee00ee4a9","commits":[{"sha":"97373a2d02b63a9a95c225d9aa1c2ce5101716c2","author":{"email":"735abbb1be438b4a5a87e3490ac5953995c247f2@gmail.com","name":"eljefedelrodeodeljefe"},"message":"Feature: change `cwd` for `npm run script`\nThis commit adds the above mentioned feature by checking whether the package\nJSON includes a scriüt in the form of\n```\n{\n}\n```\nIt then attaches a un-enumerable array to the `scripts` objects, which the `npm`\nclient can check for during execution.\nFrom the `npm` client's POV, this seems a little odd since it needs to transform\na lot. But in order to pass hard checks here and w/ `npm` and not to break, this\nseemed to be necessary for the author.\n*Background:*\nthis in greater detail. Fundamentally though, this for enabling `npm` to be more\nof a build tool. For example some programs such as make don't allow non-cwd\nruns. And in order to not `cd` to it, this is supposed to greatly help.","distinct":true,"url":"https://api.github.com/repos/eljefedelrodeodeljefe/read-package-json/commits/97373a2d02b63a9a95c225d9aa1c2ce5101716c2"}]}