EJS Templates, Environment Variables and Cache Invalidation #8573
Replies: 1 comment 3 replies
-
|
In the Some examples of other transformers: parcel/packages/transformers/js/src/JSTransformer.js Lines 534 to 536 in 59610c1 |
Beta Was this translation helpful? Give feedback.
-
|
Awesome, i just added that line to the transformer and it works like a charm. In order to implement this in a more generic way, should a transformer parse the input in order to find all used environment variables? Or rather add a config option that allows users to specify which vars should be tracked? I could try to contribute this to parcel-transformer-ejs... |
Beta Was this translation helpful? Give feedback.
-
|
You should talk to the maintainer of that transformer (open an issue for this repo https://github.com/sarscode/parcel-transformer-ejs). From a user perspective it would ideally find all used env vars automatically. But that depends on what information the EJS library exposes. |
Beta Was this translation helpful? Give feedback.
-
|
Will do, thanks for your quick reply! |
Beta Was this translation helpful? Give feedback.
-
Consider the following EJS file index.ejs.
Then i run parcel with:
When i run parcel again with a different value of SITE_LANG the transformer cache is not invalidated and the change is not reflected in the final output. What do i need to to do in order to have the cache invalidated when the environment variable changes. Is this something that needs to be implemented in the transformer plugin?
Im using parcel 2.7.0 and parcel-transformer-ejs 1.0.0
Thanks a lot!
Beta Was this translation helpful? Give feedback.
All reactions