Module not found: Error: Can't resolve 'fs' in '/Users/Saravanan/projects/frontend/widgets/web/node_modules/antlr4'

[saravanan10393]

I am using antlr4 with javacript target since years, Now it is throwing error when i do a build using webpack

Module not found: Error: Can't resolve 'fs' in '/Users/Saravanan/projects/frontend/widgets/web/node_modules/antlr4'

It was working fine with webpack-4 with following settings enabled. But now with wbpack-5 it is throwing the error as above.

[ericvergnaud]

Smells like a webpack issue more than an antlr one... How about checking webpack specs and submitting a PR to update the antlr docs? Envoyé de mon iPhone

…

Le 19 juin 2020 à 17:49, Saravanan Ramupillai ***@***.***> a écrit :  I am using antlr4 with javacript target since years, Now it is throwing error when i do a build using webpack Module not found: Error: Can't resolve 'fs' in '/Users/Saravanan/projects/frontend/widgets/web/node_modules/antlr4' It was working fine with webpack-4 with following settings enabled. But now with wbpack-5 it is throwing the error as above. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[toolgood]

Browser throws an error

require.js:178 GET http://localhost:8888/fs.js 404 (Not Found)

CharStreams.js
const fs = require("fs");

[LemonyPie]

@ericvergnaud Maybe it is possible to optionally include char and file stream files? Not to force its inclusion in antlr's index.js if antlr is used on frontend
Additionally the options which allow to fix this in webpack 4 does not work for webpack 5

[ericvergnaud]

Suggest you stick to webpack 4 until webpack 5 provides an equivalent for the below config:

node: { module: "empty", net: "empty", fs: "empty" },

[namratha-b]

I am using antlr4 with javacript target since years, Now it is throwing error when i do a build using webpack

Module not found: Error: Can't resolve 'fs' in '/Users/Saravanan/projects/frontend/widgets/web/node_modules/antlr4'

It was working fine with webpack-4 with following settings enabled. But now with wbpack-5 it is throwing the error as above.

hi @saravanan10393 ,
any update on this issue?

[kaiyoma]

Suggest you stick to webpack 4 until webpack 5 provides an equivalent for the below config:

node: { module: "empty", net: "empty", fs: "empty" },

This seems like very unrealistic advice. webpack 5 has been out for an entire year already; I don't think you can tell people "don't upgrade until they fix this problem with our package".

I tried adding fs: "empty" to my webpack configuration and webpack rejects the configuration. Are there are any workarounds or any work being invested into this?

[kaiyoma]

Ah, there is a solution for webpack 5, but for some reason it's not documented here. In your webpack config, add this:

resolve: {
  fallback: {
    fs: false
  }
}

[Ketler13]

@saravanan10393 @kaiyoma @namratha-b if you're on webpack5 could you please try suggestion I added here - #3414 ? Just modify manually package.json file in node_modules/antlr4 and check how it works?

[ericvergnaud]

Next release uses webpack 5, so closing this