Would be great to provide a documentation section with practical examples on how we propose to handle various popular patterns which usually are solved by pseudo selectors, nested classes etc.

It would be nice to have a babel macro that automatically runs the babel plugin to remove the runtime. That way, this project would work out of the box with "zero" config tools like create-react-app.

I'm thinking it could be something like:

import {html} from 'htm/preact/macro'

This is similar conceptually to CSS-IN-JS libraries providing a macro for their tools. See https://e

During vuera's existence, there were many issues where people had different hard-to-debug problems trying to get vuera running.
I think it would be helpful if there were an example application with everything set up so that people could reference it in case they have problems.

VSCode not giving auto suggestions of file name inside the directory once we are using alias name with babel module resolver plugin for react native .
I am having .js file inside the path @components but it is simply giving the suggestion as
@components/ showing the suggestion as {} react,{} props,{} react-native

My .babelrc file :
{
"presets": [
"react-native"
],

https://swc-project.github.io/docs/usage-plugin

Proposal: create an swc-plugin-macros that is similar to babel-plugin-macros

SWC is increasing in popularity. It is aiming to be a drop-in replacement for babel with some significant speed improvements. It already has a [webpack loader

tl;dr;

Use https://github.com/sharegate/craco.

Create craco.config.js:

const CSS_MODULE_LOCAL_IDENT_NAME = '[local]___[hash:base64:5]';

module.exports = {
  style: {
    modules: {
      camelCase: true,
      localIdentName: CSS_MODULE_LOCAL_IDENT_NAME
    }
  },
  babel: {
    loaderOptions: {
      // Without this Babel caches module name resolution,
      // e.g.

Currently, this monorepo consists of:

• babel-plugin-flow-prepack
• babel-plugin-flow-runtime
• flow-config-parser
• flow-runtime-cli
• flow-runtime-docs
• flow-runtime-mobx
• flow-runtime-validators
• flow-runtime

A subset of these provide the core functionality of flow-runtime:

• flow-runtime-validators
• flow-runtime
• flow-runtime-cli
• babel-plugin-flow-runtime

Meanwhile

const HeaderUser = styled.a`
  font-size: 0;
  width: 42px;
  height: 42px;
  flex-shrink: 0;
  &:hover {
    border: 0;
    margin-top: -10px;
    padding-top: 7px;
    border-top: 3px solid rgb(255, 255, 255);

    /* ${HeaderAvatar} {
      border: 2px solid rgb(255, 255, 255);
    } */
  }
`

=>

ERROR in ./clie

I believe this change in babel-preset-env babel/babel#9781 breaks this plugin. Re-create by upgrading babel-preset-env in this package and run the tests.
I tried going through the code in order to find how to fix it but I didn't manage.

Current usage:

const content = yeah ? 'yeah' : 'nah';
<div
  css={{ content: '"' + content + '"'  }}
>

styled.div({
  content: props => '"' + (props.yeah ? 'yeah' : 'nah') + '"'
})

And it'll work (probably). Would be nice if we didn't need the quotations!

In this ticket make sure that template literal css works great too

styled.div`
  content: ${props => props.c

Issue

Create-React-App has a plugin, ModuleScopePlugin, that stops components from accessing files outside /src/. Apparently, when I import tailwind in a component while using a tailwind.config.js in the root of my project, Tailwind can't access it, and I get this error:

./src/App.js
Module not found: You attempted to import ./../tailwind.config.js which falls outside of 

Although graphql will often already be installed in projects using this module, this isn’t necessarily the case (e.g. when sending queries using graphql-request. If graphql is not installed, attempting to use this module will throw the following error:

Error: Cannot find module 'graphql/language'
Require stack:
(...)

which can be fixed by installing graphql.

Readme says:

NOTE: There's also a separate package available called scope.macro which you can install and use instead if you prefer to type less.

That links to an empty repo. If this package no longer exists, please remove, else please update the link. I'd love to type less :D

I think ts-patch is much easier to setup than ttypescript. I need to test it out though.

Currently downloading the graphql schema is a requirement for babel-plugin-tag to work. It would be useful to specify an URL as an option to the file path.