Closed binajmen closed 2 years ago
Thinking out loud: should we enable dependabot for stacks?
@machour I know @kentcdodds isn't a fan of using @dependabot, although I think it can be valuable tbh.
@binajmen I just updated all dependencies in #25 (did this for all stacks), but I still get these 4 severity vulnerabilities warnings, so nothing else we can do for now I'm afraid 🤷♂️
@MichaelDeBoey no problem on my side. As I suppose these kind of warnings will trigger future remix'ers, it is still good to acknowledge it here.
It seems to be a false positive anyway: https://github.com/sindresorhus/trim-newlines/issues/8#issuecomment-879693347
No, it's not serious. It's just a "vulnerability" that may affect 0.0000001% of users, but waste the time of everyone.
I leave it to you to decide whether or not you want to keep the issue open ;)
@binajmen Strange, as I still get them when removing node_modules
& package-lock.json
and running npm i
🤔
By false positive, I meant "classified as not a serious vulnerability" by the author.
This is supposed to be a 4 lines package 😄 https://github.com/sindresorhus/trim-newlines/commit/25246c6ce5eea1c82d448998733a6302a4350d91
The issue is not with the blues stack but with transitive dependencies. We can't do anything about those in this repo, so I'll close this issue. Feel free to open PRs in the deps to fix these issues.
@binajmen I've created a PR to remove the unused chalk-animation
dependency, which is causing this warning: https://github.com/remix-run/remix/pull/2547
https://github.com/remix-run/remix/pull/2547 is merged, so it will be released when 3.4.0
gets released.
Once that's done, we'll update the package-lock.json
of all stacks, which should fix these warnings
What version of Remix are you using?
latest via
npx create-remix
Steps to Reproduce
Run
npx create-remix --template remix-run/blues-stack
in consoleExpected Behavior
No severe warnings
Actual Behavior