Why doesn't uniapp open the browser automatically?
When developing a uniapp project, we often use command line tools to start the project. The traditional development method is that after starting the project, the tool will automatically open the default browser and display our project page there. However, some developers have found that when using the latest version of the uniapp framework, the command line tool no longer automatically opens the browser. Why is this? How to solve this problem?
Cause of the problem
First we need to understand the development model of the uniapp project. uniapp adopts a multi-terminal unified development model, and its development process includes two links: local development and compilation and release. During local development, we need to use the command line tool provided by uniapp to start the project, that is, use the npm run dev:%PLATFORM%
command. Among them, %PLATFORM%
represents the platform corresponding to the current project, such as h5, app, etc. When executing this command, we will find that the console outputs the following information:
DONE Compiled successfully in xxxms 14:38:11 App running at: - Local: http://localhost:8080/ Network: http://192.168.xxx.xxx:8080/
We can see that in the line Local
, the console outputs the access address of our local project , this address is generally http://localhost:8080/
. In the traditional development method, the console will also automatically open the browser and display our project page there.
However, in the latest version of the uniapp framework, the command line tool turns off the function of automatically opening the browser by default. This modification is based on security considerations, because the developer's project may contain some sensitive information, and if you open the browser to display the project at will, it may cause security issues.
Solution
Now that we know the cause of the problem, we can take appropriate measures to solve the problem. There are two methods.
Method 1
When executing the startup command of the command line tool, add the -o
parameter to realize the function of automatically opening the browser. The instructions are as follows:
npm run dev:%PLATFORM% -o
Among them, the -o
parameter means opening the browser.
Method 2
Modify the vue.config.js configuration file and configure the function of automatically opening the browser. The specific steps are as follows:
1. Create a new vue.config.js file in the project root directory.
2. Add the following code in the vue.config.js file:
module.exports = { devServer: { open: true } }
Among them, open:true
means that the browser will be automatically opened when starting the project.
Summary
When using uniapp to develop a project, if the command line tool does not automatically open the browser, we can take the above two methods to solve this problem. However, when modifying the default configuration of the project, you need to pay attention to controlling the developer's sensitive information from being displayed at will to avoid security issues.
The above is the detailed content of Why doesn't uniapp open the browser automatically?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



The article discusses various testing types for UniApp applications, including unit, integration, functional, UI/UX, performance, cross-platform, and security testing. It also covers ensuring cross-platform compatibility and recommends tools like Jes

The article discusses debugging tools and best practices for UniApp development, focusing on tools like HBuilderX, WeChat Developer Tools, and Chrome DevTools.

The article discusses strategies to reduce UniApp package size, focusing on code optimization, resource management, and techniques like code splitting and lazy loading.

The article discusses optimizing images in UniApp for better web performance through compression, responsive design, lazy loading, caching, and using WebP format.

Lazy loading defers non-critical resources to improve site performance, reducing load times and data usage. Key practices include prioritizing critical content and using efficient APIs.

The article discusses managing complex data structures in UniApp, focusing on patterns like Singleton, Observer, Factory, and State, and strategies for handling data state changes using Vuex and Vue 3 Composition API.

UniApp manages global configuration via manifest.json and styling through app.vue or app.scss, using uni.scss for variables and mixins. Best practices include using SCSS, modular styles, and responsive design.

The article discusses handling the back button in UniApp using the onBackPress method, detailing best practices, customization, and platform-specific behaviors.
