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

@conga/framework-webpack

v2.1.1

Published

Adds webpack to a conga.js project

Downloads

8

Readme

conga-webpack Build Status

Overview

This is a bundle for the CongaJS framework which adds webpack support to a project.

The purpose of this bundle is to provide an easy to use bridge between conga.js and webpack in order to compile your js/css/.etc assets and load them in your templates.

Additionally, the bundle will serve assets through webpack-dev-middleware and webpack-hot-middleware to provide quick compilation and page reloads while building your frontend applications.

Finally, this bundle also hooks in to the conga.js production build process to compile your final production assets prior to deployment with automatic cache bursted paths.

Installation

Add the bundle to your project

$ npm install --save @conga/framework-webpack

Enable the bundle in app/config/bundles.yml:

bundles:

    all:

        - "@conga/framework-webpack"

Add configuration to app/config/config.yml:

webpack:

    # turn development mode on/off (dev middleware / hot reloading)
    development: true

    # the public path to publish files in dev mode under
    public.path: /build/

    # the path to the config file
    config.paths:
        - "frontend-bundle:resources/public/webpack.common.js"

Add a webpack config file

The following is the minimum required configuration.

// frontend-bundle/lib/resources/public/webpack.common.js

const path = require('path');

module.exports = {

    context: path.resolve(__dirname),

    entry: {
        app1: './app1.js',
        app2: './app2.js'
    },
    output: {
        filename: '[name].[hash].bundle.js'
    }

};

A "context" is required which points to the directory in which the config file is located.

The "entry" needs to be an object with a unique key which will be used to reference the compiled file from a template.

It is recommended that the output file names contain a [hash] to enable "cache busting" in production environments.

Load the assets in a template

// frontend-bundle/lib/resources/views/default/index.html.twig

<html>
<head>
    <title>Webpack Test</title>
    <link rel="stylesheet" href="{{ webpack_asset('app1', 'css') }}" />
</head>
<body>
    <h1>Webpack Test</h1>
    <script src="{{ webpack_asset('app1', 'js') }}"></script>
</body>
</html>

Use the webpack_asset() helper to point to the final compiled file in the build directory using an "entry" key as defined in your webpack config file.