Adalo CLI *Issue*

Get Help
1

Hi everyone! :waving_hand:

I’m facing a persistent issue with Adalo’s CLI while running npx adalo dev for a custom component, and I’d really appreciate any insights or advice from the community. Here are the details:

The Problem

  • Error message:
Module parse failed: Unexpected token (51:11)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file.
  • This happens when the CLI tries to process JSX in src/TransactionReport.jsx.

What I’ve Done

I’ve meticulously verified all the following steps:

  1. Configuration Files:
  • My webpack.config.js has babel-loader configured to handle .js and .jsx files, linked correctly via package.json.
  • adalo.json, manifest.json, and src/index.js paths are all consistent.
  1. Babel Setup:
  • .babelrc includes @babel/preset-env and @babel/preset-react.
  1. Dependencies:
  • babel-loader, @babel/core, @babel/preset-env, and @babel/preset-react are properly installed.
  1. React Versions:
  • Using react@17.0.0 and react-dom@17.0.0, both valid versions.

Despite everything being in place, the Adalo CLI seems to ignore the configured Webpack/Babel loaders.

Specs & Notes

  • Operating System: macOS
  • Node.js Version:
  • This error persists with this custom component, even though simpler test setups compile just fine.

Request from the Community

If anyone has faced a similar issue or knows a workaround, I’d be incredibly grateful for your suggestions! :folded_hands:

Is it possible that there’s a quirk or limitation with how Adalo’s CLI interacts with Webpack and Babel on macOS?

Any advice is welcome. Thanks in advance! :blush:

2

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.