Incompatible with Webpack 5 due to Buffer dependency #1029

csvan · 2020-10-14T06:35:26Z

Webpack 5 removes Buffer (see https://webpack.js.org/migrate/5/), effectively breaking this library since it has explicit usages of it in the code.

gilberto1991 · 2020-10-26T10:12:26Z

I also have this problem

GregdTd · 2020-12-08T12:07:40Z

Same here, any news @diegomura ?

GregdTd · 2020-12-08T13:06:08Z

I was finally able to make it works..
npm install assert browserify-zlib buffer process stream-browserify util

Then in my webpack config:

const webpack = require('webpack');

module.exports = {
 {...}
    resolve: {
        alias: {
            process: 'process/browser',
            stream: "stream-browserify",
            zlib: "browserify-zlib"
        }
    },
    plugins: [
        new webpack.ProvidePlugin({
            process: 'process/browser',
            Buffer: ['buffer', 'Buffer'],
        }),
    ]
}

matheusgrieger · 2020-12-19T03:31:49Z

@GregdTd that didn't work for me though...

csvan · 2020-12-19T09:23:13Z

@matheusgrieger I solved it in the same way. What error are you getting? What if you add buffer under resolve.fallback as well or instead of resolve.alias?

matheusgrieger · 2020-12-19T12:36:27Z

@csvan tried that but didn't work. Actually my error was being caused by a state update in another component while the PDF was rendering. Though it didn't change anything at all about the PDF content, it was crashing the app.

Some context would be good, too. I'm running React PDF in Electron and don't even need these fallbacks at all...

mstrk · 2021-01-19T14:38:06Z

@matheusgrieger I also made it work with resolve.fallback but did not had to install buffer for example. and I think @GregdTd is missing some alias like assert and util that where installed.

I know that it's probably late and you already fixed it or move on, but if you have some error log to show us, then we could help you debug that.

matheusgrieger · 2021-02-10T17:50:25Z

@mstrk I will happily get some logs to help you debug. But won't be possible for now though, as I have to change the way I wired up the app.

osimuka · 2021-02-19T10:00:27Z

I was finally able to make it works..
npm install assert browserify-zlib buffer process stream-browserify util

Then in my webpack config:

const webpack = require('webpack');

module.exports = {
 {...}
    resolve: {
        alias: {
            process: 'process/browser',
            stream: "stream-browserify",
            zlib: "browserify-zlib"
        }
    },
    plugins: [
        new webpack.ProvidePlugin({
            process: 'process/browser',
            Buffer: ['buffer', 'Buffer'],
        }),
    ]
}

After doing the above I get this error:

TypeError: Buffer.isBuffer is not a function
    at PDFDocument._write (pdfkit.browser.es.js:4190)
    at new PDFDocument (pdfkit.browser.es.js:4085)
    at Root._callee$ (react-pdf.browser.es.js:185)
    at tryCatch (runtime.js:63)
    at Generator.invoke [as _invoke] (runtime.js:293)
    at Generator.eval [as next] (runtime.js:118)
    at asyncGeneratorStep (asyncToGenerator.js:3)
    at _next (asyncToGenerator.js:25)
    at eval (asyncToGenerator.js:32)

knoefel · 2021-02-19T11:17:21Z

@osimuka In my setup (nx monorepo) i also had to add the following line in polyfills.ts:

(window as any)['global'] = window;

I guess you can also add this line in your index.html in a script tag, if you don't have a polyfill file available.

mstrk · 2021-02-19T12:48:46Z

@osimuka can you remove process: 'process/browser', line and uninstall buffer? also instead of using alias use resolve.fallback

something like this:

{
 {...}
    resolve: {
        fallback: {
            util: require.resolve('util/'),
            assert: require.resolve('assert/'),
            stream: require.resolve('stream-browserify'),
            zlib: require.resolve('browserify-zlib'),
        },
    },
    plugins: [
        new webpack.ProvidePlugin({
             Buffer: ['buffer', 'Buffer'],
             process: 'process/browser',
        }),
    ],
}

hope it helps, cheers 🖖

osimuka · 2021-02-19T12:51:34Z

@osimuka In my setup (nx monorepo) i also had to add the following line in polyfills.ts:

(window as any)['global'] = window;

I guess you can also add this line in your index.html in a script tag, if you don't have a polyfill file available.

I'm using react17, with webpack5

I did this:

<script>
    var global = window;
  </script>

DecodeStream.js:32 Uncaught TypeError: Cannot read property 'prototype' of undefined
    at eval (DecodeStream.js:32)
    at Object.eval (DecodeStream.js:99)
    at eval (DecodeStream.js:103)
    at Object../node_modules/restructure/src/DecodeStream.js (bundle.js:9841)
    at __webpack_require__ (bundle.js:10681)
    at fn (bundle.js:10912)
    at Object.eval (Number.js:7)
    at eval (Number.js:106)
    at Object../node_modules/restructure/src/Number.js (bundle.js:9881)
    at __webpack_require__ (bundle.js:10681)

osimuka · 2021-02-19T12:52:15Z

@osimuka can you remove process: 'process/browser', line and uninstall buffer? also instead of using alias use resolve.fallback

something like this:

{
 {...}
    resolve: {
        fallback: {
            util: require.resolve('util/'),
            assert: require.resolve('assert/'),
            stream: require.resolve('stream-browserify'),
            zlib: require.resolve('browserify-zlib'),
        },
    },
    plugins: [
        new webpack.ProvidePlugin({
             Buffer: ['buffer', 'Buffer'],
             process: 'process/browser',
        }),
    ],
}

hope it helps, cheers 🖖

I have tried that, I got

DecodeStream.js:32 Uncaught TypeError: Cannot read property 'prototype' of undefined
    at eval (DecodeStream.js:32)
    at Object.eval (DecodeStream.js:99)
    at eval (DecodeStream.js:103)
    at Object../node_modules/restructure/src/DecodeStream.js (bundle.js:9841)
    at __webpack_require__ (bundle.js:10681)
    at fn (bundle.js:10912)
    at Object.eval (Number.js:7)
    at eval (Number.js:106)
    at Object../node_modules/restructure/src/Number.js (bundle.js:9881)
    at __webpack_require__ (bundle.js:10681)

mstrk · 2021-02-19T13:10:32Z

@osimuka did you remove this?

<script>
    var global = window;
  </script>

and have util, assert, stream-browserify, browserify-zlib and process installed right? just checking

I don’t have buffer installed. But you might try both variations.

I think you have a mismatch of libs installed for what some of your other packages expect. If you check this line on DecodeStream.js it expects a buffer object to work with, and this might not be the same object that is being passed.

EDIT: I do have browserify-zlib installed.

osimuka · 2021-02-19T14:45:36Z

@osimuka did you remove this?
<script>
    var global = window;
  </script>
and have util, assert, stream-browserify, browserify-zlib and process installed right? just checking

I don’t have buffer installed. But you might try both variations.

I think you have a mismatch of libs installed for what some of your other packages expect. If you check this line on DecodeStream.js it expects a buffer object to work with, and this might not be the same object that is being passed.

EDIT: I do have browserify-zlib installed.

I have the modules util, assert, stream-browserify, browserify-zlib and process installed, however I have uninstalled buffer and I get the error

If you want to include a polyfill, you need to:
        - add a fallback 'resolve.fallback: { "buffer": require.resolve("buffer/") }'
        - install 'buffer'
If you don't want to include a polyfill, you can use an empty module like this:
        resolve.fallback: { "buffer": false }

Once I install buffer npm install buffer , it complies fine

I get this error on the browser with Buffer: ['buffer', 'Buffer'], removed

DecodeStream.js:31 Uncaught ReferenceError: Buffer is not defined
    at eval (DecodeStream.js:31)

Once I put it back, I get this error:

DecodeStream.js:32 Uncaught TypeError: Cannot read property 'prototype' of undefined

And I have also removed

<script>
  var global = window;
</script>

mstrk · 2021-02-19T15:00:52Z

@osimuka do what webpack ask you to do. if you install buffer add it to fallback.

add a fallback 'resolve.fallback: { "buffer": require.resolve("buffer/") }

and don't remove:

Buffer: ['buffer', 'Buffer'],

osimuka · 2021-02-19T15:10:35Z

@osimuka do what webpack ask you to do. if you install buffer add it to fallback.

add a fallback 'resolve.fallback: { "buffer": require.resolve("buffer/") }

and don't remove:

Buffer: ['buffer', 'Buffer'],

I made the changes, this is the error that happens on compile time

There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:
<path>/node_modules/restructure/src/Buffer.js
    Used by 53 module(s), i. e.
    <path>/node_modules/@react-pdf/renderer/dist/react-pdf.browser.es.js
<path>/node_modules/restructure/src/buffer.js
    Used by 12 module(s), i. e.
   <path>/node_modules/restructure/src/EncodeStream.js```

mstrk · 2021-02-19T18:34:20Z

@osimuka hmmm, you have multiple modules defined.

I think you can’t define and fallback at the same time, I would have to search the docs in webpack. I would suggest you remove the Buffer key from ProvidePlugin, or change it to buffer: 'buffer', but I have no idea. This will probably put you back at the point where you have mismatch modules from the consuming libs.

sorry for not being much help.

cheers🖖

osimuka · 2021-02-20T12:33:48Z

@osimuka hmmm, you have multiple modules defined.

I think you can’t define and fallback at the same time, I would have to search the docs in webpack. I would suggest you remove the Buffer key from ProvidePlugin, or change it to buffer: 'buffer', but I have no idea. This will probably put you back at the point where you have mismatch modules from the consuming libs.

sorry for not being much help.

cheers🖖

Yah I tried that, but it gave the error Buffer.isBuffer is not a function 🤦
Thanks for the help. I may have to revisit the library another time as I'm short for time to accomplish a new feature

ECWireless · 2021-02-25T19:33:50Z

I'm getting the same error as initially mentioned, but still no luck after reading through all this. Would be awesome if this is continually looked into.

gzhytar · 2021-02-26T17:18:28Z

This StackOverflow answer solved it for me: https://stackoverflow.com/a/65556946/15291780. To be specific, here is how different configs look like:

webpack.config.js
var webpack = require('webpack'); const NodePolyfillPlugin = require('node-polyfill-webpack-plugin') ... resolve: { fallback: { "assert": require.resolve("assert") } ... plugins: [ ... // needed to provide support for Polyfill which was part of default Webpack 4 but was removed in 5 new NodePolyfillPlugin(), new webpack.DefinePlugin({ 'process.env': { NODE_ENV: JSON.stringify(process.env.NODE_ENV || 'development') } }) ... ]

Imported packages in package.json (I use VS2019 Community Edition):
"dependencies": { ... "node-polyfill-webpack-plugin": "1.0.3", "assert": "2.0.0" ... }

ECWireless · 2021-03-01T23:54:49Z

Hmm, still not working for me. I'm using snowpack, though, which may be why. Here is what my snowpack.config.js file looks like:

const NodePolyfillPlugin = require("node-polyfill-webpack-plugin")

// @ts-nocheck
/** @type {import("snowpack").SnowpackUserConfig } */
module.exports = {
  mount: {
    public: {url: '/', static: true},
    src: {url: '/dist'},
  },
  plugins: [
    '@snowpack/plugin-react-refresh',
    '@snowpack/plugin-dotenv',
    '@snowpack/plugin-typescript',
    [
      '@snowpack/plugin-webpack', {
        extendConfig: (config) => {
          config.plugins.push(new NodePolyfillPlugin());
          return config;
        }
      }
    ],
    ['snowpack-plugin-svgr', {
      htmlMinifierOptions: false, // disabled entirely,
    }]
  ],
...

And still getting the same error.

gzhytar · 2021-03-02T12:14:05Z

@ECWireless, after I was experimenting with all the different modules and plugins, my 'node_modules' folder got bloated and random issues appeared. What helped me is to delete 'node_modules' and restore only needed packages from config. Maybe something that would help you as well.

maxdev · 2021-04-07T21:31:54Z

I was finally able to make it works..
npm install assert browserify-zlib buffer process stream-browserify util

Then in my webpack config:

const webpack = require('webpack');

module.exports = {
 {...}
    resolve: {
        alias: {
            process: 'process/browser',
            stream: "stream-browserify",
            zlib: "browserify-zlib"
        }
    },
    plugins: [
        new webpack.ProvidePlugin({
            process: 'process/browser',
            Buffer: ['buffer', 'Buffer'],
        }),
    ]
}

This solution actually works for me for Webpack 5.21.2

@diegomura but I suppose it should be also fixed in version 2.0.0?

GregdTd · 2021-05-04T13:39:21Z

Hello hello @diegomura,
FYI after upgrading to the 2.0.12 version today I got the following warning from webpack:

Again I resolved it with:

    resolve: {
        extensions: ['.js', '.jsx', '.json', '.ts', '.tsx'],
        plugins: [new TsconfigPathsPlugin()],
        alias: {
            process: 'process/browser',
            stream: "stream-browserify",
            zlib: "browserify-zlib",
            path: "path-browserify"
        },
        fallback: {
            fs: false,
            crypto: false //<----- adding this line removed the warning
        }
    },

j0nezz · 2021-05-12T11:57:39Z

If anyone stumbles accross this using Next.js, you only need to add an alias for stream and zlib since Next.js already polyfills Buffer.

This config in next.config.js worked for me:

module.exports = {
 //...
webpack: (config) => {

    config.resolve.alias.stream = 'stream-browserify';
    config.resolve.alias.zlib = 'browserify-zlib';

    return config;
  },
}

jeetiss · 2021-12-19T14:45:40Z

I googled the issue text and found this https://stackoverflow.com/a/47632275

looks like the problem is not in webpack config

mohamedaliznidi · 2021-12-19T20:39:05Z

hello @jeetiss i tryied to run my project with the exact config of the instruction but still having th same error ,

here is a link to the repo i used form my last test
https://github.com/mohamedaliznidi/pdfReader-issue

violeta-cizikas · 2021-12-22T10:25:17Z

@j0nezz thank you! Greatly helped! : >

bezchristo · 2022-01-01T18:24:00Z

I'm getting the same issue as @baonguyen2411.

Uncaught TypeError: Cannot read properties of undefined (reading 'prototype')
    at __extends (bundle.js:165215)
    at bundle.js:165231
    at Object.<anonymous> (bundle.js:165369)
    at Object../node_modules/@react-pdf/fontkit/node_modules/restructure/src/EncodeStream.js (bundle.js:165372)
    at Object.options.factory (bundle.js:504623)
    at __webpack_require__ (bundle.js:504038)
    at fn (bundle.js:504294)
    at Object.<anonymous> (bundle.js:164771)
    at Object../node_modules/@react-pdf/fontkit/node_modules/restructure/index.js (bundle.js:164797)
    at Object.options.factory (bundle.js:504623)

I followed these instructions and have all the fallbacks setup but still getting this.

aymanxdev · 2022-02-16T13:17:13Z

Can we find a way to fix this so it doesn't require modifying the webpack.config file?

vtrphan · 2022-02-17T19:02:55Z

i also got the Buffer is not defined error despite having tried all of the recommended work arounds.... I'm using create-react-app v5. There must be a solution without requiring to modify the webpack config?

wwww09z · 2022-02-25T00:35:06Z

I'm getting the same issue as @baonguyen2411.

Uncaught TypeError: Cannot read properties of undefined (reading 'prototype')
    at __extends (bundle.js:165215)
    at bundle.js:165231
    at Object.<anonymous> (bundle.js:165369)
    at Object../node_modules/@react-pdf/fontkit/node_modules/restructure/src/EncodeStream.js (bundle.js:165372)
    at Object.options.factory (bundle.js:504623)
    at __webpack_require__ (bundle.js:504038)
    at fn (bundle.js:504294)
    at Object.<anonymous> (bundle.js:164771)
    at Object../node_modules/@react-pdf/fontkit/node_modules/restructure/index.js (bundle.js:164797)
    at Object.options.factory (bundle.js:504623)

I followed these instructions and have all the fallbacks setup but still getting this.

Yes, I also got the exact same issue and cannot resolve it @jeetiss

Sasurtio · 2022-02-25T18:12:35Z

@wwww09z @baonguyen2411
I'm assuming you are using Windows or MacOS in a non-case sensitive partition

You could try to add this rule to your webpack file

{
  test: /restructure\/src\/[^w].js/,
  use: [
    {
      loader: "imports-loader",
      options: {
        type: "commonjs",
        imports: "multiple ../../buffer/ Buffer Buffer",
      },
    },
  ],
}

In my case (using NextJS 12), it looks like this

With that configuration you will force your restructure module to import the correct buffer from node_modules instead of trying to import a inner file of that library

EDIT:

If you don't already have it, you have to install imports-loader as a dev dependency, so webpack can use it as loader
https://webpack.js.org/loaders/imports-loader/#getting-started

wwww09z · 2022-02-28T02:37:05Z

@wwww09z @baonguyen2411 I'm assuming you are using Windows or MacOS in a non-case sensitive partition

You could try to add this rule to your webpack file
{
  test: /restructure\/src\/[^w].js/,
  use: [
    {
      loader: "imports-loader",
      options: {
        type: "commonjs",
        imports: "multiple ../../buffer/ Buffer Buffer",
      },
    },
  ],
}
In my case (using NextJS 12), it looks like this

With that configuration you will force your restructure module to import the correct buffer from node_modules instead of trying to import a inner file of that library

EDIT:

If you don't already have it, you have to install imports-loader as a dev dependency, so webpack can use it as loader https://webpack.js.org/loaders/imports-loader/#getting-started

@Sasurtio Thanks for your suggestion. Yes, im using macOS, but unfortunately, it still getting the same error after installing and configuring the imports-loader. So sad...

Sasurtio · 2022-02-28T07:00:09Z

@Sasurtio Thanks for your suggestion. Yes, im using macOS, but unfortunately, it still getting the same error after installing and configuring the imports-loader. So sad...

Are you using yarn or another package manager?
Have you installed buffer library?

Could you provide your webpack.config?

wwww09z · 2022-02-28T07:21:40Z

@Sasurtio Thanks for your suggestion. Yes, im using macOS, but unfortunately, it still getting the same error after installing and configuring the imports-loader. So sad...

Are you using yarn or another package manager? Have you installed buffer library?

Could you provide your webpack.config?

Sure, yep, my project is using react and Im using yarn and have installed buffer.
My webpack.config.js is currently like this:

const webpack = require("webpack");

module.exports = {
  {...},
  plugins: [
    new webpack.ProvidePlugin({
      Buffer: ["buffer", "Buffer"],
      process: "process/browser",
    }),
  ],
  module: {
    rules: [
      {
        test: /restructure\/src\/[^w].js/,
        use: {
          loader: "imports-loader",
          options: {
            type: "commonjs",
            imports: "multiple ../../buffer/ Buffer buffer",
          },
        },
      },
    ],
  },
  resolve: {
    modules: ["src", "node_modules"],
    extensions: [".js"],
    fallback: {
      process: require.resolve("process/browser"),
      zlib: require.resolve("browserify-zlib"),
      stream: require.resolve("stream-browserify"),
      util: require.resolve("util"),
      buffer: require.resolve("buffer"),
      asset: require.resolve("assert"),
    },
  },
};

wwww09z · 2022-03-01T22:21:53Z

Just for guys who have the same issue as mine and cannot resolve it after trying everything. I used the final solution which is to downgrade the Webpack from 5 to 4, then the issue resolved. This is not a solution actually, but just put here as an idea.

Sasurtio · 2022-03-02T02:18:14Z

@wwww09z Sorry to hear that. I think there should be a way to resolve this issue without adding a case-sensitive partition and moving your project there (BTW, if you want to use webpack 5 ASAP this should be the way to go)

Can you provide me more info? like if its CRA, Vite or using another library to generate the project?

Or could you provide me a mini repo where you can reproduce the issue? (For example creating one from scratch, copying the relevant config from your actual repo and only adding a component where you use this library and the error comes up)

yubinjodev · 2022-03-03T07:13:35Z

@wwww09z which webpact version did you install? im trying to downgrade my webpack but version 4.0.0 is stil giving me the error

baonguyen2411 · 2022-03-03T13:12:30Z

Hi @ALL, currently I have resolved the problem and I'm using Window, this is my Webpack 5 config
I hope it can help someone

yubinjodev · 2022-03-03T13:32:20Z

@baonguyen2411 could you paste the code please >.< also what npm packages did you install for this? And is this webpack config or craco config? im getting zlib bindings error T_T

Sasurtio · 2022-03-03T17:02:47Z

@baonguyen2411 Have you changed case sensitivity in your folder?
Because with that exact same config i had the error, only after i setted the case sensitive to true and reinstalled node_modules it worked with webpack 5 and that config

wwww09z · 2022-03-03T22:12:06Z

Hi @Sasurtio , thanks, if I still need to use webpack 5, I will try to create a mini repo later and let you know.

@yubinitdadev , here are the webpack and related packages' versions:

"webpack": "^4.43.0",
"webpack-cli": "^3.3.11",
"webpack-dev-server": "^3.11.0",
"webpack-manifest-plugin": "^4.0.2"

Sasurtio · 2022-03-04T08:29:25Z

@wwww09z when you have time could you try this rule instead of the other?
After a test in another machine (a Mac with Big Sur installed) I realized that i had an error in the regex. I accidentally deleted a "+" sign after [^w], so it wasn't finding anything with more than 1 letter before the .js extension

Also added backslash routes support (windows without WSL will need it)

{
  test: /restructure(\/|\\)src(\/|\\)[\w]+.js/,
  use: [
    {
      loader: "imports-loader",
      options: {
        type: "commonjs",
        imports: "multiple ../../buffer/ Buffer Buffer",
      },
    },
  ],
}

Here is the regex test that demonstrates the effectivity of this regex file searching:

https://regex101.com/r/MZ7M1o/1

Let me know if it worked!

luispolippo · 2022-03-05T01:40:25Z

Hi @Sasurtio. I have the exactly same problem that @wwww09z and i solved with your help.
With the correct regex it works perfectly.
Thanks 😄

sohee-K · 2022-06-14T08:48:13Z

@Sasurtio Hi, I finally solved this issue that @baonguyen2411 first posed thanks to your code! Thanks a lot 😄

WilliamPhilippe · 2022-06-24T13:12:22Z

Follow this: https://stackoverflow.com/questions/63729455/hosted-images-with-react-pdf/72744600#72744600
It worked for me

kimberleyrogers · 2022-07-24T04:16:24Z

Agonised for hours but eventually found this guide which fixed it for me. I had an extra issues (browserify-zlib) but resolved it using the same principle (adding to config-overrides.js and installing)
https://www.alchemy.com/blog/how-to-polyfill-node-core-modules-in-webpack-5

erwanriou · 2022-10-01T17:49:56Z

@WilliamPhilippe Yes for me as well

NathanFirmo · 2023-03-23T16:26:23Z

I was finally able to make it works.. npm install assert browserify-zlib buffer process stream-browserify util

Then in my webpack config:

const webpack = require('webpack');

module.exports = {
 {...}
    resolve: {
        alias: {
            process: 'process/browser',
            stream: "stream-browserify",
            zlib: "browserify-zlib"
        }
    },
    plugins: [
        new webpack.ProvidePlugin({
            process: 'process/browser',
            Buffer: ['buffer', 'Buffer'],
        }),
    ]
}

For me, it works running this:

npm install assert buffer process stream-browserify util @react-pdf/zlib

and changing webpack config to:

const webpack = require('webpack')

module.exports = {
    plugins: [
      new webpack.ProvidePlugin({
        Buffer: ['buffer', 'Buffer'],
      }),
      new webpack.ProvidePlugin({
        process: 'process/browser',
      }),
    ],
    resolve: {
      fallback: {
        zlib: require.resolve('@react-pdf/zlib'),
        stream: require.resolve('stream-browserify'),
        buffer: require.resolve('buffer'),
      },
    },
  }

ijash · 2023-06-15T05:13:58Z

please re-open this thread as CRA now uses webpack 5 as the default install.

diegomura added the bug label Apr 5, 2021

diegomura mentioned this issue Apr 21, 2021

Webpack update V4 -> V5 #1243

Closed

Alex99y mentioned this issue Apr 23, 2021

ReferenceError: Buffer is not defined randlabs/myalgo-connect#27

Open

diegomura mentioned this issue Apr 25, 2021

Webpack 5 support #1197

Closed

toranb mentioned this issue Jan 1, 2022

Support for esbuild plugins? phoenixframework/esbuild#39

Closed

andreyvEze mentioned this issue Feb 17, 2022

Upgrade react-scripts fioprotocol/fio-dashboard#477

Closed

Sasurtio mentioned this issue Feb 25, 2022

doc: updated README to work for case insensitive systems using webpack 5 #1733

Closed

jimni1222 mentioned this issue Sep 13, 2022

Add missing Buffer dependency klaytn/caver-js#705

Closed

9 tasks

Incompatible with Webpack 5 due to Buffer dependency #1029

Incompatible with Webpack 5 due to Buffer dependency #1029

Comments

csvan commented Oct 14, 2020

gilberto1991 commented Oct 26, 2020

GregdTd commented Dec 8, 2020 • edited Loading

GregdTd commented Dec 8, 2020

matheusgrieger commented Dec 19, 2020

csvan commented Dec 19, 2020

matheusgrieger commented Dec 19, 2020

mstrk commented Jan 19, 2021

matheusgrieger commented Feb 10, 2021

osimuka commented Feb 19, 2021

knoefel commented Feb 19, 2021

mstrk commented Feb 19, 2021

osimuka commented Feb 19, 2021

osimuka commented Feb 19, 2021

mstrk commented Feb 19, 2021 • edited Loading

osimuka commented Feb 19, 2021 • edited Loading

mstrk commented Feb 19, 2021 • edited Loading

osimuka commented Feb 19, 2021 • edited Loading

mstrk commented Feb 19, 2021

osimuka commented Feb 20, 2021

ECWireless commented Feb 25, 2021

gzhytar commented Feb 26, 2021 • edited Loading

ECWireless commented Mar 1, 2021

gzhytar commented Mar 2, 2021

maxdev commented Apr 7, 2021

GregdTd commented May 4, 2021

j0nezz commented May 12, 2021

jeetiss commented Dec 19, 2021

mohamedaliznidi commented Dec 19, 2021

violeta-cizikas commented Dec 22, 2021

bezchristo commented Jan 1, 2022 • edited Loading

aymanxdev commented Feb 16, 2022

vtrphan commented Feb 17, 2022

wwww09z commented Feb 25, 2022

Sasurtio commented Feb 25, 2022 • edited Loading

wwww09z commented Feb 28, 2022

Sasurtio commented Feb 28, 2022

wwww09z commented Feb 28, 2022

wwww09z commented Mar 1, 2022

Sasurtio commented Mar 2, 2022

yubinjodev commented Mar 3, 2022 • edited Loading

baonguyen2411 commented Mar 3, 2022

yubinjodev commented Mar 3, 2022 • edited Loading

Sasurtio commented Mar 3, 2022

wwww09z commented Mar 3, 2022

Sasurtio commented Mar 4, 2022

luispolippo commented Mar 5, 2022 • edited Loading

sohee-K commented Jun 14, 2022

WilliamPhilippe commented Jun 24, 2022

kimberleyrogers commented Jul 24, 2022 • edited Loading

erwanriou commented Oct 1, 2022

NathanFirmo commented Mar 23, 2023

ijash commented Jun 15, 2023

GregdTd commented Dec 8, 2020 •

edited

Loading

mstrk commented Feb 19, 2021 •

edited

Loading

osimuka commented Feb 19, 2021 •

edited

Loading

mstrk commented Feb 19, 2021 •

edited

Loading

osimuka commented Feb 19, 2021 •

edited

Loading

gzhytar commented Feb 26, 2021 •

edited

Loading

bezchristo commented Jan 1, 2022 •

edited

Loading

Sasurtio commented Feb 25, 2022 •

edited

Loading

yubinjodev commented Mar 3, 2022 •

edited

Loading

yubinjodev commented Mar 3, 2022 •

edited

Loading

luispolippo commented Mar 5, 2022 •

edited

Loading

kimberleyrogers commented Jul 24, 2022 •

edited

Loading