Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v1.68.1 and v1.69.0 use jsPDF v2.0 which throws warning #2326

Closed
merobal opened this issue Aug 16, 2020 · 25 comments · Fixed by #2367
Closed

v1.68.1 and v1.69.0 use jsPDF v2.0 which throws warning #2326

merobal opened this issue Aug 16, 2020 · 25 comments · Fixed by #2367
Labels
bug Something isn't working

Comments

@merobal
Copy link
Contributor

merobal commented Aug 16, 2020

After upgrading to v1.68.1 I get this in the console:

Compiled with warnings.

./node_modules/jspdf/dist/jspdf.umd.min.js
Critical dependency: the request of a dependency is an expression

Probably related: parallax/jsPDF#2846

Caused by: #2311

@merobal merobal added the bug Something isn't working label Aug 16, 2020
@freben
Copy link

freben commented Aug 17, 2020

Confirmed; after merging that change, our builds immediately started failing. Will pin to an older version of material-table for now.

@benrobot
Copy link

I rolled back from 1.68.1 down to 1.68.0 and the warnings are gone. I can now successfully build my React App (whereas build warnings are considered a failure in my CI/CD).

Just my opinion, I don't see how upgrading a major version of a dependency, in this case from [email protected] to [email protected], constitutes a patch version in the material-table library. I would think it would at least be a minor version change.

@jakub-bao
Copy link

jakub-bao commented Aug 18, 2020

Hi, I'm having the same issues:

Output from react-scripts start (I'm using TypeScript):

Compiled with warnings.

./node_modules/jspdf/dist/jspdf.umd.min.js
Critical dependency: the request of a dependency is an expression

./node_modules/jspdf/dist/jspdf.umd.min.js
Critical dependency: the request of a dependency is an expression

Search for the keywords to learn more about each warning.
To ignore, add // eslint-disable-next-line to the line before.

npm list jspdf:

$ npm list jspdf
[email protected] 
└─┬ [email protected]
  └── [email protected] 

jaypalexa added a commit to jaypalexa/roster that referenced this issue Aug 18, 2020
Reverting to material-table 1.68.0 due to warnings caused by 1.68.1; see mbrn/material-table#2326
@benjaminvdb
Copy link

I was extremely surprised to see material-table depends on jsPDF for a feature that most of us aren't probably even using... Hopefully this dependency will become optional in the near feature see #2164 #2168

@Jabarbasith
Copy link

Downgrade jspdf to v1.5.3. It works for me. Warning doesn't appear again.

@victororlyk
Copy link

downgraded to material 1.67 worked for me, hope it will be solved soon

@benjaminvdb
Copy link

downgraded to material 1.67 worked for me, hope it will be solved soon

@victororlyk You could also opt for downgrading to the previous version of material-table: 1.68.0 .

@victororlyk
Copy link

@benjaminvdb , thanks it is also working.

@gpessa
Copy link

gpessa commented Aug 24, 2020

Do we have any news regarding this? I feel the pdf thing add a lot of code and has warnings

@merobal
Copy link
Contributor Author

merobal commented Aug 24, 2020

The jspdf team will release a new version with the fix within days
parallax/jsPDF#2846 (comment)
And that version should be pinned in this repo after the release.

@hendra-go
Copy link

Thanks to @merobal for the info that using jspdf@^2.1.0 fix this issue.

If using yarn you can pin jspdf version to ^2.1.0 in your project's package.json for temporary fix.

"resolutions": {
	"material-table/jspdf": "^2.1.0"
}

@ldavidsp
Copy link

Use "postinstall": "cd ./node_modules/material-table && npm install [email protected]" for temporary fix.

@thSoft
Copy link

thSoft commented Sep 1, 2020

Also reproducible with material-table 1.69.0.

@merobal
Copy link
Contributor Author

merobal commented Sep 1, 2020

A path version with the fixes is not yet released. 1.69.0 doesn't contain the fix

@ldavidsp
Copy link

ldavidsp commented Sep 1, 2020

@merobal All waiting the version 1.69.1.

@TomaszWaszczyk
Copy link

TomaszWaszczyk commented Sep 3, 2020

Does it work with newest material-table, in case of issues with the table look at: parallax/jsPDF#2846

RevolutionTech added a commit to RevolutionTech/letterboard that referenced this issue Sep 4, 2020
@YaroslavAntipov
Copy link

Are there any updates on this?

@harveyconnor
Copy link

any updates?

@merobal
Copy link
Contributor Author

merobal commented Sep 20, 2020

Still waiting for @mbrn to release the fixes

@1ur11
Copy link

1ur11 commented Sep 23, 2020

Still have issue...

@merobal merobal changed the title v1.68.1 uses jsPDF v2.0 which throws warning v1.68.1 and v1.69.0 use jsPDF v2.0 which throws warning Sep 23, 2020
@harveyconnor
Copy link

@1ur11 it has been fixed we are awaiting next release.

RevolutionTech added a commit to RevolutionTech/letterboard that referenced this issue Oct 2, 2020
Damn you dependabot and mbrn/material-table#2326
Fool me once, shame on you.
Fool me twice, shame on me.
@merobal
Copy link
Contributor Author

merobal commented Oct 2, 2020

v1.69.1 is just released, finally 🎉

@jaydlawrence
Copy link

v1.69.1 is just released, finally 🎉

v1.69.0 is still the latest on the releases page.
https://github.com/mbrn/material-table/releases
When do you think it will be available to pull via npm?

@merobal
Copy link
Contributor Author

merobal commented Oct 5, 2020

@adamcarrollsimfy
Copy link

I can confirm that v1.69.1 is working for me, nice work!

abettermap added a commit to Language-Mapping/language-map that referenced this issue Oct 17, 2020
Cannot use 1.69.1 and the only way this whole fragile mess works is via
`resolutions` in package.json (did it for jspdf-autotable as well):
mbrn/material-table#2326
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.