Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix issues with config relative imports #170

Merged
merged 2 commits into from Feb 24, 2021
Merged

Fix issues with config relative imports #170

merged 2 commits into from Feb 24, 2021

Conversation

muhammadsammy
Copy link
Owner

@muhammadsammy muhammadsammy commented Feb 23, 2021 •
edited

Related to #120

@muhammadsammy muhammadsammy changed the title refactor: use node's vm module instead of eval Fix issues with config parsing Feb 23, 2021
@muhammadsammy
fix: set the vm's __dirname global to the path of the config file
0b3d7c8 
Fixes #120
This is a workaround for errors from relative imports inside the config
by using the `__dirname` global in imports
@muhammadsammy muhammadsammy changed the title Fix issues with config parsing Fix issues with config relative imports Feb 23, 2021
@muhammadsammy muhammadsammy linked an issue Feb 24, 2021 that may be closed by this pull request
Relative imports from tailwind.config.js result into errors with CLI #120
Open
@muhammadsammy muhammadsammy merged commit e1abd7c into master Feb 24, 2021
@muhammadsammy muhammadsammy deleted the muhammadsammy/issue120 branch February 24, 2021 11:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Relative imports from tailwind.config.js result into errors with CLI
1 participant
@muhammadsammy