You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 12, 2022. It is now read-only.
After upgrade to version 4.0.1: there is a problem in the package itself (although removing (node_modules & cache)) cause to throw an error on serving the app ( Error during "npm start" ): https://www.screencast.com/t/Xa0HslDOD2y
Error details: ./node_modules/angular2-signaturepad/fesm2015/angular2-signaturepad.mjs:3:0-52 - Error: Module not found: Error: Can't resolve 'signature_pad' in '.\node_modules\angular2-signaturepad\fesm2015'
Note:
I'm using Angular version 13.2.2
Current solution:
Completed working with old version 3.0.4 (which is compatible with no errors) ..till this error is fixed in next releases!
The text was updated successfully, but these errors were encountered:
Can confirm. I have the same problem but with fesm2020 & Angular 13.0.0. ./node_modules/angular2-signaturepad/fesm2020/angular2-signaturepad.mjs:3:0-52 - Error: Module not found: Error: Can't resolve 'signature_pad' in '/app-path/node_modules/angular2-signaturepad/fesm2020'
Version 3.0.4 works as expected.
Edit: Never mind. I was using an older node version. It works with node version 16 nvm use 16 for me.
After upgrade to version
4.0.1
: there is a problem in the package itself (although removing (node_modules & cache)) cause to throw an error on serving the app ( Error during "npm start" ): https://www.screencast.com/t/Xa0HslDOD2yError details:
./node_modules/angular2-signaturepad/fesm2015/angular2-signaturepad.mjs:3:0-52 - Error: Module not found: Error: Can't resolve 'signature_pad' in '.\node_modules\angular2-signaturepad\fesm2015'
Note:
I'm using Angular version
13.2.2
Current solution:
Completed working with old version
3.0.4
(which is compatible with no errors) ..till this error is fixed in next releases!The text was updated successfully, but these errors were encountered: