GeekyAnts/vue-native-core

npm run web fails

Open

#268 opened on Jul 21, 2019

View on GitHub
 (27 comments) (16 reactions) (0 assignees)JavaScript (8,333 stars) (324 forks)batch import
bughelp wanted

Description

I'm trying to run my app using the web variant. I'm getting this error when the app spins up. Ive tried to look through the expo-cli package to see if I could find anything and came up empty. I'm guessing that i'm missing a config somewhere.

Failed to compile.
C:/Users/smplman/AppData/Roaming/npm/node_modules/expo-cli/node_modules/react-dev-utils/webpackHotDevClient.js
Error: Failed to load config "universe/node" to extend from.
Referenced from: BaseConfig
    at _normalizeObjectConfigDataBody.next (<anonymous>)
    at _normalizeObjectConfigData.next (<anonymous>)

Here is how I setup my app

vue-native init test-app
cd test-app
npm run web

Contributor guide

Tech stack
vuejavascriptnodejs
Domain
frontendbuild system
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Vue Native basicswebpack configuration knowledgeunderstanding of ESLint config extensions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
The error is caused by a missing ESLint config 'universe/node' that is referenced in the webpack configuration. Investigate the source of the 'BaseConfig' in the webpack setup (likely in react dev utils or expo cli's webpack config). Check the vue native init template for how it sets up ESLint config. Look at comments in the issue for any workarounds or patches. Consider updating the template to include the required dependency or adjust the webpack config to not rely on that external config.