You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently next-on-pages creates a single worker with all the app code, is there any reason why you can't create a worker for every file created by the Build output API?
This would also remove a lot of complexity from next-on-pages logic that now has to parse the files and try to deduplicate common parts.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently next-on-pages creates a single worker with all the app code, is there any reason why you can't create a worker for every file created by the Build output API?
This would also remove a lot of complexity from next-on-pages logic that now has to parse the files and try to deduplicate common parts.
Beta Was this translation helpful? Give feedback.
All reactions