Steve

ok will review this fix via npm

did npm and bench update, can see new version on charts loaded. Still getting same errors, assume npm install is not conflicting with some basic fappe/erpnext chart package. Maybe way...

Code I am using. Reads a doc and displays a chart on a frappe built page. code is pasted into the .js that frappe generates for each new page. ```...

Results from this code. Note I have taken all hooks.py references to the chart library out. Frappe seems to find the npm module. Checked and the version is 1.5.2. Stiil...

Did this: yarn add frappe-charts yarn list ( shows 1.5.2 installed ) cd into the newly installed frappe-charts folder Run yarn link ( says registered ) Go to frappe repo...

Can we clarify how to use local version 1.5.2, followed instructions but frappe still used the charts 1.3 native to frappe. Also - Why not update the frappe version?

OK did a npm update in frappe folder and a bench update and that gave me: `├── [email protected] -> /home/mcd_steven/frappe-bench/node_modules/frappe-charts` So the link did work, now I get the following,...

OK, the yarn environment looks a bit messy. is that an issue? Should this be a new frappe issue... **mcd_steven@erp-next:~/frappe-bench/apps/frappe$ yarn upgrade** yarn upgrade v1.16.0 warning ../../package.json: No license field...

Hi thanks. Found those docs, the issue for me was the "field" name link in my app was different from the source docType name. In the examples, they are both...