Variables and functions declared in a javaScript file are only valid in that file; they can have the same value in different files Variables and functions with the same names will not affect each other.
You can obtain the global application column through the global function getApp()
. If you need global data, you can set it in app()
, such as:
//app.jsapp({ globalData:1})
// a.js// The localValue can only be used in file a.js.var localValue = 'a'// Get the app instance.var app = getApp()// Get the global data and change it.app.globalData++
// b.js// You can redefine localValue in file b.js, without interference with the localValue in a.js. var localValue = 'b'// If a.js it run before b.js, now the globalData shoule be 2.console.log(getApp().globalData)
You can extract some common code into a separate js file as a module. Modularization can only expose interfaces to the outside world through module.exports
or exports.
It should be noted that:
wxports
is a reference to module.exports
, so you can change it at will in the modularization## Pointing to #exports will cause unknown errors. Therefore, it is recommended that developers use
module.exports to expose module interfaces, unless you already clearly know the relationship between the two.
node_modules. When developers need to use
node_modules, it is recommended to copy the relevant code to the mini program.
//commont.jsfunction sayHello(name){ console.log('------ hello ' + name +'====='); } module.exports.sayHello = sayHello;
//index.jsvar common = require('../commont/commont.js'); Page({ //加载视图的时候 onLoad:function (){ //调用 common.sayHello('dqk'); })
The above is the detailed content of File scope analysis in WeChat applet. For more information, please follow other related articles on the PHP Chinese website!