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

[BUG] CRLF issue on MacOS #322

Closed
2 tasks done
MatteoGauthier opened this issue Dec 5, 2022 · 8 comments · Fixed by #324
Closed
2 tasks done

[BUG] CRLF issue on MacOS #322

MatteoGauthier opened this issue Dec 5, 2022 · 8 comments · Fixed by #324
Labels
bug Something isn't working

Comments

@MatteoGauthier
Copy link

What happened?

Go this error when I try to run yarn dev / 'pnpm dev'

env: node\r: No such file or directory

Version

Latest

What OS are you seeing the problem on?

MacOSX

What browsers are you seeing the problem on?

No response

Relevant log output

env: node\r: No such file or directory

(OPTIONAL) Contact Details

[email protected]

Code of Conduct

  • I agree to follow this project's Code of Conduct
  • I checked the current issues for duplicate problems.
@MatteoGauthier MatteoGauthier added the bug Something isn't working label Dec 5, 2022
@MatteoGauthier
Copy link
Author

➜  with-content-scripts-ui git:(master) ✗ npm run dev

> [email protected] dev
> plasmo dev

env: node\r: No such file or directory

@louisgv
Copy link
Contributor

louisgv commented Dec 5, 2022

@MatteoGauthier thanks for the issue - which version of plasmo did you clone? There was a bug last week in 0.59.0 that was patched in 0.59.2 #306

To test out example repo, please see this discussion: https://discord.com/channels/946290204443025438/1044558522316234752

@MatteoGauthier
Copy link
Author

@louisgv I've installed the "0.59.2" version

@louisgv
Copy link
Contributor

louisgv commented Dec 5, 2022

What is the plasmo version inside the package.json? If it's "workspace:*", that indicates your local clone might be deprecated. Otherwise, @ColdSauce can you test this pls

@MatteoGauthier
Copy link
Author

What is the plasmo version inside the package.json? If it's "workspace:*", that indicates your local clone might be deprecated. Otherwise, @ColdSauce can you test this pls

The version "0.59.2" is in my package.json using a starter

@ColdSauce
Copy link
Contributor

pnpm create plasmo worked for me yesterday, so I think this has been fixed for a while.

@MatteoGauthier did you run pnpm create a while ago, and now you're trying out pnpm dev or did you do the create command recently?

In any case, to mitigate this I recommend running pnpm (substitute for npm, yarn, etc) create in a new directory and copying things over. As Louis said, we had an issue in 0.59.0 and it seems to me that when you ran pnpm create, that was the latest version you picked up.

@MatteoGauthier
Copy link
Author

@ColdSauce I just created a project using pnpm, same behavior with other packages managers

@louisgv louisgv linked a pull request Dec 5, 2022 that will close this issue
2 tasks
@MatteoGauthier
Copy link
Author

Works well thanks 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants