> 1. Term Compile is too generic, could you give us some examples about this process;
eg. in */rockspec/apisix-master-0.rockspec*, it has dependencies "lualdap = 1.2.6-1". in fact, only plugin ldap-auth.lua (/apisix/plugins/ldap-auth.lua) need it, if I don't need the plugin, I don't need the lualdap. And installing lualdap, it dependency the openldap. which install difference directory in mac or linux. There are many plug-ins of this kind. > 2. How could can help developers to integrate APISIX and this plugin, so that developers can test the plugin successfully; two method. if we don't need marketplace. we can mkdir /plugins directory, and put the ldap-auth.lua into /plugins/ldap-auth/ldap-auth.lua. in fact, the APISIX already supports method. (/apisix/plugins/ext-plugin/init.lua) if we need marketplace. the plugins could create dependency repo in github, like apisix-dashboard. > 3. I didn’t get the key point of package.json, the entry point code actually can be specified (such as from the init.lua). the package.json only has described information. like the most project. eg nodejs, it has package.json. PHP it has compose.json it can store any information for the plugin. include the dependencies. eg, the ldap-auth plugin, it has included the openldap. if i dont need the ldap-auth, i can not install openldap. Chao Zhang <zchao1...@gmail.com> 于2022年3月15日周二 11:47写道： > Hi Fei, > > I have some doubts about the proposal: > > 1. Term Compile is too generic, could you give us some examples about this > process; > 2. How could can help developers to integrate APISIX and this plugin, so > that developers can test the plugin successfully; > 3. I didn’t get the key point of package.json, the entry point code > actually can be specified (such as from the init.lua). > > Chao Zhang > https://github.com/tokers > > On March 15, 2022 at 10:54:47, Fei Liang (bsch1...@gmail.com) wrote: > > stable, the addition of the plugin will be dynamic and frequent. > >
