-
## Description
The types returned from `AxiosDataFetcher::fetch()` from `@sitecore-jss/sitecore-jss-nextjs` is incompatible with the actual type declared in `axios`. This happens after updating Axios…
thany updated
3 months ago
-
Enviroment:
server,not browser;
nodejs@12.22,
"axios": "^1.7.7",
"form-data": "^4.0.0",
code:
```js
var form = new FormData();
form.append( '/firmware.binS', , file.size );
form.append( 'my…
-
### Current Behavior
Failed to create a brand new workspace
### Expected Behavior
The CLI shall create a new workspace as expected.
### GitHub Repo
_No response_
### Steps to Reprod…
-
### What version of Bun is running?
1.1.31
### What platform is your computer?
Darwin 23.5.0 arm64 arm
### What steps can reproduce the bug?
some code in my dependencies packages look like this:
…
-
axios 1.7.2 allows SSRF via unexpected behavior where requests for path relative URLs get processed as prot…
-
### Is your feature request related to a problem? Please describe.
Hey there, it's me again 😊
I currently received 401 error requests from a library i call via axios and mentioned that my api then…
-
Im using `getUri` which performs different in most recent `axios` - would appreciate bumping version
-
import Vue from 'vue'
import App from './App.vue'
import router from './router'
import axios from "./utils/axios";
import {uuid} from "vue-uuid";
import globalMethods from "@/utils/globalMethods"…
-
## install
types無しで型提供あり。
```
docker exec -it reactad npm install axios
```
-
### Describe the bug
throw error TypeError [ERR_INVALID_URL]: Invalid URL if sockPath is used.
### To Reproduce
_No response_
### Code snippet
_No response_
### Expected behavior
_No response_
…
Jssly updated
1 month ago