♫Alex Swan BoldBigflank

This is the follow up to a post I wrote recently called From Require.js to Webpack - Party 1 (the why) which was published in my personal blog.

In that post I talked about 3 main reasons for moving from require.js to webpack:

Common JS support
NPM support
a healthy loader/plugin ecosystem.

Here I'll instead talk about some of the technical challenges that we faced during the migration. Despite the clear benefits in developer experience (DX) the setup was fairly difficult and I'd like to cover some of the challanges we faced to make the transition a bit easier.

	using UnityEngine;
	using UnityEngine.EventSystems;

	public class OrtographicDrag: MonoBehaviour, IDragHandler
	{
	private Camera _mainCamera;
	public float DistanceToCamera;

	public void OnDrag(PointerEventData eventData)
	{

	public AudioSource audioSauce;
	public string CurrentAudioInput = "none";
	int deviceNum = 0;

	void Start()
	{

	string[] inputDevices = new string[Microphone.devices.Length];
	deviceNum = 0;