Skip to content

Support manifest.json file name option when packaging a plugin. #1551

@RikiyaOta

Description

@RikiyaOta

Package

  • @kintone/plugin-packer

Why

When I developed a kintone plugin, I used the same manifest.json file in dev and prod (but, when using in prod, I modified the content of manifest.json file) 🥺

If I can specify manifest.json file name like manifest-dev.json and manifest-prod.json, I think that we can easily develop in multiple environments 😉

What

I want to add a new option to kintone-plugin-packer CLI: --manifest-file-name MANIFEST_FILE_NAME

Usage I imagined:

$ PLUGIN_DIR='/path/to/your/plugin_dir'
$ kintone-plugin-packer "$PLUGIN_DIR" --manifest-file-name manifest-dev.json

If this option is specified, kintone-plugin-packer searches the file name instead of manifest.json and reads information about the plugin packaged.

I think that the default value of it should be manifest.json.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions