For me it sounds you are more in static page generation area, and less in the JS applications where webpack thrives.
You can consider:
writing a script to load the existing content, to include it in the new repository. Downside - you will replace DB with static files in the repo. This will change the workflow with content authoring. Once you have content locally, you will need to figure out importing it with wepback
use similar script, but on the build time. So data will live where you have it now, and each build will reload it's current state
write an application that loads data dynamically, from the browser
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
For me it sounds you are more in static page generation area, and less in the JS applications where webpack thrives.
You can consider: