
Security News
npm Adopts OIDC for Trusted Publishing in CI/CD Workflows
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
FusionCharts Suite XT is a front-end, JavaScript-based, comprehensive collection of 90+ charts and 1000+ maps. This includes simple and complex charts (like the column and bar charts, pie and doughnut charts, the treemap, heatmap, and logarithmic charts), gauges (like the angular gauge, bulb gauge, and the thermometer gauge), and maps (for all continents, major countries, and all US states).
The fusionmaps package includes the complete FusionCharts Suite XT. Along with all the charts and widgets, the package also includes map definition files for all maps offered by FusionCharts.
It is recommended that you download the fusioncharts package if you will be needing only the charts and widgets. With just two map definition files (for the USA and world maps) the package size is smaller and can be installed faster.
Install the fusionmaps package.
$npm install fusionmaps
Load FusionCharts using require.
var FusionCharts = require("fusioncharts");
Load the maps module using require.
require("fusioncharts/fusioncharts.maps")(FusionCharts);
Load the map definition file(s) for the map(s) to be rendered using the format: fusioncharts.<MAP_ALIAS>, where MAP_ALIAS gets replaced by the map's JavaScript alias. Click here to get the alias names for all map definition files. Map definition files for all maps to be rendered in the application have to be included.
Therefore, assuming that you need to render the world map, the alias name world replaces the MAP_ALIAS in the format.
require("fusioncharts/maps/fusioncharts.world")(FusionCharts);
Note: Unlike the core files that are stored in the fusioncharts directory, all map definition files are stored in the maps directory and are required to be fetched from there.
Create the FusionCharts instance required to render the map.
var chart = new FusionCharts ({
"type": "world",
"width": "500",
"height": "300",
"dataFormat": "json",
"dataSource": {
chart:{}
}
}).render("chartContainer");
For some chart types, you need to include/exclude certain files and in a certain order. These chart types and the corresponding files are mentioned below:
var FusionCharts = require("fusioncharts");
require("fusioncharts/fusioncharts.charts")(FusionCharts);
require("fusioncharts/fusioncharts.zoomscatter")(FusionCharts);
var FusionCharts = require("fusioncharts");
require("fusioncharts/fusioncharts.powercharts")(FusionCharts);
require("fusioncharts/fusioncharts.treemap")(FusionCharts);
var FusionCharts = require("fusioncharts");
require("fusioncharts/fusioncharts.ssgrid")(FusionCharts);
var FusionCharts = require("fusioncharts");
require("fusioncharts/fusioncharts.gantt")(FusionCharts);
Install the fusionmaps package.
$bower install fusionmaps
Load FusionCharts.
<script src="bower_components/fusionmaps/fusioncharts.js"></script>
Load the maps module.
<script src="bower_components/fusionmaps/fusioncharts.maps.js"></script>
Load the map definition file(s) for the map(s) to be rendered using the format: fusioncharts.<MAP_ALIAS>.js, where MAP_ALIAS gets replaced by the map’s JavaScript alias. Click here to get the alias names for all map definition files. Map definition files for all maps to be rendered in the application have to be included.
Therefore, assuming that you need to render the world map, the alias name world replaces the MAP_ALIAS in the format.
<script src="bower_components/fusionmaps/maps/fusioncharts.world.js"></script>
Note: Unlike the core files that are stored in the fusioncharts directory, all map definition files are stored in the maps directory and are required to be fetched from there.
<script>
new FusionCharts({
"type": "world",
"width": "500",
"height": "300",
"dataFormat": "json",
"dataSource": {
chart:{}
}
}).render("chartContainer");
</script>
For some chart types, you need to include/exclude certain files and in a certain order. These chart types and the corresponding files are mentioned below:
<script src = "bower_components/fusioncharts/fusioncharts.js"> </script>
<script src = "bower_components/fusioncharts/fusioncharts.charts.js"> </script>
<script src = "bower_components/fusioncharts/fusioncharts.zoomscatter.js"> </script>
<script src = "bower_components/fusioncharts/fusioncharts.js"> </script>
<script src = "bower_components/fusioncharts/fusioncharts.powercharts.js"> </script>
<script src = "bower_components/fusioncharts/fusioncharts.treemap.js"> </script>
<script src = "bower_components/fusioncharts/fusioncharts.js"> </script>
<script src = "bower_components/fusioncharts/fusioncharts.ssgrid.js"> </script>
<script src = "bower_components/fusioncharts/fusioncharts.js"> </script>
<script src = "bower_components/fusioncharts/fusioncharts.gantt.js"> </script>
When fusionmaps is installed via npm, the package contains the following directories and files:
node_modules/
└── fusionmaps/
│
├── package.json
│
├── maps/
│ ├── fusioncharts.world.js
│ ├── fusioncharts.usa.js
│ └── fusioncharts.<MAP_ALIAS>.js
│
├── themes/
│ ├── fusioncharts.theme.carbon.js
│ ├── fusioncharts.theme.fint.js
│ ├── fusioncharts.theme.ocean.js
│ └── fusioncharts.theme.zune.js
│
├── fusioncharts.js
├── fusioncharts.charts.js
├── fusioncharts.zoomscatter.js
├── fusioncharts.ssgrid.js
├── fusioncharts.powercharts.js
├── fusioncharts.gantt.js
├── fusioncharts.treemap.js
├── fusioncharts.widgets.js
└── fusioncharts.maps.js
When fusionmaps is installed via Bower, the package contains the following directories and files:
bower_components/
└── fusionmaps/
│
├── package.json
│
├── maps/
│ ├── fusioncharts.world.js
│ ├── fusioncharts.usa.js
│ └── fusioncharts.<MAP_ALIAS>.js
│
├── themes/
│ ├── fusioncharts.theme.carbon.js
│ ├── fusioncharts.theme.fint.js
│ ├── fusioncharts.theme.ocean.js
│ └── fusioncharts.theme.zune.js
│
├── fusioncharts.js
├── fusioncharts.charts.js
├── fusioncharts.zoomscatter.js
├── fusioncharts.ssgrid.js
├── fusioncharts.powercharts.js
├── fusioncharts.gantt.js
├── fusioncharts.treemap.js
├── fusioncharts.widgets.js
└── fusioncharts.maps.js
FAQs
Test repository to learn transfer of already published npm package
The npm package fmaps receives a total of 3 weekly downloads. As such, fmaps popularity was classified as not popular.
We found that fmaps demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.