npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

reaction-with-style

v5.0.370

Published

Programmatic styles for Reaction.

Downloads

693

Readme

Reaction with Style

Programmatic styles for Reaction.

To find out what variant of CSS is supported, which is essential to know, please read the With Style readme file.

Installation

With npm:

npm install reaction-with-style

You can also clone the repository with Git...

git clone https://github.com/djalbat/reaction-with-style.git

...then install the dependencies with npm from within the project's root directory:

npm install

You can also run a development server, see the section on building later on.

Example

There is a small development server that can be run from within the project's directory with the following command:

npm start

The example will then be available at the following URL:

http://localhost:8888

The source for the example can be found in the src/example.js file and corresponding src/example folder. You are encouraged to try the example whilst reading what follows. You can rebuild it on the fly with the following command:

npm run watch-debug

The development server will reload the page whenever you make changes.

One last thing to bear in mind is that this package is included by way of a relative rather than a package import. If you are importing it into your own application, however, you should use the standard package import.

Usage

You must call the renderStyles() function after importing the view but before rendering it. Doing so ensures that the styles generated as a result of executing the view code are inserted into the DOM before the view itself.

import withStyle from 'reaction-with-style';

import { ReactDOM } from 'reaction';

import View from './view';

const { renderStyles } = withStyle;

const bodyDOMElement = document.querySelector('body');

renderStyles();

ReactDOM.render(

    <View />

  ,
  bodyDOMElement
);

Note that rendering the styles in this way is not done as part of the build process, you must explicitly call the renderStyles() function, ideally right before you call the ReactDOM.render() function.

Creating primitive components with style

All of the standard HTML elements are supported. For a complete list of tag names, see the tagNames.js file. You can create these components, which are functional components under the hood, as follows:

const Link = withStyle.a`

  color: ${white};
  text-decoration: none;

  @media (min-width: ${desktop}) {
    color: ${black};
  }

`;

Now you are free to use the Link component in the usual way. Note that expression interpolation is supported. For example, here colour and breakpoint variables have been used.

To learn more about template literals in general and expression interpolation in particular, see the relevant MDN page.

Creating functional components with style

This can be done with the withStyle() function:

const Header = (props) => {
  const { className } = props;

  return (

    <header className={className}>

      ...

    </header>

  );
};

export default withStyle(Header)`

  ...

`;

Note that the className property is retrieved from the props object and must be used as the value of the attribute of the same name on the outermost JSX element that the function returns.

Creating class components with style

The process is much the same as for functional components:

class Button extends React.Component {
  render(update) {
    const { className } = this.props;

    return (

      <button className={className}>

        ...

      </button>

    );
  }
}

export default withStyle(AccordionButton)`

  ...

`;

Again the requisite className property is recovered, this time from the this.props object.

Extending the styles of components with style

If all you want to do is to add further styles to a component, be it a primitive, functional or class component, simply wrap it in another withStyle() call:

const HeaderLink = withStyle(Link)`

  ...

`;

In this case the Link component will keep its own styles whilst the HeaderLink component will both inherit those styles and of course possess its own.

Components with style and composition

Composing components with style obviously causes no problems in general, aside from one small caveat. If you set the className property of a component with style, then you will overwrite the class name that has been given to it automatically. In the case of all functional and class components with style, however, it is easy to recover the class name and incorporate it into your own:

const NavigationButton = (props) => {
  const { className } = Button,
        { children } = props;

  return (
    
    <Button className={`${className} navigation`}>
      {children}
    </Button>
    
  );  
}

This situation occasionally arises when using placeholder class names, see below.

Class components with style and class inheritance

It is perfectly permissible to extend class components with style. If you extend a class component with style without applying any further styling, however, you need to be careful if you overload its render() method:

class NavigationButton extends Button {
  render(update) {
    const { className } = Button;

    ...
  }
}

Note that because the NavigationButton class component has no style, the className property can only be recovered from the Button component with style.

If you were to subsequently style the component, however...

export default withStyle(NavigationButton)`

  ...
  
`;

...you would now make use of the style in the render() method conventionally thus:

class NavigationButton extends Button {
  render(update) {
    const { className } = this.props;

    ...
  }
}

Unfortunately you cannot quite have your cake and eat it, meaning that you cannot now use the NavigationButton component without its own style, so to speak, because it's render() method now expects it. However, if you export it wrapped in a withStyle() call, as shown, this can never occur.

Placeholder class names

Class names are randomly generated hashes of around eight characters, and as such are far from ideal when debugging. It is best to add your own placeholder class names, therefore. For functional components the following pattern is recommended:

const MainHeader = (props) => {
  const { className } = props;

  return (

    <header className={`${className} main`}>

      ...

    </header>

  );
};

export default withStyle(MainHeader)`

  ...

`;

For class components the pattern is essentially the same, albeit to be found in the render() method.

Placeholder class names make the association of DOM elements in your browser's developer tools with their corresponding components far easier.

An example of functional classes

Components with style are great for working with styles relating to a component's functionality as opposed to just its appearance.

class Div extends React.Component {}

Object.assign(Div, {
  mixins: [
    hide,
    display,
    isHidden,
    isDisplayed
  ]
});

export default withStyle(Div)`

  .hidden {

    display: none;

   }

`;

function hide() {
  this.addClass('hidden');
}

function display() {
  this.removeClass('hidden');
}

function isHidden() {
  const hidden = this.hasClass('hidden');

  return hidden;
}

function isDisplayed() {
  const hidden = this.isHidden(),
        displayed = !hidden;

  return displayed;
}

In the example above, for example, the component can be programmatically displayed and hidden.

Additional styles

There may be times when you need to add general styles to a page or target the children of DOM elements. In these cases you can make use of the renderStyle() method thus:

import withStyle from 'easy-with-style';   ///

const { renderStyle } = withStyle;

renderStyle(

  ...

);

This will create a separate style DOM element and place your style in there.

Building

Automation is thanks to npm scripts, have a look at the package.json file. The pertinent commands are:

npm run build-debug
npm run watch-debug

Contact