MetaEd IDE (ATOM) - Updating package.json

Owned by Stephen Fuqua
Last updated: Mar 20, 2023 by David Clements
1 min read

This page refers to the ATOM-based IDE, which was replaced with Visual Studio Code in March, 2023.  You can find the current version of MetaED IDE using VS Code here: MetaEd IDE User Guide

Generating the package.json File

The package.json file allows users to provide a custom Project Name and Project Version for their extension project. This file is required to run a successful build or deployment of an extension project.

Step 1. Create a New Extension Project

When a new extension project is created in MetaEd IDE, a package.json file is automatically generated.
image2018-5-25_14-19-19.png

Step 2. Customize

Provide the appropriate projectName and projectVersion. The projectName

  • must start with an uppercase alphabetic character
  • must have at least two alphabetic characters
  • should avoid special characters, as they will likely be stripped out for downstream artifacts

For example, "Project-Two" will be transformed to a "projecttwo" database schema by the SQL plugin.

image2018-5-25_14-20-29.png

Note that for extension projects built against Data Standard v2.0, the projectName must be "Extension", as shown in the default file. The projectName may only be customized for v3.0 and later versions.

IDE User Guide Contents

Read more about how to use the MetaEd IDE: