Daniel Bretoi
Daniel Bretoi
I just use ```bash #!/bin/bash export NVM_SYMLINK_CURRENT=true if [[ -s $HOME/.nvm/nvm.sh ]] ; then source $HOME/.nvm/nvm.sh; else echo "No nvm found in `$HOME/.nvm/nvm.sh`"; fi nvm $@ ``` And then add...
would it be easier to just have a list of paths in the plugin registration of what to exclude? Or is on a per-route basis better? Seems like more work...
What's the problem with having `/docs` and `/documentations` show up when they do exist? IOW, what's the use-case for hiding routes that do exist?
How are you blocking off the endpoints which are for internal use only then? If they're on a different connection, blipp will show it as being on the other connection....
@woolfi182 sorry for the delay. Can we change it to "exclude" as opposed to "excluded" ?
In the package.json, add `-I queueMicrotask` argument to the lab command. That will solve the issue :)
@woolfi182 I wonder if it will also be valuable to use pattern matching to exclude multiple routes. For example '/assets/*'
Also maybe some kind of marker to indicate them being internal when they are displayed too
I've just started looking a this so I'm unfamiliar with snet. Do you have a link to this "st" tool? thanks! :) -d
looks like S3 is cheaper anyway, so I'm looking at that now.