Expose real import.meta
properties, plus __dirname
and __filename
for Node.js
#9284
Labels
import.meta
properties, plus __dirname
and __filename
for Node.js
#9284
🙋 feature request
Related: #7623, #8924, #7727
At the moment Parcel transforms
import.meta.url
(and the Node.js-specific cousins__dirname
and__filename
) with no user-land way to actually access the runtime values of these properties short of usingeval
to circumvent Parcel's AST walker. This has caused problems even within Parcel itself (#7948, #9172 (comment)), and Parcel uses a special__parcel__URL__
function to actually emit the runtime value.Developers use
import.meta.url
and its cousins primarily for reflection purposes, i.e. they use it to change the behavior of their code based on the current state of the runtime. The main use cases I've seen are forking workers and accessing a location on disk relative to the runtime file-path. By setting these values at build time, Parcel removes what is in my opinion the main value of these properties; they essentially become useful for debugging and nothing else.💁 Possible Solution
Just like how we have a "fake" module
@parcel/service-worker
to get the service worker manifest information at runtime, something like@parcel/reflection
could exist where Parcel emits runtime reflection information.🔦 Context
I'm trying to get a path relative to the location of the final JavaScript file in a Node.js environment. I could use any of
__dirname
,__filename
, orimport.meta.url
to do this, but Parcel rewrites all of them. Although the value of something likenew URL('other-asset', import.meta.url)
is obvious,import.meta.url
seems quite useless at the moment because Parcel has to rewrite it to a fake absolute path likefile:///path/to/src.ts
, which can't really be used for anything but logging.Right now, I've resorted to doing the following:
I'd like to be able to do something less hacky.
The text was updated successfully, but these errors were encountered: