No.
The reason is that this could be a security risk because some plugin files might contain sensitive information and whitelisting is better than blacklisting in this case.
You can however use a route in your plugin that serves the file. Instead of using the real URL in your plugin function, you can use something like url('my-plugin/assets/my-plugin.js')
.