feat: Implement bot detection categories

[blaine-arcjet]

This is mostly just codegen and a little bit of type updates.

I'm planning to add a new example for categories, with the additional demonstration of filtering items from a category.

[trunk-io]

😎 Merged successfully - details.

[socket-security]

New dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@types/react@18.3.5	None	0	438 kB	types
npm/eslint-config-next@14.2.9	unsafe Transitive: filesystem	+1	83.5 kB	vercel-release-bot
npm/eslint@8.57.0	environment, filesystem	+3	3.16 MB	eslintbot
npm/next@14.2.9	environment, filesystem, network, shell, unsafe	+10	1.19 GB	vercel-release-bot
npm/nextjs-14-bot-categories@0.1.0	None	0	0 B
npm/tailwindcss@3.4.10	environment, filesystem	0	5.71 MB	adamwathan

View full report↗︎

[blaine-arcjet]

@davidmytton I've added an example for the bot categories. Please try it out! I also included usage and details about your filtering request in the example.

[blaine-arcjet]

Note to self: add this to dependabot and CI

[davidmytton]

I tested the nextjs-14-bot-categories example app, but I don't get the category in the headers or when the decision is logged:

< HTTP/1.1 429 Too Many Requests
< vary: RSC, Next-Router-State-Tree, Next-Router-Prefetch
< content-type: application/json
< x-arcjet-bot-allowed:
< x-arcjet-bot-denied: CURL
< Date: Sun, 15 Sep 2024 16:45:40 GMT
< Connection: keep-alive
< Keep-Alive: timeout=5
< Transfer-Encoding: chunked
<
* Connection #0 to host localhost left intact
{"error":"You are a Bot!"}%

ArcjetDenyDecision {
  id: 'req_01j7v96s53fc7btc6naz433qce',
  results: [
    ArcjetRuleResult {
      ruleId: '',
      ttl: 60,
      state: 'RUN',
      conclusion: 'DENY',
      reason: [ArcjetBotReason]
    }
  ],
  ttl: 60,
  ip: ArcjetIpDetails {
    latitude: undefined,
    longitude: undefined,
    accuracyRadius: undefined,
    timezone: undefined,
    postalCode: undefined,
    city: undefined,
    region: undefined,
    country: undefined,
    countryName: undefined,
    continent: undefined,
    continentName: undefined,
    asn: undefined,
    asnName: undefined,
    asnDomain: undefined,
    asnType: undefined,
    asnCountry: undefined,
    service: undefined
  },
  conclusion: 'DENY',
  reason: ArcjetBotReason { type: 'BOT', allowed: [], denied: [ 'CURL' ] }

[blaine-arcjet]

@davidmytton did you test against the decide service running locally? Since the example is using an allow list, if you tested against the test or prod server, you'd get CURL denied (as categories aren't supported until it is deployed). I also ran into this when testing so the result looks familiar.

[davidmytton]

Yeh I was testing against prod. Just tested against the local branch and all looks good!