AAM configuration

I suggest enabling X-WA-Info headers (enabled in advanced application settings--choose standard or debug).

When you subsequently request your javascript through bigip, you should get a header which looks like this:

X-WA-Info: [V2.S10201.A82433.P18038.N13694.RN0.U3291613691].[OT/all.OG/includes].[P/0.2].[O/0.1].[EH1/0].[DH1/0].[C/Pk.s].[K/n]

Then you can decode that on your bigip at the shell prompt to see what policy node matched the request:

wainfodecode '[V2.S10201.A82433.P18038.N13694.RN0.U3291613691].[OT/all.OG/includes].[P/0.2].[O/0.1].[EH1/0].[DH1/0].[C/Pk.s].[K/n]'

    V2: X-WA-Info Format Version
    S10201: Response was served from the origin web server, because the request was for new content.
    A82433: Application: /Common/intranet
    P18038: Local-policy: /Common/Copy2 of Generic Policy - Complete
    N13694: Request Policy Node: Includes
    RN0: Response match did not supersede request match
    UCI hash: c43209fb
    Object type: all
    Object group: includes
    Request served from TMM: 0.2
    Request owned by TMM: 0.1
    Entity hit count (local/remote): 1/0
    Document hit count (local/remote): 1/0
    Document cacheable, but not seen enough to cache.
    Reason: Usable content received.
    Bypass: Cache score does not meet caching threshold.
    Parking: Not parked.

If the node which matched is not the node you expected (where you enabled minification) you need to adjust your matching rules until the rule you expect to match does so.

If you get no X-WA-Info header at all, you may not have AM enabled at all.