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

Webpack/Translations module causing build errors #24

Open
KuraFire opened this issue Jun 19, 2015 · 2 comments
Open

Webpack/Translations module causing build errors #24

KuraFire opened this issue Jun 19, 2015 · 2 comments

Comments

@KuraFire
Copy link

This could be a local issue, so here's my env for reference:

Pellet: 0.0.100
System: OS X 10.10.3
Node: 0.12.4
(npm: 2.10.1)

Steps to reproduce:

  1. pellet init and use defaults, including Translations
  2. cd into the project, and run pellet run --build
  3. Build errors with this message:

error: [pellet] Error in webpack passes (browser|server) because: Cannot parse records: Unexpected string

Steps to avoid error:

  1. pellet init and use defaults, excluding Translations
  2. cd into the project, and run pellet run --build
  3. Build completes without problems

Notably, the following commands work fine:

  • pellet run build
  • pellet --watch --clean

So it may just be something specific to the command in relation to webpack/translations.

@ghost
Copy link

ghost commented Jun 19, 2015

Thanks for the heads up. I just tried switching my env to node 12.4, but I can not repro the error. I think the problem is with the version of i18n. Do you mind running "npm ls" in pellet and trying editing the translation file in assets/translations.json to just "{}" and see if that fixes the problem.

Thanks again for the help!

@KuraFire
Copy link
Author

@vevo-demetrius-johnson Changing the translations.json file did not fix it. However, I'm noticing now that (days later) in one of my test projects I did for this, the command now runs fine, while in another it still fails with the same issue.

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