State of JS 2025 Preview

- Previous suggestions: https://github.com/Devographics/surveys/issues/255
- Preview the survey: https://survey.devographics.com/en-US/survey/state-of-js/2025

## Features

#### Added

- Iterator Methods
- Scheduler API
- URLPattern
- RegExp.escape
- structuredClone()? (old but has never been in the surveys)

- New Native Type question options:
- Runtime types (Types that are parsed at runtime by the browser)
- Type annotations (Compiler-level TypeScript-like type annotations that get stripped during bundling)
- JSDoc-like types (JSDoc-like types written as code comments)

## Libraries

- Bring back "Back end Frameworks" section
- Added Bun in Build Tools category
- Added Analog and Quasar to meta-frameworks category
- Downgraded "Mobile & Desktop" section
- Downgraded "Monorepo Tools" section

## Other Tools

- Brought back Utilities question (ESLint/Biome/etc.)
- Brought back Text Editors/IDEs question
- Add "Mobile & Desktop" section here
- Add "Monorepo Tools" section here

## Usage

- Add: "I would prefer to use JavaScript without a build step" (agree/disagree/etc.)

## Other Pending Questions

1. Is it worth asking if people want runtime types?
- pro: some people [do want them](https://www.reddit.com/r/typescript/comments/13twezh/askts_what_do_you_think_will_be_the_future_of/) and are already finding workarounds to have them.
- cons: not realistically going to be implemented natively (although we can use the results as an opportunity to educate people about why that is not possible)
2. Anything to add/remove from "Which of these active JavaScript proposals are you most excited about?" question?
3. Anything to add/remove from "What do you feel is currently missing from JavaScript?" question?
4. What is the status of JSSugar? Should we ask about that?
5. There's also a parallel movement of standards-focused, no-build JS (see [Remix blog post](https://remix.run/blog/wake-up-remix), "religiously runtime" for example). How could we best measure interest in this?