npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@magaya/extension-fs-helper

v0.1.0

Published

Helper package to manage local data for Magaya Extensions

Downloads

193

Readme

Extensions Filesystem Helper

Helper package to manage local data for Magaya Extensions

This package is designed to create a folder for extension persistent data (config files and extensions related files) outside of extension folder once installed in Magaya. This way the extension can be updated without accidentally deleting important persintent data or configuration files. The folder is located along with Magaya Corp were Magaya software is installed. The structure is "extensions-data/magaya-extension-name/networkId".

For this package to work an extension.config.json file must be present with valid id property, also Magaya networkId should be sent as a parameter to the function that creates or retrives the extension data folder.

usage:


const util = require('@magaya/extension-fs-helper');

myExtensionDataFolder = util.GetExtensionDataFolder(extJson.id, networkId);

Important:

:point_right: Add extension.config.json file to gitignore so it won't be downloaded to your Magaya installation duplicated. If you want to have extension.config.json file on the repository, please rename it. Also add extension-data folder to gitignore in order to avoid adding your test data and config files to the repository.

GetExtensionFolder[Async](extensionId)

Gets extension installation folder. If the extension folder is not found somewhere up the filesystem tree, then the current working directory is returned.

  • extensionId <Object>: Object with extension id data (company, name)

Example:

const util = require('@magaya/extension-fs-helper');

myExtensionFolder = util.GetExtensionFolder(extJson.id);
// or async
myExtensionFolder = await util.GetExtensionFolderAsync(extJson.id);

GetExtensionConfig[Async](extensionId)

Gets the content from the extension configuration file. Returns null if file is not found somewhere up the filesystem tree.

  • extensionId <Object>: Object with extension id data (company, name)

Example:

const util = require('@magaya/extension-fs-helper');

myExtConfig = util.GetExtensionConfig(extJson.id);
// or async
myExtConfig = await util.GetExtensionConfigAsync(extJson.id);

GetExtensionDataFolder[Async](extensionId, networkID, skipCreate)

Gets extension data folder. If it does not extist, it is created by default. If called from a Magaya installed extension, the path will be:

[magaya-installation-folder]/Magaya Corp/extensions-data/[extension-name]/[network-id]

Otherwise, the folder will be created relative the current working directory:

[cwd]/extensions-data/[extension-name]/[network-id]

  • extensionId <Object>: Object with extension id data (company, name)
  • networkID <number|string> Network id running the extension
  • [skipCreate=false] <boolean> If true, the path is resolved but the directory won't be created. Default is false

Example:

const util = require('@magaya/extension-fs-helper');

myExtensionDataFolder = util.GetExtensionDataFolder(extJson.id, networkId, true);
// or async
myExtensionDataFolder = await util.GetExtensionDataFolderAsync(extJson.id, networkId);