If you added FastGrid to your project with a script tag before version 3.2, it still works. Nothing breaks. But since 3.2, FastGrid also ships as an official npm package for React, Angular, Vue and Svelte. Here is what changes, what doesn't, and how to move over.
npm install fastgrid-<framework> instead of being loaded from a <script src="..."> tag.FastGrid uses a scaffolding command rather than a plain npm install, so it can set up a working example project alongside the package:
npm create fastgrid-react
npm create fastgrid-angular
npm create fastgrid-vue
npm create fastgrid-svelte
npm create fastgrid-html
Run the one matching your stack. This creates a new example project; copy the FastGrid-related dependency and setup into your existing app, or use the generated project as your new starting point if you're migrating a small app.
Delete the <script> tag that previously loaded FastGrid from your HTML template or layout file.
Where you previously wrote something like:
var grid = new TreeGrid(document.getElementById('grid'), config);
you now import and use the framework-native component instead. The exact syntax differs by framework; see the example project generated in step 1, or the corresponding documentation page (FastGridReact.html, FastGridAngular.html, FastGridVue.html, FastGridSvelte.html).
Your existing column definitions, formulas and cell types map directly onto the component's config prop/input. This is usually a copy-paste, not a rewrite, since the underlying grid engine is unchanged between the script-tag and package versions.
Move any inline event handlers (onCellChange, onSort, etc.) to the framework's event binding style (props in React, @Output in Angular, emits in Vue, event dispatch in Svelte). Handler logic itself does not need to change.
Confirm that your data source (JSON/XML/XLSX endpoint) still loads correctly and that export/print functions behave the same as before. This part of the API does not change with the migration.
Once the framework component is confirmed working, remove any leftover references to the old global FastGrid object elsewhere in your codebase.
FastSheet: FastSheet uses the same packages as FastGrid and follows the same migration steps.
No. Column, formula and formatting configuration is portable between the script-tag and package versions.
No. Licensing is per developer/application, independent of installation method.
Yes. The script-tag and package versions can coexist during a gradual migration, as long as you're not loading the same FastGrid version twice on the same page.
The script-tag setup remains fully supported, and a plain HTML/JavaScript example is also available via npm create fastgrid-html.
Yes for FastSheet, it uses the same packages as FastGrid. TreeGrid and GanttChart do not yet have dedicated framework packages.
Install the package for your framework
Or contact us if you're migrating a large or heavily customized grid.
Get migration help →