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.

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

Keep the nightmare package. #52

Open
klablink opened this issue Sep 25, 2023 · 4 comments
Open

Keep the nightmare package. #52

klablink opened this issue Sep 25, 2023 · 4 comments

Comments

@klablink
Copy link

The npm package nigthmare seems to be no longer supported. The latest version released, 3.0.2, integrated chromium at version '61.0.3163.100', which does not support the new javascript directives. We can use a fork or create one for the purpose but I don't know if it is actually used. Is anyone using nigthmare for testing?

@github-actions
Copy link

Thank you for submitting this issue!

We, the Members of Meteor Community Packages take every issue seriously.
Our goal is to provide long-term lifecycles for packages and keep up
with the newest changes in Meteor and the overall NodeJs/JavaScript ecosystem.

However, we contribute to these packages mostly in our free time.
Therefore, we can't guarantee you issues to be solved within certain time.

If you think this issue is trivial to solve, don't hesitate to submit
a pull request, too! We will accompany you in the process with reviews and hints
on how to get development set up.

Please also consider sponsoring the maintainers of the package.
If you don't know who is currently maintaining this package, just leave a comment
and we'll let you know

@nachocodoner
Copy link
Member

#53

I just reviewed Nightmare and seems to be working on my end. I only faced a warning which I skipped since in test env that security alert is not important. What issue do you face exactly? Any error message or so?

@klablink
Copy link
Author

The instruction introduced In Blaze using the syntax:

const templateName = this.view?.name.

This seems not to be supported by version 61 of chromium.

@nachocodoner
Copy link
Member

Do you have a repository with the problem you face so I can easily reproduce and check your problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant