chore(webpack): set up basic example project to test plugin against

[BethanyBerkowitz]

Status

READY

Description

In working on #1013, I found I needed a basic project to test sourcemap upload and deploy notifications. I decided to set up the project first so I could see the behavior on the existing package before making changes.

Steps to Test or Reproduce

> cd packages/webpack/example
> npm i
> npm run build

You should see

Uploaded main.js.map to Honeybadger API
Successfully sent deploy notification to Honeybadger API.

[subzero10]

Nothing blocking, but I left some comments.

[subzero10]

Since HONEYBADGER_API_KEY is required to be passed as an env variable for this example app, you could read it from there using the EnvironmentPlugin.

[BethanyBerkowitz]

I do think that would work for our testing purposes, but I don't think it's the example we necessarily want to set for our users. From those docs it looks like this will put the API key into the bundled code as a string, which would expose it publicly.

I didn't intend this little example to be about the main HB functionality... really just about the sourcemap and deploy upload, but I still wouldn't want to publish something that if copy/pasted could cause user API keys to be public.

[subzero10]

👍 Gotcha.

Btw, API keys on the client side are exposed publicly anyway in some way or another. Best we can do is hide them under minified/uglified code, but they are exposed nevertheless.