Open cewert opened 1 year ago
One of the unused variables is from a roku module that we import during npm install
- the api module.
This issue points out the downside of using roku modules - we lose control of them and they don't have to pass through our CI checks. At the very least we should be using specific versions of these modules and only upgrading them once we approve of the changes. Right now though, these modules are set to automatically update to the latest minor/build version without any approval (that's what the caret means in package.json).
This seems like a huge design flaw in our app IMO. The roku modules aren't owned by the Jellyfin org and present a potential security risk if the repos were to fall in the wrong hands. It also makes it so we can't run or test the app without running npm install
or else we will be missing files.
Edit: What are the benefits to us using roku modules for our app? Like I know the NPM modules could potentially help other people make a Roku app, but what is the advantage to us? I don't see any advantages only downsides.
Is your feature request related to a problem? Please describe
While testing the latest version of unstable, I noticed there are several compile warnings displayed when deploying the app in vscode (hitting F5).
I don't understand why the app appears to be compiled twice with different warnings and compile times.
I also don't understand why we are seeing warnings for unused variables during compile time when our CI is supposed to be flagging unused variables as errors
Describe the solution you'd like
Only compile once and have zero compile warnings
Additional context