You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running fractive from the command line via a global npm installation, it becomes very difficult to reference one of the example templates in an original story without copying the file to a new location relative to the story, not the fractive installation.
I'm thinking we could implement a hackish macro for that like letting the user write the path $(builtin)/basic.html in fractive.json and Compiler.ts would interpret that into the path of the fractive installation.
The text was updated successfully, but these errors were encountered:
Note: at compile time, the global __dirname variable contains the path of the current source file (i.e. fractive/lib. We can use this to access the location of the fractive installation.
When running fractive from the command line via a global npm installation, it becomes very difficult to reference one of the example templates in an original story without copying the file to a new location relative to the story, not the fractive installation.
I'm thinking we could implement a hackish macro for that like letting the user write the path
$(builtin)/basic.html
infractive.json
and Compiler.ts would interpret that into the path of the fractive installation.The text was updated successfully, but these errors were encountered: