pseidemann

hi @avelad, what is the reason for changing the bug report to a question?

@shaka-bot change to bug

hi @avelad, same problem. I've never encountered this issue with other node packages. I think there must be something wrong how shaka is packaged for npm.

hi @joeyparrish, thanks for looking into it! I'm wondering: why are these files referenced in the first place? I can't find these paths when I grep inside the node package....

correction: these paths _do_ exist inside the `*.map` files. I think that's the mistake. ``` node_modules/shaka-player $ grep -r -l 'src/com' . ./dist/shaka-player.ui.debug.map ./dist/shaka-player.compiled.debug.map ./dist/shaka-player.compiled.map ./dist/shaka-player.ui.map ```

gotcha. one reason why this is maybe more than an annoyance, is that the CRA/webpack stack doesn't allow to disable source maps for single packages. so the only way to...

the user will be able to use your protected api as long as the access token (or refresh token, depending on if you use it) is still valid (the tokens...

to be clear, you can still deny an user access to your api, even though there is a valid token. here is a good explanation: https://community.auth0.com/t/best-practice-for-checking-if-token-is-revoked-in-api/17460/2