fix: set a name to exported fn

[ramasilveyra]

This PR contains a:

• bugfix
• new feature
• code refactor
• test update
• typo fix
• metadata update

Motivation / Use-Case

This can help debugging since error stack traces will have names.

And also removes the warning of anonymous functions next.js https://nextjs.link/codemod-ndc from.

Breaking Changes

None

Additional Info

None

[codecov]

Codecov Report

Merging #299 (38888c6) into master (464bf30) will increase coverage by 0.16%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #299      +/-   ##
==========================================
+ Coverage   76.02%   76.19%   +0.16%     
==========================================
  Files           6        6              
  Lines         146      147       +1     
  Branches       51       51              
==========================================
+ Hits          111      112       +1     
  Misses         30       30              
  Partials        5        5              

Impacted Files	Coverage Δ
src/utils.js	86.84% <100.00%> (+0.35%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 464bf30...38888c6. Read the comment docs.

[alexander-akait]

What is the problem? Can you provide example

[ramasilveyra]

@evilebottnawi next.js logs this when every worker is built, which is a bit noisy:

../lib/workers/some.worker.ts
Anonymous function declarations cause Fast Refresh to not preserve local component state.
Please add a name to your function, for example:
Before
export default function () { /* ... */ }
After
export default function Named() { /* ... */ }
A codemod is available to fix the most common cases: https://nextjs.link/codemod-ndc

The code of this log is here https://github.com/vercel/next.js/blob/8221c180a55828b39a7e1e01811365bfaaa0dd19/packages/next/build/babel/plugins/no-anonymous-default-export.ts#L59-L68.

But adding a function name in this lib it can also help while debugging errors, since stack trace errors will have names.

[alexander-akait]

No sure it will fix the problem with hot reloading, but I can merge it

[alexander-akait]

Please avoid using this module, it is deprecated, we don't need extra module for simple logic

[ramasilveyra]

@evilebottnawi Sorry for my delay.

I've tried to use simpler solutions like https://stackoverflow.com/a/2970667, but they can fail with RangeError.

So since lodash.camelcase is deprecated I have remplace it with camelcase.

camelcase:

• It has recent activity, latest release was published 1 month ago.
• It doesn't depend on more dependencies.
• It's small https://bundlephobia.com/result?p=camelcase@6.2.0. More than 3 times smaller than lodash.camelcase.

If still doesn't work, I can try inlining this code https://github.com/sindresorhus/camelcase/blob/master/index.js here.

[alexander-akait]

Why just don't use ${typeOfWorker}_fn name without any additional logic?

[ramasilveyra]

@alexander-akait by typeOfWorker do you mean workerConstructor?

worker-loader/src/utils.js

Lines 38 to 47 in 464bf30

	let workerConstructor;
	let workerOptions;
	if (typeof options.worker === 'undefined') {
	workerConstructor = 'Worker';
	} else if (typeof options.worker === 'string') {
	workerConstructor = options.worker;
	} else {
	({ type: workerConstructor, options: workerOptions } = options.worker);
	}

I can make that change, that would still solve the issue with noisy logs from next.js! The only difference is that unique function names can help while debugging.

[alexander-akait]

I don't think you need unique function here because you already have stack trace in console with link on file, line and column

[ramasilveyra]

@alexander-akait done!

[alexander-akait]

Thanks

[ramasilveyra]

Thanks for your time @alexander-akait !