npm init -y
Create a folder called src and add an empty index.js file. The code that webpack compiles goes in here including any Javascript modules and the main Tailwind file.
| >!a::Send {U+00E2} | |
| >!c::Send {U+00E7} | |
| >!g::Send {U+011F} | |
| >!i::Send {U+0131} | |
| >!o::Send {U+00F6} | |
| >!s::Send {U+015F} | |
| >!u::Send {U+00FC} | |
| >!+a::Send {U+00C2} | |
| >!+c::Send {U+00C7} | |
| >!+g::Send {U+011E} |
The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.
This means you have the following choices:
import foo from 'foo' instead of const foo = require('foo') to import the package. You also need to put "type": "module" in your package.json and more. Follow the below guide.await import(…) from CommonJS instead of require(…).| function insert(obj, {before, property, value}) { | |
| let found, temp = {}; | |
| // Delete all properties from before onwoards and save them in temp | |
| for (let p in obj) { | |
| if (p === before) { | |
| found = true; | |
| } | |
| if (found) { |
| // create a bookmark and use this code as the URL, you can now toggle the css on/off | |
| // thanks+credit: https://dev.to/gajus/my-favorite-css-hack-32g3 | |
| javascript: (function() { | |
| var elements = document.body.getElementsByTagName('*'); | |
| var items = []; | |
| for (var i = 0; i < elements.length; i++) { | |
| if (elements[i].innerHTML.indexOf('* { background:#000!important;color:#0f0!important;outline:solid #f00 1px!important; background-color: rgba(255,0,0,.2) !important; }') != -1) { | |
| items.push(elements[i]); | |
| } | |
| } |
| Bu sorun ile karşılaştığımda sorunun benden kaynaklandığını düşünüp tekrar ve tekrar yazarak yanlış olan kısmı çözmeye çalışmıştım ama | |
| nafile idi :( Bu sorunu yaşayan bir çok kişi varmış meğersem. | |
| Yapmaya çalıştığım şey; | |
| Bs nav-tabs kullanarak her bir kategoriye tıkladığımızda aktif olan kategorinin içerisinde slider olacak | |
| <nav> | |
| <div class="nav nav-tabs" id="nav-tab" role="tablist"> | |
| <a class="nav-item nav-link active" id="nav-home-tab" data-toggle="tab" href="#nav-home" role="tab" aria-controls="nav-home" aria-selected="true">Kategori 1</a> |
| <?php | |
| /** | |
| * Plugin name: WP Trac #42573: Fix for theme template file caching. | |
| * Description: Flush the theme file cache each time the admin screens are loaded which uses the file list. | |
| * Plugin URI: https://core.trac.wordpress.org/ticket/42573 | |
| * Author: Weston Ruter, XWP. | |
| * Author URI: https://weston.ruter.net | |
| */ | |
| function wp_42573_fix_template_caching( WP_Screen $current_screen ) { |
| <?php | |
| function replace_between($str, $needle_start, $needle_end, $replacement = '') | |
| { | |
| return preg_replace('/' . $needle_start . '.+?' . $needle_end . '/sm', $replacement, $str); | |
| } |
FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent