# Jira Forge Export Excel file **URL:** \ **Category:** Forge UI Kit and Custom UI\ **Tags:** export, jira-cloud\ **Created:** [February 21, 2024, 4:18pm UTC](https://community.developer.atlassian.com/t/jira-forge-export-excel-file/77548 "2024-02-21T16:18:42Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![ibuchanan](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/ibuchanan/32/35815_2.png) [@ibuchanan](https://community.developer.atlassian.com/u/ibuchanan)\ **Post date:** [February 21, 2024, 8:13pm UTC](https://community.developer.atlassian.com/t/jira-forge-export-excel-file/77548/2 "2024-02-21T20:13:35Z")
Welcome to the Atlassian developer community @DanielVelkov, > [@DanielVelkov](#): > > We need to implement an export button for some table data we generate from the issues object. > Is that possible? Possible, but only as a distinct feature, not associated with existing export capabilities. See this recent discussion: > [@How to add menu item to the Export Issues menu](https://community.developer.atlassian.com/t/how-to-add-menu-item-to-the-export-issues-menu/76192): > > Hello, I would like to add a menu item in the Export Issues menu (in the Issues page ) and the Export menu (in the Search page) or a new Menu next to the Export Issues one. I don’t see a module in Forge to do that. Is there a way to do it? Thanks, Edgar > [@DanielVelkov](#): > > What are the allowed formats? > I tried an implementation using the file-saver and exceljs packages but it seems forge doesn’t allow npm packages other than @forge/ui It isn’t so much that there is an explicit set of “known formats”. Rather that you will have some limitations based on the Forge environment. In the currently GA runtime, you are limited by Atlassian’s proprietary Node-like implementation. While [our documentation has a pretty exhaustive list of limitations](https://developer.atlassian.com/platform/forge/runtime-reference/), we are aware that it’s often hard to know if those limitations apply to a specific library. You might have to probe the dependency tree pretty hard to know if and why a particular library doesn’t work. Fortunately, there is a new [Forge native Node.js runtime](https://developer.atlassian.com/platform/forge/runtime-reference/native-nodejs-runtime) that helps solve these problems: > The new _native Node.js runtime_ enables Forge functions to run within a standard Node.js environment. This will allow you to import any built-in, local, or third-party Node modules into your app. You might try using your libraries in that runtime instead. That said, you still don’t have full access to the infrastructure, which some libraries might assume. For example, you won’t have a way to just “drop a file” on disk and pick it up outside the Forge App. So you will still want to be aware of [the new runtime’s limitations](https://developer.atlassian.com/platform/forge/runtime-reference/native-nodejs-runtime/#known-limitations). --- _[View the full topic](https://community.developer.atlassian.com/t/jira-forge-export-excel-file/77548)._