Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Dev server throws error and is unable to start

See original GitHub issue

This also affects building the project too.

Version

3.0.0-beta.1

Reproduction link

reproducible through cli

Steps to reproduce

Vue CLI v3.0.0-beta.1
? Please pick a preset: Manually select features
? Check the features needed for your project: TS, Router, Vuex, Unit, E2E
? Use class-style component syntax? Yes
? Use Babel alongside TypeScript for auto-detected polyfills? Yes
? Pick a unit testing solution: Jest
? Pick a E2E testing solution: Cypress
? Where do you prefer placing config for Babel, PostCSS, ESLint, etc.? In dedicated config files
? Save this as a preset for future projects? No

What is expected?

Dev server to start

What is actually happening?

[...]/node_modules/regex-not/index.js:62
    throw new Error('potentially unsafe regular expression: '   res);
    ^

Error: potentially unsafe regular expression: ^(?:(?!(?:[\[!* ?$^"'.\\/] )).) 
    at Function.toRegex.create (/Users/rh/Sites/vuecli3test/node_modules/regex-not/index.js:62:11)
    at createTextRegex (/Users/rh/Sites/vuecli3test/node_modules/nanomatch/lib/parsers.js:378:22)
    at Object.<anonymous> (/Users/rh/Sites/vuecli3test/node_modules/nanomatch/lib/parsers.js:14:11)
    at Module._compile (module.js:660:30)
    at Object.Module._extensions..js (module.js:671:10)
    at Module.load (module.js:573:32)
    at tryModuleLoad (module.js:513:12)
    at Function.Module._load (module.js:505:3)
    at Module.require (module.js:604:17)
    at require (internal/module.js:11:18)
error Command failed with exit code 1.

Issue Analytics

State:
Created 6 years ago
Comments:6

Top GitHub Comments

1reaction

roberthamelcommented, Feb 20, 2018

Thank you again for the help. Much appreciated.

0reactions

jonschlinkertcommented, Feb 20, 2018

The one step I missed was deleting the yarn.lock file before running yarn again. That fixed the issue.

good suggestion. I’ll add a suggestion to delete that and package-lock.json to the fix.

Top Results From Across the Web

Unable to start the dev server. Error: The dev server is not ...

The error about being unable to start the dev server is likely because it is timing out waiting for the prompt.

"npm start" error with webpack-dev-server - Stack Overflow

I then tried using npm install webpack-dev-server and got an error. It kept saying things like xyz/abc/node_modules/xyz/node_modules/abc/.bin/file exists. Move ...

Error: Unable to Start Debugging on the Web Server

When you try to debug an ASP.NET application running on a Web server, you may get this error message: Unable to start debugging...

webpack-dev-server - npm

Getting Started. First things first, install the module: npm install webpack-dev-server --save-dev. or.

Troubleshooting - Vite

Switch to another package manager (e.g. pnpm , yarn ); Remove & from the path to your project. Dev Server #. Requests are...