JoshuaKGoldberg

External Dependencies

i18next

Error: Errors in [email protected] for external dependencies:
Error: node_modules/i18next/index.d.ts(2,34): error TS2691: An import path cannot end with a '.d.ts' extension. Consider importing './typescript/helpers' instead.
Error: node_modules/i18next/index.d.ts(14,8): error TS2691: An import path cannot end with a '.d.ts' extension. Consider importing './typescript/options' instead.
Error: node_modules/i18next/index.d.ts(16,43): error TS2691: An import path cannot end with a '.d.ts' extension. Consider importing './typescript/t' instead.
Error: node_modules/i18next/index.d.ts(497,1): error TS1383: Only named exports may use 'export type'.

JoshuaKGoldberg

function waitFor(time) {
	return new Promise((resolve) => setTimeout(resolve, time));
}

async function acceptVisiblePackages() {
	const containers = document.querySelectorAll("#container");
	for (const container of containers) {
		container.click();
		await waitFor(500);

JoshuaKGoldberg

async function goThroughFlow() {
	const waitFor = (time) => new Promise((resolve) => setTimeout(resolve, time));

	const container = document.getElementById("container");
	container.click();
	await waitFor(1000);

	const choice = document.querySelector(`[name=discloure_choice]`);
	choice.scrollIntoView();
	choice.click();

JoshuaKGoldberg

👉 This has since been posted to DefinitelyTyped's GitHub Discussions: DefinitelyTyped/DefinitelyTyped#65993 👈

Context

👋 Hi all! I've been working with the TypeScript team on overhauling DefinitelyTyped's usage of formatting and linting tools. Alongside the effort to finally migrate from TSLint to ESLint (https://typescript-eslint.io/linting/troubleshooting/tslint -> microsoft/DefinitelyTyped-tools#648), we'd like to align with how much of the industry & many linter maintainers recommend using a formatter vs. a linter (myself included).

This is a surfacing of a plan we've formulated that we think will get DefinitelyTyped onto using a proper formatter for formatting. I'd very much like to see the community's reaction: does this seem reasonable to you? What edge cases are we missing? Will this offend your sensibilities as a program

JoshuaKGoldberg

withastro/roadmap#621

Summary

ESLint is generally considered to be a useful, even necessary, tool for JavaScript/TypeScript web apps. However, configuring it can involve wrangling several configurations and plugins together. It would be useful for many Astro users if npm create astro et al. offered to set up a starting ESLint configuration.

Background & Motivation

Contained here are the most common setup points I think many Astro would need.

JoshuaKGoldberg

// Yes, I know this is super hacky! Don't worry about it.
// In theory we could use mutation observers to check for new elements...
// ...but this worked well enough. 😄

// Used as a script with the Run JavaScript extension:
// https://ataiva.com/run-javascript-chrome-extension-help

async function wait(seconds) {
  await new Promise((resolve) => setTimeout(resolve, seconds));
}

JoshuaKGoldberg

I pretty much went over this post in the class 😄: https://blog.joshuakgoldberg.com/use-effect-pet-peeve/

JoshuaKGoldberg

const { promisify } = require("util");
const { appendFile, writeFile } = require("fs").promises;
const inquirer = require("inquirer");

const exec = promisify(require("child_process").exec);

const execAndPrint = async (command) => {
  console.log(`> ${command}`);
  const { stdout, stderr } = await exec(command);

JoshuaKGoldberg

{
  "extends": ["../../../.eslintrc.json"],
  "rules": {
    "no-restricted-syntax": [
      "error",
      {
        "message": "Don't import from /platform into /portal: if you need, move the shared component to /components instead.",
        "selector": "ImportDeclaration[source.value=/(^|(\\\\.\\\\.\\\\u002F*))platform\\\\u002F(.*)/]"
      }
    ]

JoshuaKGoldberg

/**
 * @example
 * import happy from './assets/happy.svg';
 */
declare module "*.svg" {
    const fileName: string;
    export default fileName;
}