No Loaders working currently

Running a fresh expo init build with the following versions

 "expo": "^33.0.0",
    "expo-asset": "^5.0.0",
    "expo-constants": "^5.0.0",
    "expo-font": "^5.0.0",
    "expo-graphics": "^1.1.0",
    "expo-three": "^3.0.0-alpha.8",
    "expo-web-browser": "^5.0.0",

I’ve also added the following loaders per the other issues re: loading files:

"packagerOpts": {
      "assetExts": [
        "ttf",
        "mp4",
        "otf",
        "dae",
        "glb",
        "gltf",
        "fbx",
        "obj",
        "mtl",
        "amf",
        "3mf",
        "3ds",
        "jpg",
        "assimp",
        "fbx",
        "pmd",
        "vmd",
        "ply",
        "stl",
        "vtk",
        "vtp",
        "babylon",
        "drc",
        "pcd",
        "pack",
        "bvh",
        "x"
      ]
    }

The core issue is that using the exact Assets.js and file structure (Assets.js at the top level, /assets folder containing an exact copy of the one in this repo) the bundler is giving me this error:

I’m thinking perhaps a cache issue or more likely…something completely goofy but I have exactly replicated the structure in this repo and it isn’t working. FWIW, I tried running the /examples directory of this repo as its own app and that gave a ton of typescript errors about missing loaders and packages.

cc @EvanBacon seems like this may be on the back burner at the moment, but if you have a minute, anything come to mind that could be causing this?

[bberak]

I came across this issue as I was looking for something. I had the same problem @evanmrose, the trick that worked for me was to add a metro.config.js file in the root of the project. Here is my file:

const defaultAssetExts = require("metro-config/src/defaults/defaults").assetExts;

module.exports = {
  resolver: {
    assetExts: [
      ...defaultAssetExts,
      "glb"
    ]
  }
};

I think @mattblackdev is right with the packagerOpts not working as expected.

Hope this helps.

[mattblackdev]

@EvanBacon I looked at most of the loader code briefly and it seems pretty tedious to maintain. Any chance there might be a better approach? A new strategy the community could help develop that might be leaner, easier to maintain and less coupled to all the different file extensions/types?