Great to see you giving the atlassian-webresource-webpack-plugin a try and liking it!
About 8.1
If you dont mind, can you show how you are defining your provided dependencies?
This step should just work for libraries in the example.
About Step 9 - the Bonus:
The plugin described as āatlassian-webpanels-webpack-pluginā was mostly a thought experiment and a show case of what will be possible in the future.
Sadly there is no way to install this plugin as of now.
However I am happy to tell you that there is development being done in this direction as we speak.
It will, however, take some more time before we have something we are confident enough in to release.
Thanks again for your interest and we will keep you posted once we have something to show for!
glad youāre active and try to address those issues.
Iāve recently changed a job and now I work with atlassian products. As you mentioned at the atlascamp (seen the video), itās really difficult for new era fe devs to understand all of the archeological stuff thatās needed to build plugins as we are used to do things really different.
Iām now working on my first plugin and I found out I can avoid java (and its apis) almost at all. For some backend functionality I made custom endpoints with rest-service-plugin and use builtin rest apis for the rest. I want to use vue with single component files, but thereās the context thing, velocity and webfragments, which might need to be referenced as static files/templates. Have to learn about those things a bit more I guess
As I understand you want to make it possible to move all of those context/webpanel definitions directly to webpack (separate plugins) right? Whatās the roadmap? It may sound dumb, but Iām really overwhelmed by all those things that are atlassian specific.