Ku habee isku xirka API-ga dhinaca Node ee webpack.config.mjs iyadoo la isticmaalayo qaabka array proxy ee hadda:

import { HttpsProxyAgent } from 'https-proxy-agent';

export default {
  devServer: {
    proxy: [{
      context: ['/api'],
      target: 'https://service.example',
      changeOrigin: true,
      agent: new HttpsProxyAgent('http://proxy.example:8080'),
      pathRewrite: { '^/api': '' },
    }],
  },
};

Waddadu waa:

browser → webpack dev server → corporate proxy → HTTPS API

target wali waa HTTPS API-dii dhabta ahayd. Wakiilka, oo loo malaynayo in uu horey ugu jiro mashruuca, wuxuu waddada kala xaajoodaa iyada oo loo marayo dhexdhexaadiyaha HTTP.

context waxay doorataa waddooyinka codsiga ee browser-ku arko; pathRewrite waxay meesha ka saartaa prefix-ka horumarinta. Midkoodna ma sheego proxy shirkadeed. Hayso khariidadahaas waddada API-gu filayo.

Isticmaal socodka iyo maaraynta jawaabta caadiga ah ee middleware-ka si diidmada API-ga iyo guuldarada gaadiidka ay u kala garan karaan. Relay labaad oo gacan lagu qoray oo had iyo jeer soo celiya 200 ayaa qarin lahaa natiijadaas.

Dejinta proxy-ga browser-ka iyo proxy-ga soo dejinta xirmooyinka npm waxay habayaa isticmaalayaal kale. Dejintan waxay ka tirsan tahay habka webpack ee sameeya wicitaanka API-ga dibadda.

Maqaallo la xiriira