Title: Missing package.json file
Last modified: June 3, 2025

---

# Missing package.json file

 *  Resolved [Zaher (za-her)](https://wordpress.org/support/users/zaherg/)
 * (@zaherg)
 * [1 year ago](https://wordpress.org/support/topic/missing-package-json-file/)
 * Hey there:
 * While its not a bug, but it seems that the `package.json` and `package-lock.json`
   are missing , it would be nice if they were published with the source code too.
 * Thanks

Viewing 8 replies - 1 through 8 (of 8 total)

 *  Plugin Support [Jarno Vos](https://wordpress.org/support/users/jarnovos/)
 * (@jarnovos)
 * [1 year ago](https://wordpress.org/support/topic/missing-package-json-file/#post-18496706)
 * Hi [@zaherg](https://wordpress.org/support/users/zaherg/),
 * Thanks for your comment. These files are indeed not included in the release of
   the plugin, since they’re only needed during development for build processes 
   and tooling; and not actually required for the ‘live’ plugin to work as intended.
 * While this might change in the future, we currently don’t distribute those files
   in the release. The released version contains all the compiled assets that are
   necessary for the plugin to function properly in production.
 * Kind regards, Jarno
 *  Thread Starter [Zaher (za-her)](https://wordpress.org/support/users/zaherg/)
 * (@zaherg)
 * [1 year ago](https://wordpress.org/support/topic/missing-package-json-file/#post-18496741)
 * Hey [@jarnovos](https://wordpress.org/support/users/jarnovos/)
 * The code is released under [GPL-2.0-or-later](https://spdx.org/licenses/GPL-2.0-or-later.html)
   license which means that even those small files should be included in the code,
   in the same way that the `composer.json` file has been included.
 * > if you distribute copies of such a program, whether gratis or for a fee, you
   > must give the recipients all the rights that you have. You must make sure that
   > they, too, receive or can get the source code. And you must show them these
   > terms so they know their rights.
   >  GPL2.0 or later introduction
 * > complete source code means all the source code for all modules it contains,
   > plus any associated interface definition files, plus the scripts used to control
   > compilation and installation of the executable.
   >  GPL2.0 Terms and Conditions for Copying Distribution and Modification
 * Those missing file control the compilation of the source code, and should be 
   included as part of the code, otherwise the plugin does not follow the license
   rules correctly.
 *  Plugin Support [Jarno Vos](https://wordpress.org/support/users/jarnovos/)
 * (@jarnovos)
 * [1 year ago](https://wordpress.org/support/topic/missing-package-json-file/#post-18496764)
 * Hey [@zaherg](https://wordpress.org/support/users/zaherg/),
 * That is a very valid point indeed. To expand on my earlier reasoning as to why
   this is currently the case: our aim is to make the package on WordPress.org as
   small as possible.
 * While I can’t provide an exact answer on when/how this will be addressed yet;
   we will definitely discuss & review our build process to make sure we’re properly
   including each of the necessary files, to ensure full `GPL-2.0-or-later` compliance.
 * Hope this helps to address your concern for the time being.
 * Thanks again for your careful attention and feedback here. It is much appreciated!
 * Kind regards, Jarno
 *  Thread Starter [Zaher (za-her)](https://wordpress.org/support/users/zaherg/)
 * (@zaherg)
 * [1 year ago](https://wordpress.org/support/topic/missing-package-json-file/#post-18496782)
 * Hey [@jarnovos](https://wordpress.org/support/users/jarnovos/)
 * > Our aim is to make the package on WordPress.org as small as possible.
 * Those small files does not make the size of the package huge.
 * > While I can’t provide an exact answer on when/how this will be addressed yet;
   > we will definitely discuss & review our build process to make sure we’re properly
   > including each of the necessary files, to ensure full `GPL-2.0-or-later` compliance.
 * I know its not my part, but publishing the full source code (and making it publicly
   available) to github/gitlab can help with that. As it will even helps removing
   the source code from the package pushed to wordpress while following the rules
   of `GPL-2.0-or-later`
 * Thanks
    -  This reply was modified 1 year ago by [Zaher (za-her)](https://wordpress.org/support/users/zaherg/).
 *  Plugin Author [Wim Braam](https://wordpress.org/support/users/wimbraam/)
 * (@wimbraam)
 * [1 year ago](https://wordpress.org/support/topic/missing-package-json-file/#post-18497396)
 * Hi [@zaherg](https://wordpress.org/support/users/zaherg/),
 * Thanks again for flagging this issue.
 * We actually already have a GitHub repository for the plugin, a mirror of our 
   actual repository, but we haven’t set it to public yet. The reason for it to 
   be private is the simple fact we have a couple of automation files in the repository
   that we do not like to make publicly available. We are researching a way to keep
   the repo in sync without showing these files, when we’ve finished this up we 
   will set the repo to public.
 * In the meantime, if you’d like to have the `package.json`, we’re happy to share
   it with you. Just let us know.
 * Kind regards, Wim
 *  Thread Starter [Zaher (za-her)](https://wordpress.org/support/users/zaherg/)
 * (@zaherg)
 * [1 year ago](https://wordpress.org/support/topic/missing-package-json-file/#post-18497414)
 * Hey [@wimbraam](https://wordpress.org/support/users/wimbraam/)
 * Thank you so much, and I hope to see the mirrored repo public soon.
 * If you don’t mind sharing the whole code without the automation that would be
   nice.
 * Again, thanks again for you and [@jarnovos](https://wordpress.org/support/users/jarnovos/)
 *  Plugin Author [Wim Braam](https://wordpress.org/support/users/wimbraam/)
 * (@wimbraam)
 * [1 year ago](https://wordpress.org/support/topic/missing-package-json-file/#post-18497498)
 * Hi [@zaherg](https://wordpress.org/support/users/zaherg/),
 * Sure! Here you go: [https://handover.blue/get/a14d0c9f-e775-45a2-ae9d-89d06f9938b0](https://handover.blue/get/a14d0c9f-e775-45a2-ae9d-89d06f9938b0)
 * Please let us know if you have any further questions.
 * Kind regards, Wim
 *  Thread Starter [Zaher (za-her)](https://wordpress.org/support/users/zaherg/)
 * (@zaherg)
 * [1 year ago](https://wordpress.org/support/topic/missing-package-json-file/#post-18497625)
 * Amazing, thanks [@wimbraam](https://wordpress.org/support/users/wimbraam/)

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘Missing package.json file’ is closed to new replies.

 * ![](https://ps.w.org/simplybook/assets/icon-256x256.png?rev=3065290)
 * [SimplyBook.me - Booking and reservations calendar](https://wordpress.org/plugins/simplybook/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/simplybook/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/simplybook/)
 * [Active Topics](https://wordpress.org/support/plugin/simplybook/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/simplybook/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/simplybook/reviews/)

 * 8 replies
 * 3 participants
 * Last reply from: [Zaher (za-her)](https://wordpress.org/support/users/zaherg/)
 * Last activity: [1 year ago](https://wordpress.org/support/topic/missing-package-json-file/#post-18497625)
 * Status: resolved