When I try to tap a checkbox, it halves in size horizontally, and then seemingly again when I try to tap it a second time. It only allows me to actually click the radio button on the third time. After halving in size, the wrong radio button has focus.

• figure out server-side redirects
• pass on referrer, source, etc. to "take survey" button
• re-enable sharing buttons?
• mobile version
• main hero image?
• placeholder when no survey is currently open?
• favicon
• better wording all around (stay tuned -> take part in the next survey)
• Add markdown parsing or innerHTML to intro text block
• Double check meta tags

The label for carpal tunnel seems to be incorrect, it looks like a query that got accidentally turned into a string. https://2021.stateofjs.com/en-US/demographics/#disability_status_others

How to Reproduce

Browse to https://2021.stateofcss.com/en-US/technologies

Observed

Charts are missing. There are errors in place of them:

No available data for block scatterplot_overview | path: surveyApi.survey.scatterplot_overview | type: ToolsScatterplotBlock

No available data for block all_sections_tools_cardinality_by_user | path: surveyApi.cardinality | type: AllSectionsToolsCardinalityByUserBlock

Expected

Charts displaying normally.

https://github.com/cure53/DOMPurify

"sanitize-html" is massive and should be kept around only for saving data in Node.
DOMPurify is lighter. I am not yet sure if it works with SSR.

Why Reason is listed as a JavaScript Flavor? Reason is not a JavaScript flavor anymore, it's just a syntax for OCaml that used to be the default option to write JavaScript applications with BuckleScript (a tool that compiles OCaml to JavaScript).
Since BuckleScript was rebranded to ReScript and created its language I think the answers corresponding to "Reason" should be considered as ReScript, because Reason now is focused on the native side and all developers that are using "Reason" to write JavaScript applications are using ReScript. What do you think?

See https://github.com/Devographics/StateOfJS-next2/issues (private repo, this is an internal issue just to keep track of this)

See the surveyform build system for scripts or Vulcan NPM

Adding this would be nice, but it's a little complex to get right especially with i18n.

From the State of CSS 2021 results:

This kind of thing is actually a big antipattern in dataviz. First any data visualization that requires humans to compare areas is already at a disadvantage because humans are pretty bad at comparing areas. But the "circle size" visualization is especially problematic:

• People are usually confused if they need to compare radius or area
• Radius is a poor way to show relationships: a circle with half the radius is π(r/2)² = πr²/4 = a quarter of the area.

A quick demonstration:

Is your intuition about these relationships the same as the numbers displayed?

I would suggest using pie charts instead. The argument about areas still applies, but I think pie charts are fine for communicating a proportion of one variable, they start breaking down when you need to show multiple slices. And they do not suffer from the mismatched percentage shown and proportion of area that "circle size" visualizations have.

I'm moderately green-weak colorblind.

Four of the following categories are indistinguishable to me:

• The colors for Back-end & Build Tools are barely distinguishable when next to each other. They're not so when apart.
• The same goes for Mobile and Monorepo.

:has() 2022
CODE EXAMPLE

/* Matching <a> elements that directly contain an <img> */
a:has(> img)

Similarly for :where()

It seems to me the feature shouldn't be explained as people are more likely to select "Know what it is, but haven't used it" instead of "Never heard of it/Not sure what it is".

Exploiting public data can be tricky without labels, it could be useful to also export a key/translation mapping as csv for each language alongside the public data. Or at least the English version within the data.

The descriptions for the following features on the "Other Features" page are either malformed or entirely missing:

• calc()
• Houdini
• CSS Comparison Functions

Vulcan 0.7.0 brings reversed relations: https://vulcan-docs.vercel.app/docs/vulcan-fire/customFieldResolvers#method-2---assess-if-a-reversed-relation-is-enough-for-you-advanced

To be used for NormalizedResponse, that should extend Response while "Response" should not know about it (NormalizedResponse is an admin-only concept while Response is a shared concept between the core apps and the admin area).

This will let us have a totally separate admin area.

Hi, thanks for all the cool charts!

