I wanted to learn to work with webpack and decided to create a version of Sage 9 that implements it. If interested, have a look at my fork (the branch is webpack-sage-9). https://github.com/ptrckvzn/sage/tree/webpack-sage-9 I started from Austin Pray’s webpack branch and the example provided in th…

I keep the comment at the top of my scripts. Since that’s what wordpress pass to the javascript, a global, it makes sense to inform the linter.

publicPath thingie should definitely go in the docs for Sage on Github (just pulled latest Sage and since it was webpack now rather than Gulp I just went with it). Documentation was ok up until the publicPath thingie that made me scratch my head for a while

Hi Guys, How can insert a dropdown menu on these version? I try navwalker but no luck

@a2013 Sage should spit out an unordered list of menu items to help you build your own menu system how ever you want it. There’s a ton of dropdown menu scripts out there, here’s one example: http://slicknav.com/ If you have to use the bootstrap navwalker take a look at https://github.com/twittem/wp…

You guys that have used Sage 9 for a while, would you consider running it in production or is it better to hold off?

I’m currently trialling it on a dev server to launch a prod site in a couple of week’s time. Haven’t had any showstopper issues so far, the webpack build process works great. Reading the docs carefully goes a long way. But it comes down to what your tolerance levels are for dealing with bugs and unf…

What is the proper way of installing external resources? Trying to install https://github.com/Selz/plyr I ran npm install plyr and then proceeded to run npm i -S plyr. In my Home.js route I then added import plyr from 'plyr/src/js/plyr'; and also added plyr.setup(); to the finalize part. But tha…

Oh, simply const plyr = require('plyr'); in Home.js works fine! It does not include the css though, so something is still off. Halp plz? Is this the intended method of adding stuff or am I just lucky I got it seamingly working? Also, it’s still complaining about console.log in Home.js which I fin…

Hey again guys, I get that you’re all busy coding away on your great little apps, but I’d be eternally grateful if someone could just point me in the right direction here. Where can I read up on including external dependencies in my project – the right way!

[image] intelligence: In my Home.js route I then added import plyr from ‘plyr/src/js/plyr’; and also added plyr.setup(); to the finalize part. That should normally work? Did you exit and re-run npm run watch after that?[quote=“intelligence, post:92, topic:6066”] Also, adding console.log(ply…

Getting Started
Releases
Support us

WP Packages is our new WPackagist replacement that's 17x faster and updates every 5 minutes

Roots Discourse

Sage 9 + webpack

sage

webpack

strarsis March 1, 2018, 11:16pm 105

Sage 9 + BrowserSync not loading any CSS at all on 'yarn run start' sage

The theme still got the wp_footer(), so this isn’t the issue in my case. I noticed that in console the following is logged on a (failed) hot-reload (after saving source styles): Failed to load http://localhost:3000/app/themes/the-theme/dist/57efeac3e396fa2f9996.hot-update.json: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://192.168.8.101:3000' is therefore not allowed access. Uncaught (in promise) Error: Manifest request to http://localhost:3000/a…

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled