snellingio

const plugin = require('tailwindcss/plugin')

module.exports = {
    mode: 'jit',
    purge: ['./resources/**/*.{js,vue,blade.php}'],
    darkMode: false, // or 'media' or 'class'
    theme: {
        extend: {},
    },
    variants: {

samselikoff

const plugin = require("tailwindcss/plugin");

module.exports = {
  mode: "jit",
  purge: {
    content: ["./src/**/*.{js,ts,jsx,tsx,mdx,vue}"],
  },
  theme: { extend: {} },
  variants: {},
  plugins: [

sindresorhus

Pure ESM package

The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.

This means you have the following choices:

1. Use ESM yourself. (preferred)
   Use 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.
2. If the package is used in an async context, you could use await import(…) from CommonJS instead of require(…).
3. Stay on the existing version of the package until you can move to ESM.

freekmurze

<?php

use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Support\Facades\Schema;

class MigrateToJetstream extends Migration
{
    public function up()
    {

spoonerWeb

definitions:
  caches:
    composer: vendor/
    node: frontend/node_modules
  steps:
    - step: &composer
        name: "Install project via composer"
        image: composer:2
        caches:
          - composer

tannerlinsley

Replacing Create React App with the Next.js CLI

How dare you make a jab at Create React App!?

Firstly, Create React App is good. But it's a very rigid CLI, primarily designed for projects that require very little to no configuration. This makes it great for beginners and simple projects but unfortunately, this means that it's pretty non-extensible. Despite the involvement from big names and a ton of great devs, it has left me wanting a much better developer experience with a lot more polish when it comes to hot reloading, babel configuration, webpack configuration, etc. It's definitely simple and good, but not amazing.

Now, compare that experience to Next.js which for starters has a much larger team behind it provided by a world-class company (Vercel) who are all financially dedicated to making it the best DX you could imagine to build any React application. Next.js is the 💣-diggity. It has amazing docs, great support, can grow with your requirements into SSR or static site generation, etc.

So why

acf-extended

<?php

/*
 * TinyMCE: Add Tailwind CSS style
 */
add_editor_style('/assets/css/tailwind.min.css');

/*
 * TinyMCE: Remove WP styles
 */

yanknudtskov

<?php

/**
 * Example: Add order meta to the REST API
 * WC 2.6+
 *
 * @param \WP_REST_Response $response The response object.
 * @param \WP_Post $post Post object.
 * @param \WP_REST_Request $request Request object.
 * @return object updated response object

llagerlof

<?php
// original author: https://www.php.net/manual/en/function.print-r.php#93529
// another dev said it was fixed for null values, but I don't encountered errors with null values for Matt's: https://www.php.net/manual/en/function.print-r.php#121259

// Matt
function print_r_reverse($in) {
    $lines = explode("\n", trim($in));
    if (trim($lines[0]) != 'Array') {
        // bottomed out to something that isn't an array
        return $in;

opejovic

.animated-placeholder {
    background: linear-gradient(-90deg, #eef2f6, #ffffff, #bcbfc3);
    background-size: 400% 400%;

    -webkit-animation: left-to-right 3s ease infinite;
    -moz-animation: left-to-right 3s ease infinite;
    animation: left-to-right 3s ease infinite;
}

@-webkit-keyframes left-to-right {