Giter VIP home page Giter VIP logo

preact-helmet's Introduction

Preact Helmet

A document head manager for Preact

This project is a port of react-helmet to Preact, the 3kB lightweight React alternative.

npm Version Build Status Dependency Status PRs Welcome

This Preact component will manage all of your changes to the document head with support for document title, meta, link, style, script, noscript, and base tags.

Inspired by:

Table of Contents generated with DocToc

Examples

import {h} from "preact"; /** @jsx h */
import Helmet from "preact-helmet";

export default function Application () {
    return (
        <div className="application">
            <Helmet title="My Title" />
            ...
        </div>
    );
};
import {h} from "preact"; /** @jsx h */
import Helmet from "preact-helmet";

export default function Application () {
    return (
        <div className="application">
            <Helmet
                htmlAttributes={{lang: "en", amp: undefined}} // amp takes no value
                title="My Title"
                titleTemplate="MySite.com - %s"
                defaultTitle="My Default Title"
                titleAttributes={{itemprop: "name", lang: "en"}}
                base={{target: "_blank", href: "http://mysite.com/"}}
                meta={[
                    {name: "description", content: "Helmet application"},
                    {property: "og:type", content: "article"}
                ]}
                link={[
                    {rel: "canonical", href: "http://mysite.com/example"},
                    {rel: "apple-touch-icon", href: "http://mysite.com/img/apple-touch-icon-57x57.png"},
                    {rel: "apple-touch-icon", sizes: "72x72", href: "http://mysite.com/img/apple-touch-icon-72x72.png"}
                ]}
                script={[
                    {src: "http://include.com/pathtojs.js", type: "text/javascript"},
                    {type: "application/ld+json", innerHTML: `{ "@context": "http://schema.org" }`}
                ]}
                noscript={[
                    {innerHTML: `<link rel="stylesheet" type="text/css" href="foo.css" />`}
                ]}
                style={[
                  {type: "text/css", cssText: "body {background-color: blue;} p {font-size: 12px;}"}
                ]}
                onChangeClientState={(newState) => console.log(newState)}
            />
            ...
        </div>
    );
};

Features

  • Supports title, base, meta, link, script, noscript, and style tags.
  • Attributes for html and title tags.
  • Supports isomorphic/universal environment.
  • Nested components override duplicate head changes.
  • Duplicate head changes preserved when specified in same component (support for tags like "apple-touch-icon").
  • Callback for tracking DOM changes.

Installation

npm install --save preact-helmet

Server Usage

To use on the server, call rewind() after using render from preact-render-to-string to get the head data for use in your prerender.

Because this component keeps track of mounted instances, you have to make sure to call rewind on server, or you'll get a memory leak.

import { render } from 'preact-render-to-string'
import Helmet from 'preact-helmet'

const markup = renderToString(<MyApp />);
const head = Helmet.rewind();

// populate some document template using `markup` and `head`
const html = `
    <!doctype html>
    <html>
        <head>
            ${head.title.toString()}
            ${head.meta.toString()}
            ${head.link.toString()}
        </head>
        <body>
            <div id="content">
                ${markup}
            </div>
        </body>
    </html>
`;

head contains the following properties:

  • htmlAttributes
  • title
  • base
  • meta
  • link
  • script
  • noscript
  • style

Each property contains toComponent() and toString() methods. Use whichever is appropriate for your environment. For htmlAttributes, use the JSX spread operator on the object returned by toComponent(). E.g:

As string output

const html = `
    <!doctype html>
    <html ${head.htmlAttributes.toString()}>
        <head>
            ${head.title.toString()}
            ${head.meta.toString()}
            ${head.link.toString()}
        </head>
        <body>
            <div id="content">
                ${markup}
            </div>
        </body>
    </html>
`;

As Preact components

If you are doing server side rendering with Preact, it may be easier to render the document template with Preact as well:

function HTML({head}) {
    const attrs = head.htmlAttributes.toComponent();

    return (
        <html {...attrs}>
            <head>
                {head.title.toComponent()}
                {head.meta.toComponent()}
                {head.link.toComponent()}
            </head>
            <body>
                <div id="content">
                    <MyApp />
                </div>
            </body>
        </html>
    );
}

Use Cases

  1. Nested or latter components will override duplicate changes.
<Helmet
    title="My Title"
    meta={[
        {"name": "description", "content": "Helmet application"}
    ]}
/>
<Helmet
    title="Nested Title"
    meta={[
        {"name": "description", "content": "Nested component"}
    ]}
/>

Yields:

<head>
    <title>Nested Title</title>
    <meta name="description" content="Nested component">
</head>
  1. Use a titleTemplate to format title text in your page title
<Helmet
    title="My Title"
    titleTemplate="%s | MyAwesomeWebsite.com"
/>
<Helmet
    title="Nested Title"
/>

Yields:

<head>
    <title>Nested Title | MyAwesomeWebsite.com</title>
</head>
  1. Duplicate meta and/or link tags in the same component are preserved
<Helmet
    link={[
        {"rel": "apple-touch-icon", "href": "http://mysite.com/img/apple-touch-icon-57x57.png"},
        {"rel": "apple-touch-icon", "sizes": "72x72", "href": "http://mysite.com/img/apple-touch-icon-72x72.png"}
    ]}
/>

Yields:

<head>
    <link rel="apple-touch-icon" href="http://mysite.com/img/apple-touch-icon-57x57.png">
    <link rel="apple-touch-icon" sizes="72x72" href="http://mysite.com/img/apple-touch-icon-72x72.png">
