# 0.33.1 - webpack - config.globalResources not working

**URL:** <https://discourse.aurelia.io/t/0-33-1-webpack-config-globalresources-not-working/934>\
**Category:** Help Requests\
**Created:** [March 20, 2018, 8:24pm UTC](https://discourse.aurelia.io/t/0-33-1-webpack-config-globalresources-not-working/934 "2018-03-20T20:24:19Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![eicthecat](https://avatars.discourse-cdn.com/v4/letter/e/8797f3/32.png) [@eicthecat](https://discourse.aurelia.io/u/eicthecat)\
**Post date:** [March 20, 2018, 8:24pm UTC](https://discourse.aurelia.io/t/0-33-1-webpack-config-globalresources-not-working/934/1 "2018-03-20T20:24:19Z")

</div>

I have succeded in installing the Aurelia cli version 0.33.1 and now previous version and require based project won’t run with “au run” (but let’s say no matter - who has never made a bug…) - the think that’s going wrong and annoy me is that resources registering thru an index.js file with

> config.globalResources([“./elements/test”])

seems not to be handled by the webpack bundle (console message Unhandled rejection Error: Unable to find module with ID: resources/elements/test) - I have tried a lot of paths but did not find a good one - so I turn to the

> \<require from="…

solution whitch is not really clever… is this an issue (or me ?:-))

---

<div class="post-metadata">

**Author:** ![zewa666](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/zewa666/32/19_2.png) [@zewa666](https://discourse.aurelia.io/u/zewa666)\
**Post date:** [March 20, 2018, 8:55pm UTC](https://discourse.aurelia.io/t/0-33-1-webpack-config-globalresources-not-working/934/2 "2018-03-20T20:55:10Z")

</div>

You need to wrap the global resource with PLATFORM.moduleName. search the discourse Forum or take a look at the Docs for further clarification.

---

<div class="post-metadata">

**Author:** ![Alexander-Taran](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/alexander-taran/32/2308_2.png) [@Alexander-Taran](https://discourse.aurelia.io/u/Alexander-Taran)\
**Post date:** [March 20, 2018, 8:57pm UTC](https://discourse.aurelia.io/t/0-33-1-webpack-config-globalresources-not-working/934/3 "2018-03-20T20:57:12Z")

</div>

you (-:

what @zewa666 said  
as well take a look at this tutorial  
[http://aurelia.io/docs/tutorials/creating-a-contact-manager#building-the-application-shell](http://aurelia.io/docs/tutorials/creating-a-contact-manager#building-the-application-shell)

---

<div class="post-metadata">

**Author:** ![eicthecat](https://avatars.discourse-cdn.com/v4/letter/e/8797f3/32.png) [@eicthecat](https://discourse.aurelia.io/u/eicthecat)\
**Post date:** [March 21, 2018, 7:11am UTC](https://discourse.aurelia.io/t/0-33-1-webpack-config-globalresources-not-working/934/4 "2018-03-21T07:11:07Z")

</div>

> [@zewa666](#):
>
> PLATFORM.moduleName

Thanks a lot - …arglll, me again - it’s been a long time since I read the documentation!  
For my understanding, PLATFORM.moduleName seems used everywhere now… hum… not a big deal - a human can do this… but for my understanding… when not to use it?

---

<div class="post-metadata">

**Author:** ![zewa666](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/zewa666/32/19_2.png) [@zewa666](https://discourse.aurelia.io/u/zewa666)\
**Post date:** [March 21, 2018, 7:13am UTC](https://discourse.aurelia.io/t/0-33-1-webpack-config-globalresources-not-working/934/5 "2018-03-21T07:13:04Z")

</div>

The need for moduleName is to explain Webpack properly how to find those additional resources. So in essence wherever you dynamically load content, like in `globalResources`, plugin names or the sorts use `PLATFORM.moduleName`.  
There is work underway to remove the need for that by using a different API

---

<div class="post-metadata">

**Author:** ![eicthecat](https://avatars.discourse-cdn.com/v4/letter/e/8797f3/32.png) [@eicthecat](https://discourse.aurelia.io/u/eicthecat)\
**Post date:** [March 21, 2018, 7:33am UTC](https://discourse.aurelia.io/t/0-33-1-webpack-config-globalresources-not-working/934/6 "2018-03-21T07:33:17Z")

</div>

First, thanks again for your answer - I can now move my code to the new version.  
I can understand the webpack needs - and the fact that when something is flaged, it’s flaged so there are no misunderstandings…  
But as a lazy developer I may have prefered to set the minimum - my job is to make bugs, it should be the builder job to find which buged-modules I am using from a dependency walk [I am really lazy :-)] - don’t you think so?  
(I think i use some gulp-amd to do this for require - and so far it works)

---

<div class="post-metadata">

**Author:** ![zewa666](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/zewa666/32/19_2.png) [@zewa666](https://discourse.aurelia.io/u/zewa666)\
**Post date:** [March 21, 2018, 7:51am UTC](https://discourse.aurelia.io/t/0-33-1-webpack-config-globalresources-not-working/934/7 "2018-03-21T07:51:13Z")

</div>

If you’re referring to error messages, those exactly state that, can’t find requested module/resource 🙂  
Nevertheless as said we all agree that its suboptimal having to add those flags and I hope said PR gets merged quickly