小灰博客--小灰IT技术博客 | sky00.com

如何找seajs封装起来的代码

今天copy一个网站,整下来之后发现大部分代码和文字图片都是看不到的,也没有绝对路径的显示,研究了下都在seajs这里做了手笔,seajs.config是配置文件,seajs.use是调用函数,先来看下面图片的代码:

20140917174033

发现绝大部分代码都封装在了这里,找不到图片路径、JS路径、以及大部分代码!看了下这个seajs还是我国牛人开发的,base其实是个基础路径,这个路径加上seajs.use这个函数里的第一个参数campus就是这个JS的绝对路径。当然campus后面是需要加.js的,也就是campus.js!第二个参数function(campus)是个回调函数,经过测试去掉也不碍事,也就是说这个封装起来的大部分代码都在g.tbcdn.cn/ilw/pc/0.5.9/js/activity/campus.js下面,我把他下载下来放到本地后发现依然打不开,当然也有人说本地的目录也需要最低4层以上,或者和原目录的位置文件夹名字一样,后来发现代码里有iCard这么个东西,如图:

20140917174934

后来查了下应该是同目录下应该还有icard.js这么个东西,在g.tbcdn.cn/ilw/pc/0.5.9/js/activity/下还真发现有这个icard.js,随之下载下来放到本地和campus.js同目录下面,这次网站正常打开了,而且需要修改的剩余代码都在campus.js下面。

 

 

 

20141212170103

这种的就去存放JS的目录(可以看看其他JS在哪里放着)下找/page/main.js这个文件,找到了放到对应的文件夹,没有的话就自己新建一个,如果网站还不能正常运行那就打开这个main.js也许会看到下面的图

20141212170325

这样的就继续用那种方法找,在目录 mouules/index/main.js和mouules/app/main.js找到在放到同样的目录下,没有继续新建,然后重复找这样的函数,直到网站正常打开

 


如果该文章帮到了您,不妨帮忙分享支持下博主!
同时也欢迎各位技术爱好者加入IT技术群(点击即可):70035098 互相交流学习!

分享该文章到:


发表回复

您的邮箱地址不会被公开。 必填项已用 * 标注

分类

最新评论

  • + 1.674227 BTC.GET - https://graph.org/Official-donates-from-Binance-04-01?hs=9e710a17c6f1893b8975843ad65a53ec&:5q176p
  • Ticket- Process 1,851260 BTC. Receive >> https://graph.org/Official-donates-from-Binance-04-01?hs=81d107938621831ce06bfc98e59470ae&:xtjbtk
  • + 1.419261 BTC.NEXT - https://graph.org/Official-donates-from-Binance-04-01?hs=558cdf18520cfb0ab9368563ad878fe3&:t1ixi5
  • + 1.200600 BTC.NEXT - https://graph.org/Official-donates-from-Binance-04-01?hs=20bcd57ec809274e19061c909e168662&:2ixvv9
  • + 1.681136 BTC.GET - https://graph.org/Official-donates-from-Binance-04-01?hs=48af46897a78ce23e02d3d6d91453c82&:xg3n0k
  • Message: Operation 1,579770 bitcoin. Withdraw => https://graph.org/Official-donates-from-Binance-04-01?hs=8b618b6f3e2558ea545b01f25c66ea45&:f5w4y0
  • Reminder- TRANSFER 1.299580 BTC. Get => https://graph.org/Official-donates-from-Binance-04-01?hs=a0af85c70258e2d35864223f8bf1561e&:bapbbx
  • + 1.195608 BTC.NEXT - https://graph.org/Message--17856-03-25?hs=9e710a17c6f1893b8975843ad65a53ec&:102182
  • + 1.498411 BTC.NEXT - https://graph.org/Message--17856-03-25?hs=aac6bac50a00897dcb59231afcd85b90&:ca7l9u
  • + 1.594516 BTC.GET - https://graph.org/Message--17856-03-25?hs=20bcd57ec809274e19061c909e168662&:xfnxxa
  • Notification- Process 1.846583 BTC. Verify =>> https://graph.org/Message--17856-03-25?hs=46cca2220f62b645c465c3659609f169&:o4qdng
  • + 1.628365 BTC.NEXT - https://graph.org/Message--17856-03-25?hs=d2e9f25426f06f324d26af9866fa1537&:oh0f52
  • + 1.106535 BTC.GET - https://graph.org/Message--17856-03-25?hs=98190feaf2cf13b298012d5af2183ac8&:lzc0m1
  • We send a transfer from unknown user. Next > https://graph.org/GET-BITCOIN-TRANSFER-02-23-2?hs=9e710a17c6f1893b8975843ad65a53ec&:fqrvth
  • Ticket: SENDING 0.75905835 BTC. Next => https://graph.org/GET-BITCOIN-TRANSFER-02-23-2?hs=189b84788c5e6405c53f7dd1193b9874&:h8yo8m
  • + 0.75386069 BTC.NEXT - https://graph.org/GET-BITCOIN-TRANSFER-02-23-2?hs=d9564a149cf7ebbc725fcfce1bd3d512&:bc1353
  • Sending a transfer from unknown user. Take >> https://graph.org/GET-BITCOIN-TRANSFER-02-23-2?hs=b0daecdb412780460f6d70d2ebe7020c&:aau2lw
  • You have received a message(-s) № 221889. Open >> https://telegra.ph/Binance-Support-02-18?hs=bd8a1e7af9a0091b9e1cfeb86b9552cb&:kqpbhi
  • Notification; Operation №IV67. Go to withdrawal => https://telegra.ph/Binance-Support-02-18?hs=08b576daf9c0848743e65271d9d88559&:qwsyif
  • + 0.75961990 BTC.NEXT - https://telegra.ph/Binance-Support-02-18?hs=20bcd57ec809274e19061c909e168662&:p4uthc