Alex

Found a setting for changing color for codeLens: ```json "editorCodeLens.foreground": "#666" ``` So it can be made less distractive:  But I think I still would prefer a shorter version...

So with short notice, we just give a user an indication of the state. But when we actually want to give a hint that probably something wrong here, you may...

> I think it should be possible to toggle the lenses at the top of the file near the module definition. Could you elaborate on what actions should be available...

Just for notice, this is how Elm's lenses look like: 

> @wclr what happens when you click on them? Unexpose/expose action.

It works if the type is defined in the same module, does not for external types, so maybe it is not a regression.

> Hello @wclr. Please provide a [minimal reproduction](https://stackoverflow.com/help/minimal-reproducible-example) using a GitHub repository or [StackBlitz](https://vite.new). Issues marked with `need reproduction` will be closed if they have no activity within 3 days....

Another thing that is related to file params, is that during the build plugins (neither `rollupOptions.plugins` no `worker.plugins`) do not get any access to to params (in `resolveId` or `transform`)....

I believe I understand where it comes from, with the current approach to packages, user namespaces rightfully may seem to be **unnecessary level of grouping**. In a certain sense, it...

A couple of notices to the "no change" post statements. > As you can see above, if you really care about namespacing your package you can already do it today,...