🇵🇱Poland @kamil_lw

Hello,

I'm reopening this issue, because I'm experiencing a PHP Fatal Error.

Here's a part of the stack trace:

 Error: Call to undefined method Drupal\preview_site\Generate\TomeStaticExtension::getJavascriptModules() in /opt/drupal/web/modules/contrib/preview_site/src/Generate/TomeStaticExtension.php:185 Stack trace: 
#0 /opt/drupal/web/modules/contrib/preview_site/src/Plugin/PreviewSite/Generate/TomeGenerator.php(207): Drupal\preview_site\Generate\TomeStaticExtension->exportPaths(Array) 
#1 /opt/drupal/web/modules/contrib/preview_site/src/Plugin/PreviewSite/Generate/TomeGenerator.php(129): Drupal\preview_site\Plugin\PreviewSite\Generate\TomeGenerator->generateBuildForPath(Object(Drupal\preview_site\Entity\PreviewSiteBuild), '_entity:node:en...', 'http://default/...', Object(Drupal\Core\Queue\DatabaseQueue)) 
#2 /opt/drupal/web/modules/contrib/preview_site/src/Plugin/QueueWorker/Generate.php(115): Drupal\preview_site\Plugin\PreviewSite\Generate\TomeGenerator->generateBuildForItem(Object(Drupal\preview_site\Entity\PreviewSiteBuild), Object(Drupal\dynamic_entity_reference\Plugin\Field\FieldType\DynamicEntityReferenceItem), 'http://default/...', Object(Drupal\Core\Queue\DatabaseQueue)) 
#3 /opt/drupal/web/modules/contrib/preview_site/src/PreviewSiteBuilder.php(180): Drupal\preview_site\Plugin\QueueWorker\Generate->processItem(0) 
#4 /opt/drupal/web/modules/contrib/preview_site/src/PreviewSiteBuilder.php(120): Drupal\preview_site\PreviewSiteBuilder->processQueueItem('preview_site_ge...') 
#5 /opt/drupal/web/modules/contrib/preview_site/src/PreviewSiteBuilder.php(242): Drupal\preview_site\PreviewSiteBuilder->processSiteGeneration(Object(Drupal\preview_site\Entity\PreviewSiteBuild)) 
#6 /opt/drupal/packages/languagewire_tmgmt_connector/src/Adapter/PreviewSite/PreviewSiteBuilder.php(66): Drupal\preview_site\PreviewSiteBuilder::operationProcessGenerate(303, Array)
(...)

I've taken a look at the preview_site module source code, and I indeed can find the "getJavascriptModules()" method definition nowhere in there.

This issue was introduced in the release 1.1.5 of the module.

PS. This is my first time adding a comment in Drupal's issue tracker. Please forgive me if I should have opened a new issue instead.