Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Javascript and CSS in packer versions >1.3.8 don't compile and/or don't evaluate #88

Closed
adrianocr opened this issue Apr 28, 2021 · 2 comments
Labels
bug Something isn't working

Comments

@adrianocr
Copy link

adrianocr commented Apr 28, 2021

For me all packer versions above 1.3.8 successfully compile (as in there are no errors in the terminal) and upload but the JS doesn't evaluate and the CSS file(s) are blank.

If I open the browser inspector I can see a <script> and <link> tag before </head>. If I open the JS file(s) link in a new tab I can see the code is correctly in there, but the browser doesn't load or evaluate the javascript code webpack builds; it never runs. I emptied all the JS code and placed console.log('testing packer in [template name here]') in each template and you never see a single console message on any of the templates. Likewise if you open the CSS file(s) through their address in a new tab they are completely blank for me, like packer isn't actually compiling and bundling the CSS.

This project was NOT built on packer-blank-theme; it was an existing project that I retroactively added packer to. And this worked beautifully up until 1.3.8 but after I upgrade to the latest versions the same exact setup no longer works.

OS: macOS 11.3
Node: v14.16.0
Yarn: 1.22.10

Perhaps also related to #76

@adrianocr adrianocr added the bug Something isn't working label Apr 28, 2021
@hayes0724
Copy link
Owner

@adrianocr I think this is a macOS issue with SSL, in v1.3.8 the method for using and creating SSL was changed. I unfortunately don't have a mac to test on so this is taking a while to debug.

@hayes0724
Copy link
Owner

@adrianocr Fixed pushed in #89 see issue #76 or updated SSL docs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants