📺 YouTube Live: https://youtu.be/1DTvRu4pILY
In this episode, we will be setting up the development tools for Kintone Plug-in Development!
Table-Utility-Plug-in/blob/main/1_Starting_Point/
We need to start by reconfiguring the manifest.json file by linking to the appropriate code.
Automate the Kintone Plug-in Development pipeline
- Details at Developer_Tools.md
npm run build
command generates this folder.
Webpack takes in the React JSX files and generates the JS files.
- Missing link turn our directory of code into a machine readable
- Webpack starts from index.js --> then spider their way into all the refereed files
- Kintone Plug-in's desktop.js & config.js never touch.
Create a .env
file with the following:
KINTONE_BASE_URL=<subdomain>.kintone.com
KINTONE_USERNAME=<user name>
KINTONE_PASSWORD=<user password>
Add .env
to .gitignore
to prevent your Kintone login credential from being uploaded.
npm install -g dotenv-cli
entropitor/dotenv-cli: A cli to load dotenv files
Use dotenv to map the Kintone login credential inside .env
in the command
npm i cross-var
Use cross-var to make our custom commands usable across Mac, Linux, and Windows
npm run pack
Tie it to kintone-plugin-packer
--ppk PPK_FILE
: The path of input private key file. If omitted, it is generated automatically into .ppk in the same directory of PLUGIN_DIR or --out if specified.