@sect/webpack-sweet-entry

Multiple entry points with glob pattern / Ignore files and directories with leading underscore _ / Preserve directory structure

Install

npm install --save-dev @sect/webpack-sweet-entry

Features

• Multiple entry points with glob pattern.
• Ignore files and directories with leading underscore _.
• Preserve directory structure in dist directory.
• Dual Package Support (CommonJS and ES Modules).

Usage Example

CommonJS

constwebpack=require('webpack');constpath=require('path');const{ WebpackSweetEntry }=require('@sect/webpack-sweet-entry');constsourcePath=path.join(__dirname,'src');constbuildPath=path.join(__dirname,'dist');module.exports=[{entry: WebpackSweetEntry(path.resolve(sourcePath,'assets/js/**/*.js*'),'js','js'),output: {path: path.resolve(buildPath,'assets/js'),filename: '[name].js',},module: {
...
}},{entry: WebpackSweetEntry(path.resolve(sourcePath,'assets/css/**/*.css'),'css','css'),output: {path: path.resolve(buildPath,'assets/css'),filename: '[name].css',},module: {
...
}}];

ES Modules

importwebpackfrom'webpack';importpathfrom'path';import{fileURLToPath}from'url';import{dirname}from'path';import{WebpackSweetEntry}from'@sect/webpack-sweet-entry';const__filename=fileURLToPath(import.meta.url);const__dirname=dirname(__filename);constsourcePath=path.join(__dirname,'src');constbuildPath=path.join(__dirname,'dist');exportdefault[{entry: WebpackSweetEntry(path.resolve(sourcePath,'assets/js/**/*.js*'),'js','js'),output: {path: path.resolve(buildPath,'assets/js'),filename: '[name].js',},module: {
...
}},{entry: WebpackSweetEntry(path.resolve(sourcePath,'assets/css/**/*.css'),'css','css'),output: {path: path.resolve(buildPath,'assets/css'),filename: '[name].css',},module: {
...
}}];

TypeScript

importwebpackfrom'webpack';importpathfrom'path';import{fileURLToPath}from'url';import{dirname}from'path';import{WebpackSweetEntry}from'@sect/webpack-sweet-entry';const__filename=fileURLToPath(import.meta.url);const__dirname=dirname(__filename);constsourcePath=path.join(__dirname,'src');constbuildPath=path.join(__dirname,'dist');constconfig: webpack.Configuration[]=[{entry: WebpackSweetEntry(path.resolve(sourcePath,'assets/js/**/*.js*'),'js','js'),output: {path: path.resolve(buildPath,'assets/js'),filename: '[name].js',},module: {
...
}},{entry: WebpackSweetEntry(path.resolve(sourcePath,'assets/css/**/*.css'),'css','css'),output: {path: path.resolve(buildPath,'assets/css'),filename: '[name].css',},module: {
...
}}];exportdefaultconfig;

Multiple(Mixed) extensions

constconfig: webpack.Configuration[]=[{entry: WebpackSweetEntry(path.resolve(sourcePath,'assets/scripts/**/*.*s*'),['ts','js'],'scripts'),output: {
...
},module: {
...
}},
...
];

API

WebpackSweetEntry(path,ext,parentdir);

arg	type	Description	Example
path	string | string[]	File path glob(s)	path.resolve(sourcePath, 'assets/js/**/*.js*') or [path.resolve(sourcePath, 'assets/js/**/*.js*'), '!**/a.js']
ext	string | string[]	File extension	js or ['ts', 'js']
parentdir	string	Parent Dirctory Name for files (The directory name where the tree starts)	js

Returns object like the following.

{a: '/path/to/your/src/assets/js/a.js',b: '/path/to/your/src/assets/js/b.js','dir/e': '/path/to/your/src/assets/js/dir/e.js'}{a: '/path/to/your/src/assets/css/a.css',b: '/path/to/your/src/assets/css/b.css','dir/e': '/path/to/your/src/assets/css/dir/e.css'}

Build Result

.
├── dist
│ └── assets
│ ├── css
│ │ ├── a.css
│ │ ├── b.css
│ │ └── dir
│ │ └── e.css
│ └── js
│ ├── a.js
│ ├── b.js
│ └── dir
│ └── e.js
├── src
│ └── assets
│ ├── css
│ │ ├── a.css
│ │ ├── b.css
│ │ ├── _c.css
│ │ ├── _d.css
│ │ └── dir
│ │ ├── e.css
│ │ └── _f.css
│ └── js
│ ├── a.js
│ ├── b.js
│ ├── _c.js
│ ├── _d.js
│ ├── _modules
│ │ ├── a.js
│ │ └── b.js
│ └── dir
│ ├── e.js
│ └── _f.js
├── package-lock.json
├── package.json
└── webpack.config.js

Migrate from v1

$ npm uninstall webpack-sweet-entry
$ npm install --save-dev @sect/webpack-sweet-entry

- const WebpackSweetEntry = require('webpack-sweet-entry');+ const { WebpackSweetEntry } = require('@sect/webpack-sweet-entry');

Development

Making Changes

When you make a change that should be included in the next release:

1. Create a feature branch
2. Make your changes
3. Add a changeset: npm run changeset
   • Select the type of change (patch/minor/major)
   • Provide a description of the change
4. Commit the changeset file along with your changes
5. Create a pull request

Release Process

This project uses changesets for version management and releases.

Automated Release Workflow:

1. When a PR with changesets is merged to master, a "Version Packages" PR is automatically created
2. The Version Packages PR includes:
   • Updated version numbers in package.json
   • Updated CHANGELOG.md
   • Removed changeset files
3. When the Version Packages PR is merged:
   • The package is automatically built
   • Published to npm with provenance
   • A GitHub release is created

Manual Testing:

# Create a test changeset
npm run changeset
# Preview version bump (without publishing)
npm run version-packages
# Build and test before release
npm run build
npm test
npm run lint

Changelog

See CHANGELOG file.

✌️

_{^{A little project by @sectsect}}