spatie / statamic-responsive-images

Responsive images for Statamic 3
MIT License
99 stars 29 forks source link

Uncaught SyntaxError: 60 #175

Closed qbixx closed 1 year ago

qbixx commented 1 year ago

Bug description

When compiling the assets for production with npm run production the page doesn't load and only a white screen is visible. This probably is because of an issue in combination with Vue3.

When looking at the console log, I get the following error:

![Uploading Screenshot 2022-10-24 at 17.22.25.png…]()

How to reproduce

I'm using the following packages:

TailwindCSS: 3.0.19 Vue: 3.2.31

When running npm run watch or npm run develop everythings works fine. However when running npm run production the error appears.

Logs

No response

Environment

Application Name: Statamic
Laravel Version: 9.36.4
PHP Version: 8.0.20
Composer Version: 2.1.6
Environment: local
Debug Mode: ENABLED
URL: 
Maintenance Mode: OFF

Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED

Drivers
Broadcasting: log
Cache: statamic
Database: mysql
Logs: stack / single
Mail: smtp
Queue: sync
Session: file

Statamic
Addons: 4
Antlers: regex
Version: 3.3.48 PRO

Statamic Addons
edalzell/forma: 1.2
silentz/mailchimp: 2.9.1
spatie/statamic-responsive-images: 2.14.2
statamic/seo-pro: 3.1.0

Installation

Fresh statamic/statamic site via CLI

Antlers Parser

regex (default)

Additional details

No response

ncla commented 1 year ago

Could you reupload the screenshot please? It seems to be bugged and not loading.

This probably is because of an issue in combination with Vue3.

This might be the culprit. The Statamic CMS control panel is based on Vue 2

qbixx commented 1 year ago

Sorry, I uploaded the image below:

Screenshot 2022-10-28 at 11 21 22

ncla commented 1 year ago

I am not sure if this relates to this addon at all. Are you compiling this addons assets to setup a dev environment for developing this addon? Or are you compiling something in your project (e.g. custom fieldtype)?

You need to use Vue 2 if you are creating custom fieldtype components.

Closing for now as this does not seem related to this addon.

Also, thanks to you I realized that front-end assets had not be compiled in this repository, which I sorted just now!