Closed adamgins closed 7 years ago
@aprilwebster @germanattanasio any ideas pls... was hoping to demo this at a Watson meetup tomorrow. Even if I could just get the minified JS for this lib, I could just include it (short term).
My hack to get around this was remove this NPM package and just include minified file from this separate project https://github.com/watson-developer-cloud/personality-insights-nodejs/blob/master/public/js/components/personality-sunburst-chart.standalone.min.js
so not sure if @germanattanasio had similar issues vs using this NPM package?
Are you using the library as an script or with browserify ?
Initially, I just did a npm install personality-sunburst-chart --save
then used it in my code using a require
as I would normally do with a node package. I ran into some issues as per #18
I then went to the script tag and included ...
<script src="https://cdnjs.cloudflare.com/ajax/libs/d3/3.5.14/d3.min.js"></script>
<script src="https://unpkg.com/personality-sunburst-chart@2.0.4/dist/index.js"></script>
The ran fine locally, but when trying to deploy I got the issues above. So my hack was to include both 3d.js
and https://github.com/watson-developer-cloud/personality-insights-nodejs/blob/master/public/js/components/personality-sunburst-chart.standalone.min.js in my public library and refer to it in using script tags as per...
<script type="text/javascript" src="/d3.js"></script>
<script type="text/javascript" src="/personality-sunburst-chart.js"></script>
This works, and will do for the iBM Watson meetup tonight, but is nasty as I am now maintaining some specific version of d3 and this js file... so probably will become messy down the road.
So any ideas on how to resolve, appreciated.
BTW, I use a ton of NPM packages and never seem to have this issues. Also not sure if some way to get the dependency on d3 a bit cleaner (ie dealt with dependencies on specific versions), as initially I had downloaded the latest version and personality-sunburst-chart.js would not work.
@germanattanasio I got a not back from Meteor Support saying that this package should
1) have an Engines param https://docs.npmjs.com/files/package.json#engines so the deployer does not have to guess this
2) should browser param too https://github.com/defunctzombie/package-browser-field-spec
Also check it ECMA script compliant https://github.com/tc39/test262
So just passing this on.. I have not had time to to see if I could create a pull request or if it's something you could look at pls?
@adamgins I've added engines
to the package.json
and I also translated the es6
to es5
in v2.0.5
but I think the problem you have is with d3.
This library is in npm but only works if you have a browser and d3. I don't think we planned on making this library work on the server side.
Can you just use?
<script type="text/javascript" src="/d3.js"></script>
<script type="text/javascript" src="/personality-sunburst-chart.js"></script>
I think this should be working with the latest changes.
Hi thanks for this package. I have it running locally ( did an npm install --save personality-sunburst-chart`and it works fine with Watson.. all good, besides in grayscale (as per issue #18).
I am trying to deploy as apart of a MeteroJS (v1.4) project, which uses NPM.
I have tried both 'import PersonalitySunburstChart from 'personality-sunburst-chart';' and 'const PersonalitySunburstChart = require('personality-sunburst-chart');` These both work locally, but cannot deploy via Meteor Galaxy.
In the example on npmjs it shows
<script src="path/to/personality-sunburst-chart.standalone.js"></script>
but I cannot find that file in the code here.when I deploy to the cloud (Galaxy/AWS), I get the following error during the build/deploy: