Cannot use it on ReactJs ,

[vishwasrj]

# creating a simple winston variable and calling the log function from it shows the errors bellow

ERROR in ./~/winston/lib/winston/common.js
Module not found: Error: Cannot resolve module 'fs' in

ERROR in ./~/pkginfo/lib/pkginfo.js
Module not found: Error: Cannot resolve module 'fs' in <filepath>

ERROR in ./~/winston/lib/winston/transports/file.js
Module not found: Error: Cannot resolve module 'fs' in

[danieleleoni]

Same issue here!

[ultrafez]

fs is a Node module, so you'll need to use webpack or browserify which should polyfill it.

[bradisbell]

Using webpack... no polyfill for fs (which makes sense when you think about it... unless it were completely stubbed).

I get the following with Webpack:

WARNING in ./~/winston/lib/winston/transports.js
Critical dependencies:
23:17-34 the request of a dependency is an expression
 @ ./~/winston/lib/winston/transports.js 23:17-34

WARNING in ./~/colors/lib/colors.js
Critical dependencies:
127:29-43 the request of a dependency is an expression
 @ ./~/colors/lib/colors.js 127:29-43

WARNING in ./~/colors/lib/extendStringPrototype.js
Critical dependencies:
106:31-45 the request of a dependency is an expression
 @ ./~/colors/lib/extendStringPrototype.js 106:31-45

ERROR in ./~/winston/lib/winston/common.js
Module not found: Error: Cannot resolve module 'fs' in /vagrant/node_modules/winston/lib/winston
 @ ./~/winston/lib/winston/common.js 12:9-22

ERROR in ./~/pkginfo/lib/pkginfo.js
Module not found: Error: Cannot resolve module 'fs' in /vagrant/node_modules/pkginfo/lib
 @ ./~/pkginfo/lib/pkginfo.js 8:9-22

ERROR in ./~/winston/lib/winston/transports/file.js
Module not found: Error: Cannot resolve module 'fs' in /vagrant/node_modules/winston/lib/winston/transports
 @ ./~/winston/lib/winston/transports/file.js 10:9-22

[bradisbell]

If I use node: { fs: 'empty' } in my webpack.config.js, the errors go away (I'm left with the warnings), but the script doesn't work. Calls to try to read pkginfo are being made.

[shawnxusy]

@bradisbell I'd guess you are importing the winston in a browser environment, which winston is not supporting right now (see #582).
Even if you think your winston is imported in a server-only file (let's say logger.js), make sure to check that logger.js is not imported into another file used by webpack browser build. It is common that this happens with universal rendering.
In short, winston stays in Node only.

[jeanabraham]

@bradisbell, also see #287. I'm looking for something similar. Curious to know if you found anything that did the trick for you?

[bradisbell]

@jeanabraham I just wrote my own. The core functionality of Winston can be replicated quite quickly.

[indexzero]

Yes, this is a duplicate of #287. After winston@3.0.0 ships adding proper browser support is the next thing on our ROADMAP.

If you're interested in contributing to this effort please let me know and I can help you get involved!

[moffsugita]

TypeError: fs.stat is not a function