This positioning on the front-end frameworks satisfaction rankings looks a bit odd:

Svelte's ranking has increased from 89% to 90%, but its trajectory to 2021 is shown as downwards because of the appearance of Solid above it.

Here's a similar thing happening on the build tools listing, because of Vite appearing at 98% over esbuild at 96% - which has actually increased from 94%.

If the years weren't top-aligned it would prevent this from happening.

I'm exploring the idea of doing a "State of GraphQL" survey, so I'm opening this thread to gather feedback.

• If you use GraphQL, which questions would you hope the survey would answer?
• Which areas should it cover?
• Which features/architecture patterns/libraries/services should be included?
• What other questions can we ask to get a better picture of the GraphQL community?
• What are the main current GraphQL pain points we should ask about?
• What are the main currently missing features we should ask about?

Let me know here!

Feature

Library

What's New

• Ability to group options together for added clarity.
• Any top-level option has the ability to trigger an inline follow-up question when checked.
• Follow-up questions support an "Other…" free-form field
• Note: avoid triggering follow-ups for too many top level options to avoid increasing survey length too much.

https://2021.stateofcss.com/images/favicon.svg returns 404.

Some charts, like the back end frameworks, are showing errors instead of loading.

See https://developer.mozilla.org/en-US/docs/Web/CSS/contain contain is not in code in CSS results site.

I noticed that some section titles start out showing something like "Css2022__something__something" and second or so later change to the proper title. The section title "Css2022__resources__podcasts_css__others" under "Resources" didn't change at all.

I see an error in the console, not sure if it's related:

2instrument.js:109 currentFocusIndex was not null, but currentTabindex was null during keypress
(anonymous) @ instrument.js:109

This occurs both in JS 2021 and CSS 2021 surveys.

https://2021.stateofjs.com/en-US/about#project-funding
https://2021.stateofcss.com/en-US/about#project-funding

The data is coming from Markdown inside YAML files, but to me they look fine...

https://github.com/StateOfJS/locale-en-US/blob/fd2eeeaef7f36c2eafe4324df290d7215d1a4101/state_of_js_2021_results.yml#L392-L409

https://survey.devographics.com/survey/state-of-graphql/2022

Thank you for including StepZen in the question about tools you use to combine, aggregate, or merge GraphQL schemas from different APIs.

Possible to addd StepZen to the “API Generators” and "GraphQL Servers" categories?
Developers can create schemas for REST, database, SOAP, etc data sources using StepZen
and GraphQL APIs runs on StepZen (as a service)

prefer reduced motion url - https://developer.mozilla.orghttps//developer.mozilla.org/en-US/docs/Web/CSS/CSS_Grid_Layout
Grid - https://developer.mozilla.orghttps//developer.mozilla.org/en-US/docs/Web/CSS/CSS_Grid_Layout

To consider:

• https://slinkity.dev/
• LinkedIn Learning (formerly Lynda)
• https://parceljs.org/blog/parcel-css/
• Add "how could we improve this survey" question
• Add "other surveys" resources question
• Add Stencil?
• Add a "Slack/Discord/IRC" category?
• Add "what do you use JS for?" question
• https://github.com/BuilderIO/qwik
• htmx

It seems that relying on a custom CLI tool or binary requires a custom Docker image on Render.com.

• Try to get binaries built for mongoexport? Not sure it can work, but see https://community.render.com/t/install-custom-packages-on-my-deploy-do-i-need-docker/5857
• Otherwise try deployment with a custom Dockerfile => almost there but somehow the file structure of the end image is wrong. Anyway a Docker image on a monorepo will be very bristle
• Add mongoexport to the Dockerfile

Current process:

• Run the app locally, but with MONGO_URI aiming at the prod db (careful on that)
• Connect as admin /!\ when connecting via anonymous login, it will find based on emailHash, but via password login, via pure email => I need to clean this part up a bit
• Export from your own machinge

receiving the following error when trying to view frontend framework rankings:

Cannot read properties of undefined (reading 'percentage_question')

