Failing when starting my app
See original GitHub issueHello, i recently start having this error, when my app starting
TypeError: Cannot read property '1' of null at Object.FileStreamRotator.getStream (/var/www/html/app/node_modules/winston-daily-rotate-file/node_modules/file-stream-rotator/FileStreamRotator.js:396:38) at new DailyRotateFile (/var/www/html/app/node_modules/winston-daily-rotate-file/daily-rotate-file.js:81:57)
dependencies from package.json
"winston": "^3.0.0-rc6", "winston-daily-rotate-file": "^3.2.1", "winston-transport": "^4.2.0"
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
6 key reasons why a new app fails - Retail Dive
Reason #1: The app does not meet your customers' needs · Reason #2: Failure to define your business goals with the app—upfront ·...
Read more >Fix an installed Android app that isn't working - Google Support
Try the following steps if an app installed on your phone has any of these problems: Crashing. Won't open. Won't respond. Isn't working...
Read more >Why Apps Fail: 6 Prominent Reasons & How To Avoid Them
Another major reason for why apps fail is that they often simply aren't original. The truth is, app stores are oversaturated with similar...
Read more >How to Turn Your Mobile App Failure into Success - BuildFire
Take a step back. Look at yourself honestly and figure out if you were the reason why the app failed. Don't blame others...
Read more >10 Major Causes That Lead to Mobile App Failure
Unoptimized apps result in a loss of interest from the audience. Poor optimization is one of the reasons why mobile apps fail. App...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I also faced this issue and looks like defect introduced in file-stream-rotator v0.3.0. However v0.2.1 of the same package works perfectly.
winston-daily-rotate-file latest release is dependent upon file-stream-rotator 0.3.0 and hence this issue.
For now, to fix this issue, in my package.json, I have hard wired winston-daily-file-rotate to 3.1.3, it works file. This version depends upon 0.2.1 of file-stream-rotator, which works fine. You can try removing “^” from version 3.2.1 and check. If that does not work, then use version 3.1.3 without ^
Hope this helps…
Thank you for the help. I’ve updated dependency and push
winston-daily-rotate-file@3.3.2
to npm.