# Local Texture Not Showing with Node.js **URL:** \ **Category:** Questions\ **Tags:** material, texture\ **Created:** [September 13, 2023, 1:45pm UTC](https://forum.babylonjs.com/t/local-texture-not-showing-with-node-js/44093 "2023-09-13T13:45:24Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![11128](https://avatars.discourse-cdn.com/v4/letter/1/d07c76/32.png) [@11128](https://forum.babylonjs.com/u/11128)\ **Post date:** [September 14, 2023, 8:37am UTC](https://forum.babylonjs.com/t/local-texture-not-showing-with-node-js/44093/7 "2023-09-14T08:37:50Z")
Yes, I use next.js. I took the test again with `not_a_babylon_env_map_error_with_node_js.zip` as you listed. As a result, the creation of the texture fails, and the declaration of the inspector (even just the import) starts giving errors. Also, the url, path, etc. for model import are unknown. I think the reason for this may be a problem with the structure of wepack - build, etc. > **[Getting Set Up | Babylon.js Documentation](https://doc.babylonjs.com/guidedLearning/createAGame/gettingSetUp)** > > Dive into some deeper game creation methods and techniques. Something to look at as an example > [@Basic setup of running Babylon.js NullEngine with server side (node.js) using TypeScript](https://forum.babylonjs.com/t/basic-setup-of-running-babylon-js-nullengine-with-server-side-node-js-using-typescript/15817/6): > > As explained earlier node-js expects common.js import style until version 14 so no import / export keywords could work before. In order to convert our import statements, either you could rely on a bundler like webpack/parcel/rollup or you could transpile your files using babel. Here using babel and babel-node for instance, you can add the following dependencies: "devDependencies": { "@babel/cli": "^7.12.1", "@babel/core": "^7.12.3", "@babel/node": "^7.12.6", "@babel/plugin-tra… --- _[View the full topic](https://forum.babylonjs.com/t/local-texture-not-showing-with-node-js/44093)._