Support npm specifiers

[WilliamBergamin]

Type of change (place an x in the [ ] that applies)

• New sample
• New feature
• Bug fix
• Documentation

Summary

This PR aims to update the version of the deno-slack-hooks package and enable the project to use npm specifiers to import packages

This also resolves #32

Testing

1. Pull this branch
2. Run slack deploy
3. The project should bundle and deploy as expected

Requirements

• I’ve checked my submission against the Samples Checklist to ensure it complies with all standards
• I have ensured the changes I am contributing align with existing patterns and have tested and linted my code
• I've read and agree to the Code of Conduct

[filmaj]

Should this be created as a pre-release branch for the upcoming release? Since it includes a freshly-cut SDK version bump, and the automated tests will rely on the existence of a pre-release branch?

[WilliamBergamin]

this PR or the pre-release PR will update the package, but we may require a follow up PR to update the npm specifiers

[filmaj]

Should probably use a versioned types package and also move it into a deps.ts if it exists?

This PR will also conflict with #34 FYI.

[filmaj]

I'd version this, the current version is 2.9.0. I am planning on releasing a 3.0 version soon-ish which will include breaking changes.

[filmaj]

LGTM but def should be tested with an actual slack deploy / at least a deno-hooks build hook invocation to see if esbuild can handle it or not.

Would be nice to add that to samples' CI, too: can the project be built using the deno build hook?

[WilliamBergamin]

🟢 tested with slack deploy everything works as expected
🟢 tested with deno run ... https://deno.land/x/[email protected]/build.ts everything builds as expected