Hello! It seems like the tool you’re using to resolve modules can’t find the babel-loader/@babel file that you’re trying to import in app/pages/index.vue.
Do you mind sharing the name of the project so someone here can take a look?
Hey @ThatNerdyPikachu we might have a line on this and it seems like it’s a bug around vue, yarn, and babel-loader. I’m assuming that you’re using yarn based on the contents of your project, so correct me if I’m wrong about that. If you are you might take a look at https://github.com/vuejs/vue-cli/issues/2599, which touches on a few common aspects to what you’re seeing here.
Running the suggested solution (yarn add -D babel-loader) in the console for a project remixed from your got rid of the nuxt build error. Some other things popped up and I’m not familiar enough with Nuxt, Vue, and Webpack all together to know off the top of my head where they’re coming from (although I do think you’re missing a } after https://glitch.com/edit/#!/pikas-pogo-stick?path=pages/index.vue:28:0 in your current vue file)
I’m running into the same issue with an NPM powered Nuxt project. This didn’t occur with earlier versions of Nuxt but can’t seem to get the latest to cooperate on Glitch.
Yeah, it’s running pnpm and it looks like that same issue. You can run enable-npm from the console to switch over to using npm. That will likely resolve this issue, however, then node modules begin to count towards your project space which may become a problem for you. But let us know how you get on.