Extract Logger into its own package#2165
Conversation
| const config = require('./utils/config'); | ||
| const syncPromise = require('./utils/syncPromise'); | ||
| const logger = require('./Logger'); | ||
| const logger = require('@parcel/Logger'); |
There was a problem hiding this comment.
should be lower case: @parcel/logger
| "name": "babel-plugin-autoinstall" | ||
| "name": "babel-plugin-autoinstall", | ||
| "devDependencies": { | ||
| "@babel/core": "^7.1.2" |
There was a problem hiding this comment.
this shouldn't change - part of the test is asserting that this is added.
|
Awesome, thanks! Can you rebase with master? |
275c73d to
bddae15
Compare
|
I removed the original emoji and prettyError files from utils and exposed them as part of the |
|
I have parcel-bundler 1.11.0 installed locally (don't want to install globally) and using npx as a result. Everything was fine in development, but can't build my assets for production. Am getting the following in Terminal console: Does parcel-bundler not work with npx??? |
|
@interglobalmedia are you using any plugins? |
|
I have since removed parcel, but yes I was. If I remember correctly, the parcel-plugin-bundle-manifest, parcel-plugin-eslint, and parcel-plugin-static-files-copy. |
|
@interglobalmedia then it’s definitely a plugin issue. Plugins shouldn’t be using internal parcel code (including the logger) Sent with GitHawk |
|
I'm not very familiar with parcel. What does that mean? And then why are there plugins to extend parcel? Thanks! |
|
It means that parcel/src/Logger shouldn’t be imported directly but by using Bundler.logger instead as internal code is not protected by semver The plugin architecture wasn’t perfect in parcel 1. It should be easier to extend functionality once Parcel 2 gets released. The bug originates from this line probably https://github.com/BoltDoggy/parcel-plugin-eslint/blob/7a0947bdec7d4552a68ce3a3bbcba339040a2db2/index.js#L1 |
|
Thanks for the response! I looked for some kind of explanation about plugins in the docs, but didn't really find anything that might help. Just a list. Willing to give Parcel another go when version 2 comes out. But will hold off for the moment. I have things I need in my builds which don't work yet with Parcel 1+ (1.11.1). Looking forward to the release! |
↪️ Pull Request
Extract logger code into a separate package inside the monorepo
closes [#2134]
💻 Examples
🚨 Test instructions
✔️ PR Todo