Skip to main content
100%

Gist bae3b305134e90c96401e1f54a8c23e3

✓ Published0🌍 Public
Aandresmijares
Last edited Mar 11, 2019
Created on Mar 11, 2019

This example shows a serverless webpack configuration for deploying a Node.js application. It demonstrates how to bundle JavaScript code with the Serverless Webpack plugin, targeting AWS Lambda’s Node runtime. The configuration uses `serverless-webpack` to generate entry points, sets the build mode based on local development, and applies `webpack-node-externals` to exclude Node modules. It also ignores the `/opt` directory and outputs CommonJS2 bundles to the `.webpack` folder, with source maps for debugging.

AI-generated description

Similar vizzes

Loading thumbnail…

serverless webpack sample

This example demonstrates a serverless AWS Lambda function, defined in `serverless.yml`, that uses the `serverless-webpack` plugin to bundle JavaScript code with webpack. The configuration specifies a Node.js 8.10 runtime and includes a single function, `handler.hello`, which is the entry point for the Lambda. The setup also customizes the packager to rebuild the `grpc` native module for a Linux target with glibc, ensuring compatibility in the AWS environment. The visible code focuses on the deployment and build configuration, not on data visualization or rendering logic.

Aandresmijares
86% match
Loading thumbnail…

webpack configuration for webpack-es6-boilerplate

This example shows a minimal webpack configuration for the webpack-es6-boilerplate, defining how JavaScript source files are bundled. It sets the entry point to `babel-polyfill` and `./app/index.js`, outputs a single `bundle.js` to a `build` directory, and uses `babel-loader` to transpile `.js` files while excluding `node_modules`. The configuration also includes a development server on port 3000 serving from `./build` with inline mode enabled. The code directly references the webpack API, including `module.exports`, the `entry`, `output`, `module.loaders`, and `devServer` properties.

115Dkatz
69% match
Loading thumbnail…

Gist 7880143

This example demonstrates a minimal client-side build setup for a web application, showing how Less styles and browser JavaScript are compiled into static bundles. The code uses `catw` with `lessc` to transform `.less` files from `style/` into `static/bundle.css`, and `browserify` to bundle browser code from `browser/` into `static/bundle.js`. A watch mode via `watchify` and `catw` enables live recompilation during development, while a production build generates the final static assets. The example also illustrates npm script orchestration for both watch and build workflows.

Aalessioalex
65% match
Loading thumbnail…

bundle/index.html for webpack-es6-boilerplate

This example shows a minimal webpack setup for an ES6 project, producing a single-page HTML document that loads a compiled JavaScript bundle. The page contains no visible content or user interface, only an empty body with a script tag referencing `bundle.js`. The code demonstrates the entry-point plumbing of a webpack-built application, where the frontend relies entirely on the bundled output for any rendering or behavior. The files include the `index.html` shell and the webpack configuration source, indicating how a boilerplate project connects its build system to a basic HTML host page.

115Dkatz
64% match
Loading thumbnail…

Gist 11442448

This example shows a Gruntfile configuration that automates JavaScript build tasks using webpack, JSHint, and Mocha. It defines a webpack task with entry point `src/entry.js`, outputting a UMD bundle named `WithGrunt` to `lib/bundle.js`, and includes module resolution for `node_modules` and `bower_components`. The configuration also sets up JSHint linting for source and test files, a Mocha test runner with a spec reporter, and a watch task for continuous linting and testing. The default task chains these steps together, demonstrating a complete build pipeline for a modular JavaScript project.

Aakollegger
64% match
Loading thumbnail…

webpack2-config

This example shows a webpack 2 configuration file that sets up separate entry points for app and admin bundles, with output paths and public paths defined for the dist folder. The configuration uses `CommonsChunkPlugin` to extract shared code into a commons bundle, and `ExtractTextPlugin` to handle SCSS compilation into separate CSS files. Module rules apply `url-loader` for images under 10k, `babel-loader` with the `babel-preset-es2015` preset for JavaScript, and `sass-loader` chained through the CSS extraction plugin. The source is a JavaScript module exporting the config object.

VVeronicaM
62% match
Loading thumbnail…

basic webpack config file for react including babelrc

This example shows a minimal webpack configuration for a React application, including a separate .babelrc file. It defines the entry point, output bundle location, and module rules for processing JavaScript files. The configuration uses babel-loader to transform JSX and ES2015 syntax, with presets for React and es2015 modules disabled, while the webpack config sets up context, resolve extensions, and output statistics.

Aakmalmuqeeth
61% match
Loading thumbnail…

Webpack Simple Hot Reloading

This example demonstrates a development setup for a Webpack project with hot module replacement (HMR), where the webpack-dev-server serves a bundle.js file to an index.html page on localhost:9000. The configuration enables live reloading during development by using the `--hot` and `--inline` flags, along with the `webpack.NamedModulesPlugin` for readable module names and `webpack.NoEmitOnErrorsPlugin` to suppress error output. The code defines an entry point at `./index.js` and outputs a bundle with inline source maps, using `DefinePlugin` to set the development environment. The scripts support both standard and Windows command-line syntax for starting the dev server.

NN0taN3rd
60% match