New Research: Supply Chain Attack on Axios Pulls Malicious Dependency from npm.Details →
Socket
Book a DemoSign in
Socket

proxy-linked-module-request

Package Overview
Dependencies
Maintainers
1
Versions
1
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

proxy-linked-module-request

proxy webpack linked module inner request to origin node_modules

latest
npmnpm
Version
1.0.0
Version published
Weekly downloads
0
Maintainers
1
Weekly downloads
 
Created
Source

使用 webpack 编译

package1 本地调试 package2 //package1 import 'package2'

yarn link package2
// package1:
// index.ts

import react from "react" // 从 package1 node_modules 获取
import { fun } from "package2" //linked package2

// package2:
// index.ts

import react from "react" // 从 package2 node_modules 获取

export { fun }

// package1 有两个版本的 react ,导致运行失败

如果 package1 在本地 link 了 package2 , 因为 link 的 package 不会对 package2 内的 node_modules link. 所以 如果 package2 import 了 node_modules 还是 从 package2 的 node_modules 获取, 不是从 package1 的 node_modules 获取,这会导致 : 对于(react ,react-router ,apollo/client ) 这种必须只能从一个 node_modules 获取 的 module 产生两个版本的代码 (从 package1 import 的 和 从 package2 import 的 ) 所以必须 都改成 从 package1 node_modules 获取 资源

使用

const {ProxyLinkedModuleRequest} = require("proxy-linked-module-request")

const webpackConfig = {
  plugins: [
    // linked 的 package 的完整路径 : /dir/xx/package
    new ProxyLinkedModuleRequest({linkedPackagePath}),
  ],
}

Keywords

webpack

FAQs

Package last updated on 16 Jun 2022

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts