remove handleDebounce incorrect arguments from arrow functions

[justincorrigible]

Temporary workaround, for anyone who may come across this issue before this PR is merged:

use import ToolkitProvider from 'react-bootstrap-table2-toolkit/dist/react-bootstrap-table2-toolkit.min'; instead.

---

Problem addressed:
As seen in MDN's web docs, an arrow function...

"Does not have arguments, or new.target keywords."

leading to this error when trying to import the toolkit package.

Uncaught ReferenceError: arguments is not defined

---

Edit for housekeeping: closes #1520

[justincorrigible]

Bonus: corrects typo

[justincorrigible]

@AllenFang @Chun-MingChen For your consideration
Thanks for a great set of packages. Time saving and very useful!

[cjmaynar]

I saw this issue upon attempting to upgrade to Webpack 5; thanks for the PR! Would love to see this merged and released to allow this package to work with newest version of Webpack

[Sharpek]

Any chance for release?

[itsmepetrov]

Hi @AllenFang and @chunming-c, could you please approve this PR and release a new version. I'm trying to upgrade webpack to v5 and this is the last thing which prevents me from that.

[janeksmielowski]

What is the chance for a release?

[MarlonAEC]

Hi folks!...Any news on this issue!? Cheers!

[juniorkibirige]

Error is back
Mix: Laravel Mix v6.0.13

[IlanFrumer]

Using this inside vitejs for now

 // vite.config.ts const modulesFolder = path.resolve(__dirname, 'node_modules/'); // ... resolve: { alias: { 'react-bootstrap-table2-toolkit-css': `${modulesFolder}/react-bootstrap-table2-toolkit/dist/react-bootstrap-table2-toolkit.min.css`, 'react-bootstrap-table2-toolkit': `${modulesFolder}/react-bootstrap-table2-toolkit/dist/react-bootstrap-table2-toolkit.js`, '@': srcFolder, }, },

[erhanfirat]

PR is opened on Nov 10,
And I see as time passes new developers getting same error like me.
Don't you think to release?

[mah51]

Hi, I have also encountered this problem. Any chance of this being merged soon?

[afvieira]

Hi, I have also encountered this problem. Any chance of this being merged soon?

+1

[Jarvismkennedy]

Hi, I have also encountered this problem. Any chance of this being merged soon?

+1

[steveast]

+1

[collynwalte]

I'm having this issue too

[jeremy-london]

Im having this issue can we get this MR reviewed and pushed please @AllenFang @itsmepetrov

The workaround in the MR description works, but we also needed to ignore some typescript pieces.. looking forward to updates

[Anonymous3105]

Can we get to know the timeline for the merge and release for this?
A lot of people (including me) are facing this issue. I tried the given workaround

use import ToolkitProvider from 'react-bootstrap-table2-toolkit/dist/react-bootstrap-table2-toolkit.min'; instead.

But I'm still getting the same error.
Please provide the resolution for this.

[sheldonsebastian]

+1 on this issue

[jamesbaker1]

+1

[xcarlosamm]

+1

[regis-samurai]

+1

[RuDami]

+1

[wcordelo]

+1

[duhmojo]

+1 +1 +1 +1 +1

[DeDX3]

+1
I'm stuck here too. Used the link you gave but still same issue

[spookier]

+1

[duhmojo]

FYI to all. The workaround by @IlanFrumer works for me. Added it to my resolve rebuilt and all is good again in the app.

Using this inside vitejs for now

 // vite.config.ts const modulesFolder = path.resolve(__dirname, 'node_modules/'); // ... resolve: { alias: { 'react-bootstrap-table2-toolkit-css': `${modulesFolder}/react-bootstrap-table2-toolkit/dist/react-bootstrap-table2-toolkit.min.css`, 'react-bootstrap-table2-toolkit': `${modulesFolder}/react-bootstrap-table2-toolkit/dist/react-bootstrap-table2-toolkit.js`, '@': srcFolder, }, },

There should still be a release or a statement that the project is inactive. With no activity in nearly 2 years, yet still 70K downloads weekly, this module is an example case of a disaster waiting to happen. If its inactive, just state it so people know what they're getting into.

[RuDami]

okay, i'm used comment by duhmojo, but adapted for use with react-app-rewired && react-scripts.

1. yarn add react-app-rewired

2. package.json:

 "scripts": { "start": "react-app-rewired start --scripts-version react-scripts", "build": "react-app-rewired build --scripts-version react-scripts" } 

3. in project root create config-overrides.js with

module.exports = function override(config, env) { if (!config.resolve) { config.resolve ={ alias: { "react/jsx-dev-runtime": "react/jsx-dev-runtime.js", "react/jsx-runtime": "react/jsx-runtime.js", 'react-bootstrap-table2-toolkit-css': `react-bootstrap-table2-toolkit/dist/react-bootstrap-table2-toolkit.min.css`, 'react-bootstrap-table2-toolkit': `react-bootstrap-table2-toolkit/dist/react-bootstrap-table2-toolkit.js`, } }; }else { config.resolve = { ...config.resolve, alias: { ...config.resolve.alias, "react/jsx-dev-runtime": "react/jsx-dev-runtime.js", "react/jsx-runtime": "react/jsx-runtime.js", 'react-bootstrap-table2-toolkit-css': `react-bootstrap-table2-toolkit/dist/react-bootstrap-table2-toolkit.min.css`, 'react-bootstrap-table2-toolkit': `react-bootstrap-table2-toolkit/dist/react-bootstrap-table2-toolkit.js`, } } } return config; } 

4. yarn start

5. ???

6. PROFIT

[KevinGage]

This is preventing us from updating to react-scripts 5 due to the webpack 5 incompatibility. It seems like a small but critical patch. I'll echo what @duhmojo said. It sure looks like this project has been abandoned by its maintainers. If that's the case it would be great to know. Maybe someone would fork at that point.

[alex-shepel]

To use with TypeScript import types separately.

import { ToolkitContextType } from 'react-bootstrap-table2-toolkit'; import ToolkitProvider from 'react-bootstrap-table2-toolkit/dist/react-bootstrap-table2-toolkit'; <ToolkitProvider exportCSV {...tableProps}> {(props: ToolkitContextType) => ( // everything else )} </ToolkitProvider> 

[Swethasri1512]

Please anyone give me solution for this

[mustafaasif1]

Use "react-bootstrap-table2-toolkit/dist/react-bootstrap-table2-toolkit" instead of "react-bootstrap-table2-toolkit" for importing of Components.