chore: March Dependency Updates

[eric-forte-elastic]

Summary

Dependency updates to address requested updates from the detection-rules-explorer dependency PRs, applied without introducing errors.

axios: devDependencies uses an exact pin to 1.13.4 instead of ^1.14.0, so installs stay on the 1.13.x line and do not float to 1.14.x.

Category	Package	Updated Version / Change
dependencies	@emotion/cache	^11.14.0
dependencies	@emotion/react	^11.14.0
dependencies	core-js	^3.48.0
dependencies	react	^18.3.1
dependencies	react-dom	^18.3.1
dependencies	regenerator-runtime	^0.14.1
dependencies	tar	^7.5.13
devDependencies	@emotion/babel-plugin	^11.13.5
devDependencies	@types/node	^16.18.126
devDependencies	@typescript-eslint/eslint-plugin	^7.18.0
devDependencies	axios	1.13.4 (exact pin; not ^1.14.0)
devDependencies	copy-webpack-plugin	^13.0.1
devDependencies	eslint	^8.57.1
devDependencies	eslint-config / prettier plugins	bumped (version not specified)
devDependencies	moment	^2.30.1
devDependencies	prettier	^2.8.8
devDependencies	sass	^1.97.3
devDependencies	serve	^14.2.6
devDependencies	typescript	^5.9.3

Testing

Screenshots

Local Test Steps

Use either the commands from the README if you wish to use your local node installation, or use the following Docker container to test.

Docker Instructions

1. Clone detection-rules-explorer and cd into the newly cloned directory

2. Create a Dockerfile with the following contents

   Dockerfile

   FROM node:20.19.3-alpine
   RUN mkdir -p /opt/app
   WORKDIR /opt/app
   COPY package.json package-lock.json /opt/app/
   RUN npm ci
   COPY . .
   RUN npm run build && npm run export
   CMD [ "npm", "start"]

3. Run docker build -t rules_explorer_test . to build the container

4. Run docker run rules_explorer_test to start the container

5. Navigate to 10.10.0.2:3000 to view the explorer (note this is http NOT https)

   • Note this IP address may be different for you depending on your Docker setup or if you are running additional containers.

   • You can use the docker container list command to find your running container

     Example

     ❯ docker container list
     CONTAINER ID   IMAGE                                         COMMAND                  CREATED          STATUS          PORTS                                       NAMES
     c0a434dbfde6   rules_explorer_test                           "docker-entrypoint.s…"   37 seconds ago   Up 37 seconds   443/tcp                                     determined_lehmann
     
     

   • Now you can grab the CONTAINER ID and use it to get the IP address via the following docker inspect <container_id> | grep IPAddress

     Example

     detection-rules-explorer on  remove_ml_packages [!?] via  v20.9.0 on  eric.forte 
     ❯ docker inspect 1ae633496a1b | grep IPAddress
                 "SecondaryIPAddresses": null,
                 "IPAddress": "10.10.0.2",
                         "IPAddress": "10.10.0.2",

6. Check to make sure the website renders as intended.