Popup.<<hash>>.js final build resulting in rearrangement of lines different from teh one submitted

We have submitted the extension which is having issue with the final build as the final build in case of reviewer is resulting in re-arrangement of the source code lines, as they compare on their base as the lines are shuffled + chunk vendor last hash is different , that are resulting in rejection pf the extension ,
Though we have observed that the lines are all present same the on e, only different is they are rearranged as the key value pair forming are different in the file , any suggestion what should we do that can help us.

How are these “key value” pairs generated? Do you provide a package-lock that also includes all the build tooling?