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

react-native-web-image-loader

v0.1.1

Published

react-native-web-image-loader

Downloads

36,879

Readme

React Native Web Image Loader

Using this loader will automatically bundle scaled counterparts too. Since Image component of react-native-web accepts objects as value of its source property it is possible to display scaled images based on device pixel ratio.

This loader will inject an AdaptiveImage class into your bundle. Everywhere you require an image an instance of AdaptiveImage will be returned.

This is my first node.js package so every recommendation is welcome. :smile:

Installation

Install it via npm:

$ npm install --save-dev react-native-web-image-loader

Usage

In your webpack config use it as a loader for images:

{
  ...,
  module: {
    rules: [
      {
        test: /\.(png|jpe?g|gif)$/,
        options: {
          name: 'static/media/[name].[hash:8].[ext]',
          // publicPath: 'https://cdn.example.com/', // uncomment to override webpack public path
          // esModule: true
          scalings: { '@2x': 2, '@3x': 3 },
        },
        loader: 'react-native-web-image-loader',
      },
    ]
  }
}

You're done.

Configuration

The following configuration variables can be defined in the options object:

  • name The name template of the output files. (default: [hash].[ext]) You can use the following placeholders:
    • [ext] the extension of the resource
    • [name] the basename of the resource
    • [path] the path of the resource relative to the context query parameter or option.
    • [hash] the hash of the content, hex-encoded md5 by default
  • scalings is an object where the keys are the possible filename suffixes and values are the amount of scale. (Default is {"@2x": 2, "@3x": 3}, which means filenames ending with "@2x" will be used on devices where the pixel-ratio is 2)
  • imageClassPath the path of image class that should be used instead of AdaptiveImage. This gives you the possibility to use your own image class representation.
  • publicPath Specifies a custom public path for the target file(s). Default: __webpack_public_path__ + outputPath. You dynamically set custom public path by passing a function.
  • outputPath Specify a filesystem path where the target file(s) will be placed.
  • esModule By default, react-native-web-image-loader generates JS modules that use the ES modules syntax. You can disable it by setting its value to false.

Examples

We have the following files:

|--assets/
   |-- pic1.png
   |-- [email protected]
   |-- pic1-3x.png
|--index.js

webpack.config.js

module.exports = {
    ...,
    module: {
      rules: [
        {
          test: /\.(png|jpe?g|gif)$/,
          options: {
            name: 'static/media/[name].[hash:8].[ext]',
            scalings: { '@2x': 2, '@3x': 3 },
          },
          loader: 'react-native-web-image-loader',
        },
      ]
    }
}

index.js

import React from 'react'
import { Image } from 'react-native-web'

export default class Picture extends React.Component {
  render() {
    return <Image source={require('./assets/pic1.png')} />
  }
}

Value of source property looks like this:

AdaptiveImage {
    "data": {
        "uri": "static/media/pic1.abcd1234.png",
        "uri@2x": "static/media/[email protected]",
        "uri@3x": "static/media/pic1-3x.efgh5678.png",
        "width": 128,
        "height": 64
    },
    get uri(),       // returns uri based on pixel ratio
    get width(),     // returns this.data.width
    get height(),    // returns this.data.height
}

So when Image component resolves source it will treat it as a normal object. But value of uri is dynamically returned according to current device pixel ratio.