</head>
  1. Duplicate tags can still be overwritten
<Helmet
    link={[
        {"rel": "apple-touch-icon", "href": "http://mysite.com/img/apple-touch-icon-57x57.png"},
        {"rel": "apple-touch-icon", "sizes": "72x72", "href": "http://mysite.com/img/apple-touch-icon-72x72.png"}
    ]}
/>
<Helmet
    link={[
        {"rel": "apple-touch-icon", "href": "http://mysite.com/img/apple-touch-icon-180x180.png"}
    ]}
/>

Yields:

<head>
    <link rel="apple-touch-icon" href="http://mysite.com/img/apple-touch-icon-180x180.png">
</head>
  1. Only one base tag is allowed
<Helmet
    base={{"href": "http://mysite.com/"}}
/>
<Helmet
    base={{"href": "http://mysite.com/blog"}}
/>

Yields:

<head>
    <base href="http://mysite.com/blog">
</head>
  1. defaultTitle will be used as a fallback when the template does not want to be used in the current Helmet
<Helmet
    defaultTitle="My Site"
    titleTemplate="My Site - %s"
/>

Yields:

<head>
    <title>My Site</title>
</head>

But a child route with a title will use the titleTemplate, giving users a way to declare a titleTemplate for their app, but not have it apply to the root.

<Helmet
    defaultTitle="My Site"
    titleTemplate="My Site - %s"
/>

<Helmet
    title="Nested Title"
/>

Yields:

<head>
    <title>My Site - Nested Title</title>
</head>

And other child route components without a Helmet will inherit the defaultTitle.

  1. Usage with <script> tags:
<Helmet
    script={[{
        "type": "application/ld+json",
        "innerHTML": `{
            "@context": "http://schema.org",
            "@type": "NewsArticle"
        }`
    }]}
/>

Yields:

<head>
    <script type="application/ld+json">
      {
          "@context": "http://schema.org",
          "@type": "NewsArticle"
      }
    </script>
</head>
  1. Usage with <style> tags:
<Helmet
    style={[{
        "cssText": `
            body {
                background-color: green;
            }
        `
    }]}
/>

Yields:

<head>
    <style>
        body {
            background-color: green;
        }
    </style>
</head>

Contributing to this project

Please take a moment to review the guidelines for contributing.

License

MIT

More Examples

react-helmet-example (for React, but still useful)

preact-helmet's People

Contributors

andykenward avatar artazor avatar athomann avatar avaly avatar bryanrsmith avatar cesarandreu avatar cwelch5 avatar dattran92 avatar dhoward avatar doctyper avatar download avatar felixsanz avatar gaearon avatar greenkeeperio-bot avatar jamsea avatar jasonblanchard avatar jirutka avatar jmurzy avatar katt avatar koenpunt avatar lourd avatar matthewheck avatar mull avatar neilius avatar nuc avatar ooade avatar potench avatar romanonthego avatar taak77 avatar tmbtech avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar

preact-helmet's Issues

Update test suite based on v5

No need to fix all tests yet. Instead just create issues for them and people might be able to lend us a hand in fixing them.

  • Copy tests from nfl/react-helmet v5
  • Change build scripts to use the new tests
  • Remove old tests
  • Change tests to depend on Preact i.s.o on React

Maintainers wanted

@IrvingArmenta
@rosenbjerg
@squidfunk
@DamianoMagrini
@acangiani
@DannyAziz

Hi Guys,

There was a time, not too long ago, that I was completely in love with Preact. And in fact, I still am. But I have not had the opportunity to use Preact in a while now and I don't see it coming in the very near future so I don't really have the motivation / time at the moment to maintain this project in my spare time... which is a shame if this code is actually helping you guys, which is what I as an Open Source developer dream of.

So maybe some of you guys would be willing to pick up the ball so to speak and help me maintain this thing?
Basically I will give you 'da power' to do what you want with this repo. I'll also try to help set it up so you guys can publish to NPM by yourselves.

What do you say?

Add more collaborators?

Hey,

I see that this project is not in sync with react-helmet anymore. There are also a few open pull requests.

Would you like to add more collaborators to the project? I'd be happy to help in both those aspects.

Cheers!

Initial pass at fixing the tests

After we ported the tests, there will probably be many failures, but that's ok as this is test-driven development.

Probably we can fix most tests by porting the code, then are left with some tests either failing because of small differences in test methodology (React Helmet uses some React test tools that don't translate well (or at least I dont know how) to Preact). This issue should fix most tests but it's ok if a bunch are left failing.

We will fix those last tests one by one or maybe even get rid of them if we think it's safe.

Let's get back in synch with v5!

This branch is one major version behind React Helmet.

Let's get it back in sync!

Any help is welcome! I have created a bunch of issues to try to break down the problem in reasonable chunks and added them all to this milestone:
https://github.com/Download/preact-helmet/milestone/1

We can use this issue for general progress tracking, discussions etc.

If you want to help:

  • Fork this repo
  • Create a new branch (make sure to base it on branch v5, not master)
  • Make your changes (do not change version info, we do that per release)
  • Commit and push your changes to your fork
  • Create a pull request
  • We will review your PR and if ok, merge it

Once v5 is ready, we merge it back into master and release it.

v4.0 Final

Inviting all active users of preact-helmet to give some feedback.

Is it ready for 4.0.0?

Please add a remark below.

Note: React-Helmet is at v5 and there is development going on to implement that. But it would be nice to release the current version as 4.0.0 before we move on imho.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.