pi0

import { bench, summary, run } from "mitata";
import { createStorage, defineDriver } from "unstorage";
import fsLite from "unstorage/drivers/fs-lite";

const denoDriver = defineDriver((opts) => {
  return {
    async getItem(key: string) {
      const val = await Deno.readTextFile(`${opts.base}/${key}`);
      return val;
    },

pi0

function reportRollupTiming(build) {
  if (!build.getTimings) {
    console.log(
      "Rollup timing information is not available. Make sure `perf: true` config is set."
    );
    return;
  }
  const formatTime = (ms) =>
    ms > 1000 ? `${(ms / 1000).toLocaleString()}s` : `${ms.toLocaleString()}ms`;
  const timings = build.getTimings();

pi0

# The Lazy Coder's Guide to Programming

## Chapter 1: The Art of Copy-Pasting

### Section 1.1: Ctrl+C, Ctrl+V, Repeat

Programming can be hard. But fear not! With the power of copy-paste, you can conquer any coding challenge without breaking a sweat. Just remember: if it works once, it'll work a thousand times. Who needs original code anyway?

## Chapter 2: Debugging 101: Blame the Compiler

pi0

#!/bin/env node
import { existsSync } from 'fs'
import fs from 'fs/promises'
import path from 'path'
import { execSync } from 'child_process'

const LATEST_PNPM = '6.32.3'

const dir = path.resolve(process.argv[2] || '.')
const resolve = (...p) => path.resolve(dir, ...p)

pi0

const Webpackbar = require('webpackbar')

module.exports = {
  webpack: (config, { isServer }) => {
    config.plugins.push(new Webpackbar({ name: isServer ? 'server' : 'client' }))
    return config
  }
}

pi0

(function() {
  const nowOffset = Date.now();
  const now = () => Date.now() - nowOffset;
  global.process.hrtime = global.process.hrtime || ((previousTimestamp) => {
    const baseNow = Math.floor((Date.now() - now()) * 1e-3)
    const clocktime = now() * 1e-3
    let seconds = Math.floor(clocktime) + baseNow
    let nanoseconds = Math.floor((clocktime % 1) * 1e9)

    if (previousTimestamp) {

pi0

Nuxt loads configuration from several places and merges. Here is the order: (first has more periority)

• Config overrides by CLI
• nuxt.config (format: CJS/MJS/TS can be also wrapped into an async function)
• .nuxtrc
• ~/.nuxtrc

In order to automatically inject some configuration without direct modification of nuxt.config, it is possible to use .nuxtrc file.

Thanks to super simpler syntax of rc9 this configuration can be injected via a shell script or package itself.

pi0

const fs = require('fs')
const axios = require('axios')

callback
fs.readFile('test.txt', 'utf-8', (err, str) => {
  if (err) {
    console.error('Something bad!' + err)
  }
 console.log(str)
})

pi0

Nuxt functions implementation specs

Initial RFC: nuxt/rfcs#35

This is a Draft

Introducing a functions/ directory could have a powerful effect for users that want to add server functions but without having to go through serverMiddleware Functions can be also provided by Nuxt modules, for example, CMS module or auth provider can add it's functionalities to the user context.

Usage

pi0

<template>
  <div>
    <component :is="CMSComponent" :x="x" />
    <button @click="x++">
      Click on me
    </button>
  </div>
</template>

<script>