← Back to context Comment by ATechGuy 3 hours ago Curious to know what made you DIY this? 5 comments ATechGuy Reply ashishb 3 hours ago Tell me a better alternative that allows me to run, say, 'markdown lint', an npm package, on the current directory without giving access to the full system on Mac OS? ATechGuy 3 hours ago sandbox-exec -f curr_dir_access_profile.sb markdownlint ashishb 2 hours ago So you have to install npm package markdownlint on your machine and let it run it's potentially dangerous postinstall step? 2 replies →
ashishb 3 hours ago Tell me a better alternative that allows me to run, say, 'markdown lint', an npm package, on the current directory without giving access to the full system on Mac OS? ATechGuy 3 hours ago sandbox-exec -f curr_dir_access_profile.sb markdownlint ashishb 2 hours ago So you have to install npm package markdownlint on your machine and let it run it's potentially dangerous postinstall step? 2 replies →
ATechGuy 3 hours ago sandbox-exec -f curr_dir_access_profile.sb markdownlint ashishb 2 hours ago So you have to install npm package markdownlint on your machine and let it run it's potentially dangerous postinstall step? 2 replies →
ashishb 2 hours ago So you have to install npm package markdownlint on your machine and let it run it's potentially dangerous postinstall step? 2 replies →
Tell me a better alternative that allows me to run, say, 'markdown lint', an npm package, on the current directory without giving access to the full system on Mac OS?
sandbox-exec -f curr_dir_access_profile.sb markdownlint
So you have to install npm package markdownlint on your machine and let it run it's potentially dangerous postinstall step?
2 replies →