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

panorama-manifest-html-webpack-plugin

v1.0.0

Published

HtmlWebpackPlugin extension that generates custom_ui_manifest.xml file for Panorama

Downloads

4

Readme

panorama-manifest-html-webpack-plugin

HtmlWebpackPlugin extension that generates custom_ui_manifest.xml file for Panorama

Install

npm i panorama-manifest-html-webpack-plugin
# or
yarn add panorama-manifest-html-webpack-plugin

Usage

// webpack.config.js

const HtmlWebpackPlugin = require('html-webpack-plugin');
const PanoramaManifestHtmlWebpackPlugin = require('panorama-manifest-html-webpack-plugin');

module.exports = {
  // ...
  plugins: [
    new HtmlWebpackPlugin({
      // ...
    }),
    new PanoramaManifestHtmlWebpackPlugin({
      // Plugin Options
    }),
  ],
};

Options

PanoramaManifestHtmlWebpackPlugin constructor has only one option - typeMappings.

This option allows to alter type property on created CustomUIElement nodes.

Should have object type with keys of asset path.

By default all CustomUIElement nodes will have HUD type.

If type is false, asset won't be added to generated html (useful for custom_loading_screen.xml)

Example

// webpack.config.js

const HtmlWebpackPlugin = require('html-webpack-plugin');
const PanoramaManifestHtmlWebpackPlugin = require('panorama-manifest-html-webpack-plugin');

module.exports = {
  entry: {
    'custom_ui_manifest.js': 'src/panorama/scripts/custom_game/custom_ui_manifest.js',
    'end-screen.xml': 'src/panorama/scripts/custom_game/end-screen.xml',
    '../layout/custom_game/custom_loading_screen.xml': 'src/panorama/custom_game/custom_loading_screen.xml',
  },
  output: {
    path: 'content/panorama/custom_game/',
    // Because we need to emit .xml and .js at the same time
    filename: '[name]',
    publicPath: 'file://{resources}/custom_game/',
  },
  module: {
    loaders: [
      // Some loader for your layout files
    ],
  },
  plugins: [
    new HtmlWebpackPlugin({
      template: 'src/panorama/layout/custom_game/custom_ui_manifest.xml',
      filename: '../layout/custom_game/custom_ui_manifest.xml',
    }),
    new PanoramaManifestHtmlWebpackPlugin({
      'end-screen.xml': 'EndScreen',
      // Remove custom_loading_screen.xml from manifest
      '../layout/custom_game/custom_loading_screen.xml': false,
    }),
  ],
};