Tried to see the back-end results but it sais that o is undefined. It's the same for front-end and all the others on the tab "Libraries"

This isn't a good practice. It annoys potential buyers into avoiding donation altogether, because they didn't even get what they came for before you started begging. Putting a donate link in the sidebar/footer is a much better, more generally accepted way of providing people who want to donate with the means of doing so.

On the report part related to Monorepo tools (https://2021.stateofjs.com/en-US/libraries/monorepo-tools/), the recommended resources features outdated training from Frontend Masters.

I believe the link to monorepo.tools, de facto most up-to-date overview of the modern monorepo solutions, maintained by monorepo creators themselves provide more relevant information.

Unless these are paid adverts, in which case the "Recommended resources" is a bit misleading.

https://2021.stateofjs.com/en-US/libraries/
click the "Data" button on right

The introduction said that all questions would have the option to add additional comments. I noticed in the "CSS Usage" section that the comment button is not present. Maybe double-check all questions and add it where it should be available.

(Outline WIP available here).

Deletions

The two big changes I'm planning are to remove the "JavaScript Flavors" and "Data Layer" sections.

JavaScript Flavors

TypeScript has almost 100x the usage of any other options, so setting aside a whole section for this category feels a bit superfluous at this point. Technologies like Reason or Elm are still very interesting but maybe they have their place in a more targeted survey?

Data Layer

This has always been a somewhat nebulous category, and would probably be better served by library-specific surveys (how to manage state in React, how to manage state in Svelte, etc.).

Features

• async_await
• promises
• destructuring
• spread_operator
• arrow_functions
• local_storage
• fetch

(These are removed because they're pretty much at 100% usage and/or awareness so it doesn't make a ton of sense to keep asking about them)

• decorators (not actually implemented yet so not the best section for them?)

Libraries

• koa
• meteor
• hapi

Other Deletions

• Text Editors

Additions

Since the deletions free up space, maybe we could add a new category such as Animations and Graphics? Or else just keep the survey shorter.

Features

• numeric_separators
• replace_all
• match_all
• logical_assignment
• promise_any
• array_at
• top_level_await
• page_visibility
• broadcast_channel
• geolocation
• file_system_access
• web_share

Libraries

• Solid
• Redwood
• Blitz
• Astro
• Eleventy
• Sveltekit
• Remix
• Vite
• WMR
• Turborepo
• Tauri
• pnpm
• Vitest

I also want to open the discussion regarding which features/browser APIs should be included.

See above

Here is the outline for the survey in markdown format. I coded up the export pretty quickly so it's a bit rough, feel free to disregard any weirdness of things that don't make sense. I will also deploy a preview of the actual survey soon. Feedback welcome!

[Updated May 12 2022]

State of GraphQL 2022

Language

The vocabulary of JavaScript.

features_intro

Custom Directives

• Never heard|Know what it is|Used it

Custom Scalars

• Never heard|Know what it is|Used it

Fragments

• Never heard|Know what it is|Used it

Unions

• Never heard|Know what it is|Used it

Interfaces

• Never heard|Know what it is|Used it

Directives

Augmenting your GraphQL fields.

@Skip

• Never heard|Know what it is|Used it

@include

• Never heard|Know what it is|Used it

@deprecated

• Never heard|Know what it is|Used it

@SpecifiedBy

• Never heard|Know what it is|Used it

@defer

• Never heard|Know what it is|Used it

@stream

• Never heard|Know what it is|Used it

Security & Performance

Making your API more robuts.

Persisted Queries

• Never heard|Know what it is|Used it

Query Timeouts

• Never heard|Know what it is|Used it

Query Rate Limiting

• Never heard|Know what it is|Used it

Query Depth Limiting

• Never heard|Know what it is|Used it

Query Cost Analysis

Analyzing a set of factors before deciding whether to allow a query.

• Never heard|Know what it is|Used it

Disabling Introspection

• Never heard|Know what it is|Used it

IP Allow-listing

Only allowing a predefined set of IP addresses to access an API.

• Never heard|Know what it is|Used it

Requiring Authentication

Require authentication before any API access.

• Never heard|Know what it is|Used it

Other Features

Other technologies and patterns

GraphQL Subscriptions

• Never heard|Know what it is|Used it

Live Queries

• Never heard|Know what it is|Used it

Apollo Federation

• Never heard|Know what it is|Used it

Schema Stitching

• Never heard|Know what it is|Used it

GraphQL Servers

How you power your API.

tools_intro

Apollo Server

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

Yoga

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

GraphQL.js

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

Helix

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

Express-GraphQL

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

Mercurius

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

Hot Chocolate

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

GraphQL Java

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

DGS

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

Strawberry

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

Sangria

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

graphql_servers

graphql_servers

• Very Unhappy
• Unhappy
• Neutral
• Happy
• Very Happy

GraphQL Clients

Querying your API.

Apollo Client

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

URQL

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

React Query

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

Relay

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

Apollo iOS

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

SwiftGraphQL

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

Apollo Kotlin

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

GraphQL Hooks

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

graphql-request

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

no_dedicated_client

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

graphql_clients

graphql_clients

• Very Unhappy
• Unhappy
• Neutral
• Happy
• Very Happy

API Generators

ORMs, CMSes, and other tools that create an API for you.

PostGraphile

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

Hasura

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

GraphCMS

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

DatoCMS

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

Sanity

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

WPGraphQL

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

WunderGraph

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

Fauna

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

Dgraph

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

GraphQL Editor

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

Strapi

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

AWS AppSync

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

Contentful

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

Pothos

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

api_generators

api_generators

• Very Unhappy
• Unhappy
• Neutral
• Happy
• Very Happy

Code Generators

Generators, schema builders, and other libraries that write part of your code for you.

GraphQL Zeus

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

Genql

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

GraphQL Code Generator

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

Nexus

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

TypeGraphQL

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

graphql_code_generators

graphql_code_generators

• Very Unhappy
• Unhappy
• Neutral
• Happy
• Very Happy

GraphQL IDEs

Apps and services that help you query your GraphQL API.

GraphiQL

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

GraphQL Playground

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

Apollo Studio

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

Altair

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

Insomnia

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

Postman

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

GraphQL Editor

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

Apollo Sandbox

• Never heard|Would like to learn|Not interested|Would use again|Would not use again

graphql_ides

graphql_ides

• Very Unhappy
• Unhappy
• Neutral
• Happy
• Very Happy

Usage

How you use GraphQL.

GraphQL Experience

How long have you been using GraphQL for?

• Less than one year
• 1 to 2 years
• 3 to 5 years
• 6 to 10 years

API Types

What kind of APIs do you use GraphQL for?

• Publicly-available APIs intended for third-party developers
• APIs intended for your own website and/or apps
• Private APIs for internal usage

API Clients

What kind of clients connect to your APIs?

• Browsers
• Native Mobile Apps
• Native Desktop Apps
• Other Servers

Data Sources

Which kind of data sources are consumed by your GraphQL APIs?

• Static files (YAML, Markdown, etc.)
• Databases
• Spreadsheets
• CMSes
• REST APIs
• Other GraphQL APIs

Code Generation Type

If you use code generation, which approaches do you tend to prefer?

• Code-first (JS, TS, JSON, etc.)
• GraphQL Schema-first
• Database-first

Code Generation Target

Which part(s) of your codebase do you generate programatically?

• GraphQL schema
• Non-GraphQL (e.g. TypeScript) typings
• Server resolvers
• Client-side fragments and/or queries
• Client-side query code (e.g. React hooks)

Industry Sectors

Which industry sector(s) are you using GraphQL in?

• Ecommerce & Retail
• News, Media, & Blogging
• Healthcare
• Finance
• Programming & Technical Tools
• Social Media
• Marketing/Sales/Analytics Tools
• Education
• Real Estate
• Entertainment
• Government
• Consulting & Services

Other Server Languages

Which language(s) do you use to write your GraphQL back-ends?

• JavaScript
• TypeScript
• PHP
• Ruby
• Python
• Go
• Rust
• Java
• C/C++
• Objective-C
• Scala
• Swift
• C#
• Haskell
• OCaml
• Dart
• Kotlin
• Elixir
• Clojure
• Julia

Web Frameworks

Web frameworks that you use in conjunction with GraphQL.

• Gatsby
• Redwood
• Next.js
• Remix
• Nuxt
• SvelteKit
• Create React App

Databases

Which databases do you use in conjunction with GraphQL?

• MySQL
• SQLite
• PostgreSQL
• Neo4j
• Redis
• MongoDB
• ElasticSearch
• DynamoDB

GraphQL Strong Points

What are the main reasons why you enjoy using GraphQL?

• Avoiding Over-fetching
• Introspection & API Documentation
• Tooling & Ecosystem
• Type-checking
• Combining Different APIs
• Aggregating Requests
• Community
• Fragment Colocation

GraphQL Strong Points

What are the main reasons why you enjoy using GraphQL?

GraphQL Pain Points

What are your main pain points when using GraphQL?

• Performance
• Security
• Combining Different Schemas
• API Versioning
• File Upload
• Testing
• Error Handling
• Client-side Caching

GraphQL Pain Points

What are your main pain points when using GraphQL?

Other GraphQL Tools

• Envelop
• GraphQL Mesh
• GraphQL Shield
• Dataloader
• options.other_tools.datasources
• GraphQL Voyager
• graphqurl
• GraphCDN
• Apollo Client Devtools
• GraphQL Hive
• GraphQL Inspector
• GraphQL Scalars
• GraphQL Config
• GraphQL Modules
• Prisma

state_of_graphql

• Very Unhappy
• Unhappy
• Neutral
• Happy
• Very Happy

Resources

What {topic} resources do you consult?

First Steps With GraphQL

When first starting out, how did you initially learn GraphQL?

• Books
• Videos & screencasts
• Online courses (free)
• Online courses (paid)
• School & higher education
• Podcasts
• Coding bootcamp
• On-the-job training
• Mentoring
• Self-directed learning (Google, Stack Overflow, etc.)

Blogs & Magazines

Which blogs/magazines/etc. do you read?

Sites & Courses

Which sites/courses/etc. do you consult?

Podcasts

Which programming-related podcasts do you listen to?

Other Surveys

Which other developer surveys do you participate in?

• JetBrains State of Developer Ecosystem
• Stack Overflow Annual Developer Survey
• CodinGame Developer Survey
• Design Tools Survey
• Postman State of the API Report

People

People you read, follow, or just want to highlight.

About You

Let's get to know the real you.

Age

How old are you, in years?

• Under 10 years old
• 10-18 years old
• 18-24 years old
• 24-34 years old
• 35-44 years old
• 45-54 years old
• 55-64 years old
• 65 years or older

Years of Experience

How long have you been working or studying in this field, in years?

• Less than one year
• 1 to 2 years
• 2 to 5 years
• 5 to 10 years
• 10 to 20 years
• More than 20 years

Company Size

How big is your company, in number of employees?

• One employee
• 1 to 5 employees
• 5 to 10 employees
• 10 to 20 employees
• 20 to 50 employees
• 50 to 100 employees
• 100 to 1000 employees
• More than 1000 employees

Yearly Salary

Your yearly salary in U.S. dollar.

• I work for free
• $0k-$10k
• $10k-$30k
• $30k-$50k
• $50k-$100k
• $100k-$200k
• More than $200k

Higher Education Degree

Do you have a higher education degree?

• No
• Yes, in a field related to my current profession
• Yes, but in a field unrelated to my current profession

Your Country or Region

Where do you currently reside?

list of countries goes here

Gender

Which of the following options describes you, if any? Please pick one.

• Woman
• Man
• Non-Binary or Gender Non-Conforming
• Not Listed

Race & Ethnicity

Which of the following options describe you, if any? Please check all that apply.

• Black or of African descent
• East Asian
• Hispanic or Latino/Latina/Latinx
• Middle Eastern
• Multiracial
• Native American, Pacific Islander, or Indigenous Australian
• South Asian
• South East Asian
• White
• Not listed

Disability Status

Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries.

• Visual impairments

• Hearing impairments

• Mobility impairments

• Cognitive impairments

• Not Listed

How did you find out about this survey?

Al menos en la parte de frameworks salta un error 404 al copiar el link para compartir

Hi,
I would like to contact the team after reading the survey, but the link at the bottom has a mailto without any email address inside.

mailto:?subject=The State of CSS 2021 Survey Results&body=Here are some interesting survey results: https://2021.stateofcss.com

*I didn't find the stateOfCSS2021 to publish this issue ( I have just clicked at the bottom link of the website "Found a bug? Leave an issue" ).

Astro codebase: https://github.com/StateOfJS/Monorepo/tree/main/homepage

Context defined here: https://github.com/StateOfJS/Monorepo/blob/main/homepage/src/helpers/i18nContext.tsx

Provider called here: https://github.com/StateOfJS/Monorepo/blob/main/homepage/src/layouts/DefaultLayout.astro#L42

Context used here via a hook: https://github.com/StateOfJS/Monorepo/blob/main/homepage/src/components/T.tsx#L15

Problem: when using the context in a component, only the default value of the context is read, the context is never updated with the value passed to the provider.

This is the CSS library evaluation chart in the Japanese version:

And here's the same section in the English version:

Somehow the widths of titles in the Japanese version is about half the size of those in the English version. Since the width is narrower, some titles (in this case, "ドキュメンテーション", "アクセシビリティ", and "ユーザーベース") are chopped.

There might be no choice if the strings are too large... but unlike the English version, those Japanese title are not truncated with ellipsis, and are right-aligned with no scrolling mechanism. So there's no way to see the start of the string, making it hard to get the meaning of those long titles.

How to Reproduce

• Browse to https://2021.stateofcss.com/en-US/features/other-features#containment
• Click the "CanIUse" link in this section

Observed

The link points to https://caniuse.com/undefined

Expected

The link points to https://caniuse.com/css-containment

The link to CanIUse is broken for the section on color-contrast on the Accessibility page.
https://2021.stateofcss.com/en-US/features/accessibility/

Feels like it's probably a typo, but on the off chance it's me, I'm using Firefox mobile, on Android.

Ought to be the link: https://caniuse.com/mdn-css_types_color_color-contrast

https://github.com/StateOfJS/Monorepo/blob/f1d5860848312b85f1993f5eebf1e540d1a8359d/api/README.md#L45

This may just be me missing something, but looking at the CSS feature results from 2021 I cannot tell what percentage of respondents knew about each feature. My understanding is that the circles are showing essentially this percentage:

                      People using the feature
----------------------------------------------------------------
(People using the feature + People that knew about the feature)

The overlay provides more data, but still about usage:

What I was interested in was this percentage:

People that knew about the feature + People using the feature
----------------------------------------------------------------
                       Total respondents

Is this shown anywhere?

Also, the percentage of total respondents that use the feature would IMO be more useful than the percentage of people who use it over the percentage of people who know about it. If a feature is known by 1% of developers but almost everyone who knows about it uses it that gives us a huge usage percentage which does not actually reflect how widely the feature is used at all.

Leave your feedback or ask your questions regarding the chart sponsoring/donations feature here.

Getting 404s when using the Share -> get link feature:

https://2021.stateofjs.com/en-US/other-tools/javascript_flavors

Steps to reproduce

• Browse to https://2021.stateofcss.com/en-US/features/other-features
• Click the chain-link that appears on hover next to the "CSS Variables (Custom Properties)" title
• 404

Observed

Clicking on any of the chain-links next to a title results in a 404.

Expected

Clicking on any of the chain-links next to a title should jump to the permalink for that section.

Analysis

The generated link does not include a # in front of the anchor.