[Pkg-javascript-devel] Typescript and Debian directories

[Jonas Smedegaard]

Quoting Jérémy Lal (2021-05-05 12:38:30)
> Le mer. 5 mai 2021 à 12:29, Jonas Smedegaard <jonas at jones.dk> a écrit :
> 
> > Quoting Jérémy Lal (2021-05-05 11:04:07)
> > > Hello, i'm all right patching typescript, but that would mean local
> > > installs of typescript
> > > wouldn't find the modules anyway.
> > > So... do you know if a local user install of typescript is going to want
> > to
> > > discover global modules ?
> > > If not, then it's okay to patch typescript and i think i can do it...
> >
> > If possible to patch Typescript into supporting shared resources, then
> > that would certainly be the best approach, I think.
> >
> > Seems upstream fails to understand the value of supporting shared
> > resources. If we can reasonably maintain a patch to do it locally in
> > Debian, then it would ease both building and using Typescript in Debian
> > now, and be an offer for upstream to adopt if they change their minds.
> >
> > Patching Debian to include magic path names easing local building by
> > tricking the tools into seeing shared resources as being local sounds
> > bad to me: Upstream is then deliberately being tricked into working in
> > ways unsupported upstream, and while we only care about using it for
> > build routines we expose it to our users as well, which might cause
> > side-effects for them that then noone have any attention towards.
> >
> > If we cannot (or will not) maintain a general deviation of Typescript to
> > support shared resources, then we should contain tricks to only affect
> > build environment, not "leak" into our user-facing environments (if
> > possible).
> >
> > Great that you tried, Yadd.  Great if you can succeed, Jérémy :-)
> >
> 
> That's probably the same issue with nodejs indeed.
> Nodejs tries local first, then falls back to global if any.
> 
> However i'm concerned that if i patch typescript, module resolution in
> developer
> tools (linters...) will fail too.
> So maybe not patching as Yadd suggests is safer and won't disrupt any
> workflow.

Sorry, I don't follow.

If Typescript can be patched to use a lookup path as fallback for 
locally static path, then that would make Typescript itself be able to 
compile code.

Yes, that same code might then fail and inspection e.g. by eslint, if 
eslint were to check for Typescript modules on its own.  I don't see how 
that would be a problem for Debian, however.  We already have packages 
that can build without being possible to check their testsuites.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-javascript-devel/attachments/20210505/ff102274/attachment.sig>