Issue with strict mode
See original GitHub issueHello,
Currently starting a CI on Codeship using winston. Using babel.
Whenever I try to run my tests i get a
Warning: api/node_modules/winston/lib/winston/common.js: Invalid number (367:30) Use --force to continue.
This might be related to the Octal litteral at 367:30. Fixing this pops another error, also relating to strict mode, about callee, caller and arguments. No line passed to the error stack.
Issue Analytics
- State:
- Created 8 years ago
- Comments:11 (4 by maintainers)
Top Results From Across the Web
Strict mode in JavaScript - GeeksforGeeks
Strict Mode was a new feature in ECMAScript 5 that allows you to place a program, or a function, in a “strict” operating...
Read more >Strict mode - Angular
Angular CLI creates all new workspaces and projects with strict mode enabled. Strict mode improves maintainability and helps you catch bugs ahead of...
Read more >Turning off Strict Mode in Angular? - Stack Overflow
Following Angular doc, the strict mode can be disabled turning off these flags on tsconfig.json file:
Read more >Why to and How To Use Strict Mode in Angular Applications
For sure I took a look at the tsconfig.json and found the reason for these problems — the strict mode was not enabled....
Read more >What Is Strict Mode In TypeScript, Why And When You Should ...
Strict mode constricts you in ways of writing your code. On other hand, you won't choose the way that will bring you to...
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
same issue.
+1 really need this to work in strict mode as well.
To reproduce just try creating a winston.js file with the following content:
and run it using:
You get:
Quick fix (in case this doesn’t get released soon), add winston to your package json like this and run
npm install
:This pulls the master version which works with
--use-strict
(no issues noticed).