Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

De-couple bundling from Punchcard #100

Open
sam-goodwin opened this issue Jan 19, 2020 · 0 comments
Open

De-couple bundling from Punchcard #100

sam-goodwin opened this issue Jan 19, 2020 · 0 comments
Labels
runtime Runtime code such as Lambda, EC2, ECS tree-shaking

Comments

@sam-goodwin
Copy link
Owner

sam-goodwin commented Jan 19, 2020

As of #53, Punchcard's runtime dependencies interact with webpack directly to create an efficient bundle for AWS lambda. This coupling pollutes the runtime dependencies and is way too opinionated - developers should be able to use any tool to create their bundle.

We should move the webpack packaging out of Punchcard and instead have developers set up their repo to generate and put a bundle in a known location. I.e. use webpack.config.js and webpack as a devDependency.

@sam-goodwin sam-goodwin added runtime Runtime code such as Lambda, EC2, ECS tree-shaking labels Jan 19, 2020
@sam-goodwin sam-goodwin changed the title De-couple application packaging from Punchcard De-couple bundling from Punchcard Jan 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
runtime Runtime code such as Lambda, EC2, ECS tree-shaking
Projects
None yet
Development

No branches or pull requests

1 participant