A bit of a puzzler in here.
Created a package, exported it, imported it.
The package has a prefab and instantiating the prefab all scripts appear to be there, but reported as missing:
(the texture_put script is the last one in the folder, and a preview shows the contents being there too)
Happens across several Unity versions. Meta files and the rest are there, what am I missing?
thanks!
edit: checked the meta ID of the meta of one of the “missing” scripts againt the one referred to by the prefab file, they match, who gives?
It was an error on my side where Unity has a relatively obscure way to complain.
So, following the recomended layout: Unity - Manual: Package layout
there’s a mention of assembly definitions, you do need those, or this error happens.
@ : how come we need that for packages and not for local code? you’d hope that local code that contains the right stuff to deal with platforms -locally- and so on will be enough 
Hi @Lobolopez , the first implementation of the Package Manager had an implicit assembly definition if one was not set explicitly. This was removed because it caused issues (Sorry, I don’t remember what they were). We are working on a scaffolding UX to help create a package with sensible default layout depending on the type of package created (code library, editor tool, asset collection, sample, etc).
Regards,
Pascal
Yeah, it makes sense (might have been name collisions among packages or something), probably also makes sense to auto-namespace the incoming code, but 'tis all good, thanks for the answer!