Should I turn of linting or keep this line of code on top of my file.
Generally itâs acting quite weird, sometimes styles fail to load, sometimes itâs something else but itâs very interesting
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
@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/
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 unforseen problems that come with the territory of using bleeding edge code.
As far as BS4 goes, thatâs still in alpha. But itâs had the âalphaâ label for a solid year now. Anecdotally people are saying itâs working just fine on prod sites. Just stay on top of the Bootstrap Blog so you know what changes / modifications occur between releases.
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 that doesnât seem to have done the trick as the player is not initialized. What am I missing?
Also, adding console.log(plyr) throws warning Unexpected console statement no-console is this normal?
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!
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(plyr) throws warning Unexpected console statement no-console is this normal?
[/quote]
I didnât get it to work at all at first, but when I exited, and ran npm run build followed by npm start it started working. So probably was something I messed up with there.
Thank you for clarifying about the scss part. Both good and bad that Sage 8 has been fairly automated regarding how external dependencies are added, you forget how you do it manually, hehe.
Btw like I said I get a warning from using console.log in Home.js, and I donât get any output in the console. I.e. console.log('hey'); produces
[HMR] bundle rebuilt in 6678ms
(index):1176 [HMR] bundle has warnings:
(index):1176 [HMR] ./assets/scripts/routes/Home.js
/Users/xxx.xxx/site/web/app/themes/theme/assets/scripts/routes/Home.js
8:5 warning Unexpected console statement no-console
â 1 problem (0 errors, 1 warning)
@ ./assets/scripts/main.js 8:0-33
@ multi main
(index):1893 [HMR] Checking for updates on the server...
(index):1893 [HMR] Updated modules:
(index):1893 [HMR] - ./assets/scripts/routes/Home.js
(index):1893 [HMR] App is up to date.
Doesnât matter if I put it in init or finalize, same result. If I put it outside export default { }; I do however get output in the console. Whatâs up with that?
Had renamed theme from sage into something else, when I named it sage again, console.log started working just fine.
How can I rename and have it working? I realized that something could be fishy as publicPath was pointing towards /sage/, but when I changed publicPath into /mytheme/ it failed on finding my custom font instead.